Microsoft Azure SqlManagementClient

★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth26 EndpointsREST

For Agents

List schemas, tables, and columns inside an Azure SQL Database server so an agent can reason about database structure before running queries.

Install Jentic One Beta

Connect the SqlManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SqlManagementClient, 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 SqlManagementClient API.

List all schemas defined inside a specific Azure SQL Database

Retrieve detailed metadata for a named schema in a database

Enumerate every table contained within a given schema

GET STARTED

Start building with SqlManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for SqlManagementClient, keeping it validated and agent-ready. The Azure SQL Database management API exposes a RESTful interface for inspecting database schema metadata on Azure SQL Database servers, including schemas, tables, and columns under a given database. It targets the database-schema management surface of the broader Azure SQL control plane and is scoped to read operations on schema, table, and column resources. Use it when an agent needs to introspect the structure of an Azure SQL Database before issuing queries or generating data models.

Use Cases

Patterns agents use SqlManagementClient API for, with concrete tasks.

★ Pre-Query Schema Discovery

Before issuing SQL against an Azure SQL Database, an application or agent often needs to know which schemas, tables, and columns exist on the target server. SqlManagementClient exposes the schema, table, and column resources under a database so callers can enumerate structure without running INFORMATION_SCHEMA queries against the data plane. This keeps schema discovery in the Azure Resource Manager control plane, with the same auth and audit trail as other Azure operations.

List all schemas in the database 'reporting' on Azure SQL server 'analytics-eu' inside resource group 'data-rg', then list the tables in the 'dbo' schema.

Documenting Existing Azure SQL Databases

Teams onboarding to an existing Azure SQL Database deployment frequently need to generate up-to-date documentation of schemas, tables, and columns. SqlManagementClient lets an automated job walk the schema tree resource by resource and emit a Markdown or JSON catalog. Because every call goes through Azure RBAC, only principals with reader rights on the SQL server can produce the documentation.

Walk every schema, table, and column on the Azure SQL server 'finance-prod' in resource group 'finance-rg' and emit a JSON catalog grouped by schema.

Schema-Aware Query Generation by Agents

AI agents that author SQL on behalf of a user need accurate column names and table names; hallucinated identifiers cause query failures and bad data. Through Jentic, an agent can call SqlManagementClient to retrieve the live schema, table, and column definitions for the target database, then ground its generated query in real identifiers. Jentic isolates the Azure OAuth credentials so the agent never handles a refresh token directly.

Use Jentic to load the SqlManagementClient list-columns operation, then call it for the table 'invoices' in schema 'finance' and pass the returned column names to the SQL generation step.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas

List schemas in a database

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}

Get a specific database schema

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables

List tables in a schema

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables/{tableName}

Get a specific table

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables/{tableName}/columns

List columns in a table

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables/{tableName}/columns/{columnName}

Get a specific column definition

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas

List schemas in a database

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}

Get a specific database schema

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables

List tables in a schema

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables/{tableName}

Get a specific table

Why Jentic?

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

Credential isolation

Azure AD OAuth tokens for SqlManagementClient are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived access tokens at execution time — refresh tokens and client secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'list columns in an azure sql table') and Jentic returns the matching SqlManagementClient operation with its full input schema, so the agent can call the right endpoint without browsing Azure docs.

Time to first call

Direct integration with Azure Resource Manager OAuth, tenant configuration, and SDK setup typically takes 1-2 days. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using SqlManagementClient API through Jentic.

Why is there no official OpenAPI spec for SqlManagementClient?

Microsoft Azure publishes Swagger fragments for individual ARM services but does not publish a consolidated, validated OpenAPI 3 spec for the SqlManagementClient schema-introspection surface. Jentic generates and maintains this spec so that AI agents and developers can call SqlManagementClient via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the SqlManagementClient use?

All endpoints require Azure Active Directory OAuth 2.0, declared as the azure_auth security scheme in the spec with the user_impersonation scope against https://login.microsoftonline.com. Through Jentic, the Azure access token is held in the Jentic vault and injected at call time so the agent never sees the raw bearer token.

Can I list every table in an Azure SQL database with SqlManagementClient?

Yes. Call GET on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/schemas/{schemaName}/tables to enumerate tables under a specific schema. To cover the whole database, first list schemas, then iterate this call per schema.

What are the rate limits for the SqlManagementClient?

Calls go through Azure Resource Manager, which applies subscription-level read throttling (typically 12,000 reads per hour per subscription, varying by region and tenant). Throttled responses return HTTP 429 with a Retry-After header; the spec does not encode these limits, so handle them in client code.

How do I introspect Azure SQL columns through Jentic?

Run pip install jentic, search Jentic for 'list columns of an azure sql table', load the SqlManagementClient list-columns operation schema, then execute it with subscriptionId, resourceGroupName, serverName, databaseName, schemaName, and tableName. Jentic returns the column metadata directly without you handling the Azure AD token.

Does SqlManagementClient let me run SQL queries against the database?

No. This is a control-plane API for schema metadata only. To execute queries you connect to the database over TDS using a SQL driver. Use SqlManagementClient first to discover the structure, then use that information to compose data-plane queries.