Microsoft Azure AzureDataManagementClient
Browse all Azure APIs41
AI ReadinessFoundational (D-)41/100
Agent-ready OpenAPI document · curated by JenticStorageDatabaseoauth211 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Register on-premises SQL Server instances as Azure Data resources and manage their SQL Server child entries.
Use for: I need to register an on-prem SQL Server with Azure, List SQL Server registrations in my subscription, Add a SQL Server entry to an existing registration, Delete a SQL Server registration from Azure Data
Not supported: Does not run SQL queries, manage cloud Azure SQL databases, or provision Azure Arc agents - use for Microsoft.AzureData SQL Server registrations only.
Jentic publishes the only available OpenAPI specification for AzureDataManagementClient, keeping it validated and agent-ready. The API registers and manages on-premises SQL Server instances as Azure Data resources, letting agents create SQL Server registrations, list registered SQL Servers under a registration, and manage individual SQL Server entries. It targets the Microsoft.AzureData resource provider on Azure Resource Manager and is intended for hybrid scenarios where on-prem SQL Server inventory needs to surface inside the Azure portal and ARM tooling.
Install Jentic One Beta
Connect the AzureDataManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AzureDataManagementClient, 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%2Fazuredatamanagementclient" | 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%2Fazuredatamanagementclient" | 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 AzureDataManagementClient API.
Register an on-premises SQL Server group as an Azure Data resource
List SQL Server registrations across a subscription or resource group
Patch a SQL Server registration to update its tags or properties
Delete a SQL Server registration to remove it from Azure
List SQL Server entries under a registration
Create or delete a named SQL Server child resource on a registration
List operations exposed by the Microsoft.AzureData provider
Use Cases
Patterns agents use AzureDataManagementClient API for, with concrete tasks.
★ Bring on-prem SQL Server inventory into Azure
Register a group of on-premises SQL Server instances as a single Microsoft.AzureData/sqlServerRegistrations resource so the inventory shows up in the Azure portal and is reachable from ARM tooling. The PUT /sqlServerRegistrations/{name} operation accepts the registration metadata; subsequent PUT calls add named SQL Server children. Required for hybrid Azure Data workflows that span on-prem and cloud.
PUT /resourceGroups/{rg}/providers/Microsoft.AzureData/sqlServerRegistrations/onprem-prod and verify provisioningState=Succeeded
Inventory audit of registered SQL Servers
Walk every registration in a subscription and list the SQL Server children attached, building a single source of truth for on-prem SQL inventory visible to Azure. The GET /sqlServerRegistrations and nested /sqlServers collection calls return the full inventory in two passes. Output supports compliance reporting and licence reconciliation.
GET /subscriptions/{sub}/providers/Microsoft.AzureData/sqlServerRegistrations, then for each registration GET its sqlServers collection and emit a CSV
Add a new SQL Server to an existing registration
Attach a newly provisioned on-prem SQL Server to an existing registration so it is visible alongside its peers in Azure. The PUT /sqlServerRegistrations/{name}/sqlServers/{sqlServerName} operation creates the child resource without touching the parent registration. Standard step when bringing additional servers online into an existing hybrid estate.
PUT /sqlServerRegistrations/onprem-prod/sqlServers/sql-east-3 with the SQL Server properties and confirm subsequent GET returns the new child
Decommission a registration
Remove a SQL Server registration from Azure when retiring an on-prem environment. The DELETE /sqlServerRegistrations/{name} operation removes the registration and detaches its SQL Server children. Use during data centre decommissioning or migration cleanup.
DELETE /resourceGroups/{rg}/providers/Microsoft.AzureData/sqlServerRegistrations/{name} and verify subsequent GET returns 404
Agent-driven hybrid inventory
Let an AI agent maintain Azure Data registrations as servers are added and removed in the data centre, without an operator hand-coding the long ARM URL. Through Jentic the agent searches by intent, loads the registration schema, and executes the right PUT or DELETE. Removes a class of typos when constructing nested Microsoft.AzureData resource paths.
Search Jentic for 'register sql server with azure data', load the registration schema, and execute the PUT against the named registration
Key Endpoints
11 endpoints — jentic publishes the only available openapi specification for azuredatamanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AzureData/sqlServerRegistrations
List registrations in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations
List registrations in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}
Create or update a SQL Server registration
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}
Patch tags on a registration
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}
Delete a registration
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers
List SQL Server children under a registration
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers/{sqlServerName}
Create or update a SQL Server child
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers/{sqlServerName}
Delete a SQL Server child
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AzureData/sqlServerRegistrations
List registrations in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations
List registrations in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}
Create or update a SQL Server registration
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}
Patch tags on a registration
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}
Delete a registration
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers
List SQL Server children under a registration
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers/{sqlServerName}
Create or update a SQL Server child
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AzureData/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers/{sqlServerName}
Delete a SQL Server child
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AzureDataManagementClient
- Foundational (D-)41/100
67
Foundational Compliance61
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
67
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
61
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
78%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AzureDataManagementClient API by hand means registering an Azure AD app for OAuth2 bearer auth against management.azure.com and building the nested Microsoft.AzureData path down to each SQL Server child under a registration. Through Jentic you install once, import AzureDataManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The registration and child sit in the URL path (/sqlServerRegistrations/{sqlServerRegistrationName}/sqlServers/{sqlServerName}), so a rule can pin your agent to one registration. You choose the operations it may call, so the DELETE calls that remove a registration or detach a SQL Server child are not included unless you add them.
Credential isolation
Your Azure AD credential 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 'register an on-prem sql server with azure data' or 'list sql server registrations', and Jentic returns the matching Microsoft.AzureData sqlServerRegistrations operation with its property schema so the agent calls the right endpoint without memorising the nested ARM path.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AzureDataManagementClient API through Jentic.
Why is there no official OpenAPI spec for AzureDataManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AzureDataManagementClient 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 this API use?
The API uses Azure AD OAuth 2.0 with the implicit flow, scoped to user_impersonation against management.azure.com. Through Jentic, the bearer token is held in your Jentic One instance and exchanged for a scoped access token at execution time.
Can I register multiple SQL Servers under one registration?
Yes. A sqlServerRegistration is a parent resource; SQL Server entries are children at /sqlServerRegistrations/{name}/sqlServers/{sqlServerName}. PUT each child to add it; DELETE to detach without removing the parent.
What are the rate limits for this API?
Azure Resource Manager applies tenant-level throttling - typically 12,000 reads and 1,200 writes per hour per subscription. Most operations on this preview API are synchronous and return 200 with the resulting resource.
How do I create a registration through Jentic?
Run pip install jentic, then search for 'register sql server with azure data'. Jentic returns the PUT /sqlServerRegistrations/{name} operation, loads the registration property schema, and executes against the resource group you specify.
Does this API run queries against the registered SQL Servers?
No. This API manages registration metadata only. Connecting to the registered SQL Server data plane to run queries requires a SQL client and direct network access to the on-prem instance.
Can I limit what my agent is allowed to do with the Microsoft Azure Data SQL Server API?
Yes. Because you run Jentic One yourself, your own rules decide which Microsoft.AzureData operations and credentials the agent may use. You pick the exact calls it can make, so destructive operations like DELETE on a sqlServerRegistration or on a SQL Server child are excluded unless you explicitly add them. Since the registration and child names sit in the URL path, a rule can also pin the agent to a single registration while still allowing it to list or create the SQL Server entries beneath it.
GET STARTED