Microsoft Azure ComputeDiskAdminManagementClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth24 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Start, monitor, and cancel disk migration jobs on an Azure Stack stamp to rebalance storage shares or evacuate failing hardware.
Use for: I need to migrate tenant disks off a failing storage share on this Azure Stack stamp, List all running disk migration jobs at the eastus location, Cancel disk migration job 12345 because it is causing latency, Check the status of disk migration job abc-def
Not supported: Does not create or attach tenant disks, run snapshots, or manage public Azure managed disks - use for Azure Stack admin-plane disk migration jobs only.
Jentic publishes the only available OpenAPI specification for ComputeDiskAdminManagementClient, keeping it validated and agent-ready. The Admin Compute Disk Management Client manages disk migration jobs on an Azure Stack stamp - used by operators to move tenant disks between storage shares to rebalance capacity or evacuate failing hardware. It exposes 4 endpoints covering listing, getting, creating, and cancelling diskMigrationJobs scoped to a location. It is an admin-plane API, distinct from the tenant-side disk APIs.
Install Jentic One Beta
Connect the ComputeDiskAdminManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ComputeDiskAdminManagementClient, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcompute-disk-admin-management-client" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcompute-disk-admin-management-client" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 ComputeDiskAdminManagementClient API.
Start a disk migration job to move tenant disks from one storage share to another
Monitor the progress of a running disk migration job by migration ID
Cancel a disk migration job that is no longer needed or is causing impact
List all disk migration jobs at a location to audit fabric-side rebalancing activity
Inspect a single migration job's source share, target share, and status for post-incident review
Use Cases
Patterns agents use ComputeDiskAdminManagementClient API for, with concrete tasks.
★ Evacuate disks from a failing storage share
When SMART warnings or capacity pressure hit a storage share, an Azure Stack operator needs to migrate tenant disks off it without disrupting workloads. The Compute Disk Admin Management Client creates a diskMigrationJob with the source and target shares, returns a migration ID, and exposes status polling so the runbook can wait for completion or escalate.
PUT /subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/eastus/diskmigrationjobs/{migrationId} with sourceShare=share001 and targetShare=share002, then poll the migration ID until status is Succeeded.
Audit migration activity at a location
Operators need a periodic view of every disk migration job at a location - running, completed, and failed - to feed capacity reports and to detect runaway rebalancing. Listing diskmigrationjobs at the location returns the full set so it can be summarised by status.
GET /subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/eastus/diskmigrationjobs and group results by status.
Cancel a runaway migration
If a disk migration is causing tenant impact (latency, IOPS pressure on the target share) the operator must be able to stop it immediately. The Cancel action on a diskMigrationJob terminates the job and returns the disks to a stable state on whichever share they currently sit.
POST /subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/eastus/diskmigrationjobs/{migrationId}/Cancel and confirm the migration enters Cancelled state.
Agent-driven storage rebalancing through Jentic
An AI agent integrated through Jentic can monitor share utilisation across an Azure Stack stamp and automatically open disk migration jobs when a share crosses a high-water mark. Jentic's intent search exposes the right diskMigrationJobs operation and the AAD operator token never leaves the vault.
When share001 utilisation exceeds 85%, create a diskMigrationJob to move 100GB of disks to share002 and report the migration ID.
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for computediskadminmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs
List disk migration jobs at a location
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}
Get a single disk migration job by ID
PUT
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}
Create or update a disk migration job
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}/Cancel
Cancel a running disk migration job
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs
List disk migration jobs at a location
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}
Get a single disk migration job by ID
PUT
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}
Create or update a disk migration job
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}/Cancel
Cancel a running disk migration job
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Compute Disk Admin client by hand means registering an Azure AD app for the implicit OAuth flow, holding an Azure Stack operator role, and pointing at your own adminmanagement.local.azurestack.external stamp host rather than public Azure. Through Jentic you install once, import ComputeDiskAdminManagementClient from the API Directory, store the Azure AD operator token once, and your agent calls it.
Permission scoping
The subscription, location, and migration id all travel in the URL path (/subscriptions/{subscriptionId}/.../locations/{location}/diskmigrationjobs/{migrationId}), so a rule can pin the agent to one stamp location and its migration jobs. You choose the operations it may call, so destructive ones like creating a new disk migration job or cancelling a running one are not included unless you add them.
Credential isolation
Your Azure Stack operator token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'migrate disks off a failing Azure Stack share' or 'cancel a disk migration job', and Jentic returns the matching diskmigrationjobs operation with its input schema so the agent calls the right endpoint without reading the Microsoft.Compute.Admin reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ComputeDiskAdminManagementClient API through Jentic.
Why is there no official OpenAPI spec for ComputeDiskAdminManagementClient?
Microsoft does not publish a consolidated OpenAPI specification for the Azure Stack Compute Disk Admin API. Jentic generates and maintains this spec so that AI agents and developers can call ComputeDiskAdminManagementClient 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 ComputeDiskAdminManagementClient use?
It uses Azure Active Directory OAuth 2.0 with the implicit flow at https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. The caller must hold an Azure Stack operator role. Through Jentic the AAD token is held in the encrypted vault.
Can I cancel a running disk migration with this API?
Yes. Issue POST /subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}/Cancel. The migration transitions to Cancelled and the disks remain on whichever share they currently occupy.
What are the rate limits for the ComputeDiskAdminManagementClient?
Azure Stack admin endpoints inherit Azure Resource Manager subscription-level throttling (typically 12,000 reads and 1,200 writes per hour per subscription). The spec does not declare separate rate-limit headers.
How do I start a disk migration through Jentic?
Search Jentic for 'migrate disks azure stack', load the schema for PUT /subscriptions/{subscriptionId}/providers/Microsoft.Compute.Admin/locations/{location}/diskmigrationjobs/{migrationId}, and execute it with sourceShare and targetShare in the body. Run pip install jentic to get the SDK.
Is the ComputeDiskAdminManagementClient free?
Calling the admin API itself is free; you must hold an Azure Stack operator role. Costs come from running the Azure Stack stamp, not from initiating disk migrations.
Can I limit what my agent is allowed to do with the Compute Disk Admin Management Client?
Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. Since the subscription, location, and migration ID all travel in the URL path, you can pin the agent to a single Azure Stack stamp location and its disk migration jobs. You also choose which operations are exposed, so you can allow read-only calls like listing and getting migration jobs while withholding the destructive PUT that creates a disk migration and the Cancel action unless you explicitly add them.
GET STARTED