Azure SQL Server API spec

Name: Azure SQL Server API spec API
Brand: Azure SQL Server API spec
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth22 EndpointsREST

For Agents

Read or update the connection policy (Default, Proxy, or Redirect routing) on an Azure SQL logical server.

Connect the Azure SQL Server API spec to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Azure SQL Server API spec API.

Retrieve the current connection policy on a SQL server

Set the connection policy to Default, Proxy, or Redirect

Switch a server from Proxy to Redirect for lower latency

Audit connection policy across servers in a subscription

GET STARTED

Start building with Azure SQL Server API spec API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Azure SQL Server API spec, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Azure SQL Server API spec, keeping it validated and agent-ready. The API manages the connection policy on an Azure SQL logical server, letting agents read or update whether the server uses Default, Proxy, or Redirect connection routing for clients. It targets the Microsoft.Sql resource provider on Azure Resource Manager and is intended for low-latency or hybrid-network configurations rather than database, login, or firewall management.

Use Cases

Patterns agents use Azure SQL Server API spec API for, with concrete tasks.

★ Lower client latency by switching to Redirect

Switch a SQL server from the default Proxy mode to Redirect so clients connect straight to the database node after the initial gateway handshake. The PUT /connectionPolicies/{connectionPolicyName} operation flips the mode in a single call. Useful when application latency budgets cannot absorb the extra hop through the Azure SQL gateway.

PUT /servers/{serverName}/connectionPolicies/Default with connectionType set to Redirect and verify the GET returns the new value

Force Proxy mode for restricted networks

Set a SQL server to Proxy mode so that all client traffic flows through the Azure SQL gateway, simplifying firewall rules in environments that cannot reach individual node IPs. The same PUT operation accepts Proxy as a value. This is the canonical configuration for clients behind strict outbound firewalls.

PUT /servers/{serverName}/connectionPolicies/Default with connectionType Proxy and confirm subsequent GET returns Proxy

Connection policy compliance audit

Walk every SQL server in a subscription and report which use Proxy versus Redirect, supporting compliance teams that mandate one mode for security or latency reasons. The GET /connectionPolicies/{connectionPolicyName} operation returns the current setting in a single call per server. Output feeds a Power BI or CSV report.

Iterate every SQL server in subscriptionId X, GET /connectionPolicies/Default, and emit a CSV grouped by connectionType

Agent-driven server configuration

Let an AI agent flip a SQL server's connection policy in response to a latency alert or network change without an operator hand-writing the ARM URL. Through Jentic the agent searches by intent, loads the policy schema, and executes the PUT. Removes a class of typos on the long Microsoft.Sql resource path.

Search Jentic for 'set azure sql server connection policy', load the connectionType enum schema, and execute against the named server

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for azure sql server api spec, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/connectionPolicies/{connectionPolicyName}

Get the server connection policy

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/connectionPolicies/{connectionPolicyName}

Update the server connection policy

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/connectionPolicies/{connectionPolicyName}

Get the server connection policy

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/connectionPolicies/{connectionPolicyName}

Update the server connection policy

Why though 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., 'set azure sql server connection policy') and Jentic returns the matching Microsoft.Sql connectionPolicies operation with its enum schema, so the agent does not need to memorise the long ARM resource path.

Time to first call

Direct ARM integration: 1-2 days for AAD app registration and ARM client setup. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure SQL Database

Manages the databases that sit on the server whose connection policy this API controls

Use the database API for database-level operations; use this API for server-level connection routing

Complementary

Azure SQL Database disaster recovery configurations

Manages DR pairings on the same SQL server resource

Pair with this API when configuring connection policy alongside DR setup during server bring-up

Complementary

Azure SQL Database replication links

Manages per-database replication on databases hosted by the server

Use replication links for database-level geo-replication; use this API for server-wide connection routing

FAQs

Specific to using Azure SQL Server API spec API through Jentic.

Why is there no official OpenAPI spec for Azure SQL Server API spec?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure SQL Server API spec 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 the Azure SQL Server connection policy 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 read the connection policy without changing it?

Yes. GET /servers/{serverName}/connectionPolicies/{connectionPolicyName} returns the current connectionType value (Default, Proxy, or Redirect) without side effects. The connectionPolicyName is always Default at this API version.

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. Connection policy writes are quick and synchronous; expect a 200 response rather than 202.

How do I update the connection policy through Jentic?

Run pip install jentic, then search for 'set azure sql server connection policy'. Jentic returns the PUT /connectionPolicies/Default operation, loads the connectionType enum schema, and executes against the server you specify.

Does this API manage firewall rules or logins?

No. This API only handles the server-level connection policy. Firewall rules, logins, and database management live under separate Microsoft.Sql resources with their own APIs.