Microsoft Azure DiskResourceProviderClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth216 Endpoints

Install Jentic One Beta

Connect the DiskResourceProviderClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DiskResourceProviderClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DiskResourceProviderClient API.

Provision a managed disk in a chosen size, SKU, and region

Take a point-in-time snapshot of an existing managed disk

Grant temporary SAS read or write access to a disk for direct blob copy

GET STARTED

Start building with DiskResourceProviderClient API

Explore with Jentic

View OpenAPI Document

For Agents

Create, update, snapshot, and grant SAS access to Azure managed disks and snapshots in any subscription, resource group, or region.

Use for: I need to provision a 1TB managed disk for a new VM, Take a snapshot of the OS disk before applying patches, Grant temporary SAS access to a disk so I can copy it to another region, List all unattached managed disks in my subscription

Not supported: Does not manage virtual machines, virtual networks, or attached file shares - use for Azure managed disks and snapshots only.

Use Cases

Patterns agents use DiskResourceProviderClient API for, with concrete tasks.

★ Automated VM Backup via Snapshots

Operations teams need point-in-time copies of VM disks before risky changes such as OS upgrades or schema migrations. The Disk Resource Provider exposes Snapshots_CreateOrUpdate and Disks_Get so a script or agent can enumerate the disks attached to a VM, snapshot each one in parallel, tag the snapshots with a retention date, and revert by creating a new disk from the snapshot if the change fails. The whole flow is API-driven and avoids the manual portal click-through.

Snapshot the disk named vm01-osdisk in resource group prod-rg, tag the snapshot with retention=14d, and return the snapshot resource ID.

Cross-Region Disk Migration

Moving a disk between regions or subscriptions traditionally requires the Azure portal copy flow. With Disks_GrantAccess the API issues a short-lived SAS URI that points at the underlying blob, so an agent can call AzCopy or the Storage REST API to stream the disk content into a new region, then create a destination disk and revoke access. This lets DR runbooks and lift-and-shift jobs run unattended.

Call Disks_GrantAccess on disk db01-data with a 60 minute lease, then issue Disks_RevokeAccess once the copy completes.

Disk Hygiene and Cost Reclamation

Unattached managed disks accrue cost silently. By listing all disks in a subscription and filtering for diskState equals Unattached, a finance or platform team can identify reclaim candidates, snapshot them for safety, and delete the originals. Combined with snapshot age filtering, this drives steady monthly savings without human review of every disk.

List every disk in subscription 11111111-2222-3333-4444-555555555555 where diskState equals Unattached, snapshot each one, then delete the disk.

AI Agent Disk Provisioning via Jentic

An infrastructure agent integrated through Jentic can fulfil a request like provision a 512GB Premium SSD for the analytics VM end-to-end. It searches Jentic for create azure managed disk, loads the Disks_CreateOrUpdate schema, fills in the SKU and size, and returns the disk resource ID. Because Jentic holds the Azure service principal credentials in its vault, the agent never sees the underlying secret.

Through Jentic, search for create an azure managed disk, load Disks_CreateOrUpdate, and create a 512GB Premium_LRS disk in eastus2 attached to resource group analytics-rg.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for diskresourceproviderclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}

Create or update a managed disk

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}

Get a managed disk

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}

Delete a managed disk

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}/beginGetAccess

Grant temporary SAS access to a disk

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/snapshots/{snapshotName}

Create or update a snapshot

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Compute/disks

List all managed disks in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}

Create or update a managed disk

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}

Get a managed disk

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}

Delete a managed disk

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/disks/{diskName}/beginGetAccess

Grant temporary SAS access to a disk

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/snapshots/{snapshotName}

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected as a short-lived bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an azure managed disk' or 'snapshot a disk', and Jentic returns the matching Disks or Snapshots operation with its disk-name, location, SKU, and creation-data input schema so the agent calls the right endpoint without browsing ARM docs.

Time to first call

FAQs

Specific to using DiskResourceProviderClient API through Jentic.

Why is there no official OpenAPI spec for DiskResourceProviderClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DiskResourceProviderClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the DiskResourceProviderClient use?

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The caller must be a service principal or managed identity with at least Disk Contributor or Virtual Machine Contributor on the target subscription or resource group. Through Jentic, Azure credentials live in your Jentic One instance and the agent only sees a scoped bearer token.

Can I copy an Azure managed disk to another region with this API?

Indirectly. Call POST .../disks/{diskName}/beginGetAccess to obtain a short-lived SAS URI, stream the underlying VHD blob into the destination region with AzCopy or the Storage REST API, then call POST .../disks/{diskName}/endGetAccess to revoke the lease. The Disk Resource Provider issues the SAS but does not perform the copy itself.

What are the rate limits for the DiskResourceProviderClient?

Azure Resource Manager applies subscription-scoped throttling - broadly 12,000 reads per hour and 1,200 writes per hour per subscription, plus per-resource-provider limits. Disk and snapshot create or update operations are asynchronous: the API returns 202 with an Azure-AsyncOperation URL to poll. Always honour x-ms-ratelimit-remaining-* headers before bursting.

How do I provision a managed disk through Jentic?

Run pip install jentic, search for create an azure managed disk, load the Disks_CreateOrUpdate schema, supply diskName, location, sku.name (e.g. Premium_LRS), and creationData.createOption (Empty), then execute. The response includes the provisioning state - poll Disks_Get until it reads Succeeded.

Does this API manage virtual machines or virtual networks?

No. DiskResourceProviderClient only manages disks and snapshots under Microsoft.Compute. To attach a disk to a VM, scale a VM, or change its network configuration, use the separate Compute and Network resource provider APIs.

Can I limit what my agent is allowed to do with the Microsoft Azure Disks API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since the subscription, resource group, and disk name all sit in the URL path, you can pin the agent to a single subscription and resource group and grant only read or snapshot operations. Destructive calls such as deleting a disk or granting a SAS access URI stay off limits unless you explicitly add them.

Microsoft Azure DiskResourceProviderClient

Connect the DiskResourceProviderClient to your agent

Capabilities

Start building with DiskResourceProviderClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs