Microsoft Azure Azure SQL Database disaster recovery configurations
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth26 EndpointsREST
For Agents
Provision, inspect, and trigger failover on Azure SQL Database disaster recovery configurations across paired regions.
Use for: I need to fail over an Azure SQL Database to its secondary region, Check whether a SQL server has a disaster recovery configuration, Set up a disaster recovery pairing between two Azure SQL servers, Force a failover that allows data loss for an unreachable primary
Not supported: Does not handle database query, schema management, or backup restore — use for server-level disaster recovery pairings and failover only.
Jentic publishes the only available OpenAPI specification for Azure SQL Database disaster recovery configurations, keeping it validated and agent-ready. The API provisions and manages disaster recovery configurations on Azure SQL Database servers, allowing agents to inspect a server's DR configuration, create or remove a recovery pairing, and trigger failover or forced failover that allows data loss. It targets the Microsoft.Sql resource provider on the Azure Resource Manager control plane and is intended for high-availability automation across regions, not for routine database query or schema work.
Install Jentic One Beta
Connect the Azure SQL Database disaster recovery configurations to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure SQL Database disaster recovery configurations, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Azure SQL Database disaster recovery configurations API.
Retrieve the disaster recovery configuration attached to a SQL server
Create or update a named disaster recovery pairing between two SQL servers
Delete a disaster recovery configuration to break the pairing
Trigger a planned failover to the secondary region
Force failover with potential data loss when the primary is unreachable
Audit current DR pairings across a subscription's SQL servers
Use Cases
Patterns agents use Azure SQL Database disaster recovery configurations API for, with concrete tasks.
★ Cross-region failover for Azure SQL
Trigger a planned failover of an Azure SQL Database to its paired region during a regional outage or disaster recovery drill. The API exposes a dedicated failover operation under the disasterRecoveryConfiguration resource and a separate forceFailoverAllowDataLoss operation for unreachable primaries. Use this when an operator or automation needs to switch traffic to the secondary within minutes without rebuilding replication from scratch.
POST to /subscriptions/{subscriptionId}/resourceGroups/{rg}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{drcName}/failover and confirm the configuration status returns to Ready
Provision a DR pairing for a new SQL server
Create a named disaster recovery configuration that pairs a primary Azure SQL server with a secondary in another region. The PUT operation on disasterRecoveryConfiguration/{disasterRecoveryConfigurationName} establishes the pairing as part of an environment bring-up workflow. Use this to bake DR into infrastructure-as-code provisioning rather than configuring it manually after the fact.
PUT a disasterRecoveryConfiguration named primary-to-secondary on serverA and verify the resource appears in the GET list for that server
DR readiness audit
Walk every SQL server in a subscription and report which have a disaster recovery configuration attached and which do not. The GET operation on the disasterRecoveryConfiguration collection returns the current pairing if one exists, making it the source of truth for compliance audits. Useful for compliance teams who need to evidence that production servers have DR in place.
Iterate over every SQL server in subscriptionId X, GET its disasterRecoveryConfiguration, and emit a CSV of servers missing a DR pairing
Agent-driven incident response
Allow an AI agent to respond to a regional outage alert by checking DR state and initiating failover without a human operator. Through Jentic, the agent searches for the failover operation by intent, loads the input schema, and executes against the right resource path with scoped credentials. Removes the need to memorise long Microsoft.Sql resource paths.
Search Jentic for 'fail over azure sql disaster recovery configuration', load the operation schema, and execute against the named DR configuration
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for azure sql database disaster recovery configurations, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration
List DR configurations on a server
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}
Get a named DR configuration
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}
Create or update a DR pairing
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}
Delete a DR pairing
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}/failover
Trigger planned failover to secondary
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}/forceFailoverAllowDataLoss
Force failover with possible data loss
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration
List DR configurations on a server
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}
Get a named DR configuration
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}
Create or update a DR pairing
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}
Delete a DR pairing
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}/failover
Trigger planned failover to secondary
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/disasterRecoveryConfiguration/{disasterRecoveryConfigurationName}/forceFailoverAllowDataLoss
Force failover with possible data loss
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, short-lived 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., 'fail over azure sql database') and Jentic returns the matching Microsoft.Sql disasterRecoveryConfiguration operation with its full input schema, so the agent does not need to memorise the long resource path.
Time to first call
Direct ARM integration: 1-3 days for AAD app registration, token exchange, long-running operation polling, and error handling. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure SQL Database disaster recovery configurations API through Jentic.
Why is there no official OpenAPI spec for Azure SQL Database disaster recovery configurations?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure SQL Database disaster recovery configurations 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 Database disaster recovery configurations 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, so raw refresh tokens never enter the agent's context.
Can I trigger a failover with this API?
Yes. Two POST operations exist: /failover for a planned switch to the secondary and /forceFailoverAllowDataLoss for the case where the primary is unreachable. Both target a named disasterRecoveryConfiguration on a specific Microsoft.Sql server.
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, with subresource limits documented per provider. DR failover operations are long-running and return 202 Accepted; poll the Azure-AsyncOperation header to track completion.
How do I create a DR pairing through Jentic?
Run pip install jentic, then search for 'configure azure sql disaster recovery'. Jentic returns the PUT operation on /disasterRecoveryConfiguration/{name}, loads the request schema, and executes it with the subscription, resource group, and server names you supply.
Does this API work for Azure SQL Managed Instance?
No. This spec covers disaster recovery configurations on Microsoft.Sql/servers only. Managed Instance disaster recovery uses a separate failover groups API under the same provider.
GET STARTED