Microsoft Azure AzureDataManagementClient

Name: AzureDataManagementClient API
Brand: AzureDataManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth211 EndpointsREST

For Agents

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.

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 AzureDataManagementClient API.

List SQL Server registrations across a subscription or resource group

Patch a SQL Server registration to update its tags or properties

GET STARTED

Start building with AzureDataManagementClient API

Explore with Jentic

View OpenAPI Document

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.

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}

Why Jentic?

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

Credential isolation

Azure AD OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens at execution time — service principal client secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'register on-prem sql server with azure data') and Jentic returns the matching Microsoft.AzureData sqlServerRegistrations operation with its property schema, so the agent does not need to memorise the nested ARM resource path.

Time to first call

Direct ARM integration: 1-3 days for AAD app registration, registration property discovery, and child-resource plumbing. Through Jentic: under 1 hour — search, load, execute.

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 at https://app.jentic.com/sign-up.

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 the Jentic vault 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.

Microsoft Azure AzureDataManagementClient

Connect the AzureDataManagementClient to your agent

Capabilities

Start building with AzureDataManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs