Azure SQL Database Backup

Name: Azure SQL Database Backup API
Brand: Azure SQL Database Backup
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth24 EndpointsREST

For Agents

Inspect recoverable and restorable-dropped Azure SQL databases so an agent can discover which backups exist before triggering a restore.

Quickstart

Get started with Azure SQL Database Backup in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list azure sql recoverable databases"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Azure SQL Database Backup API.

List recoverable databases that have geo-redundant backups available on a given Azure SQL Server

Retrieve a specific recoverable database resource representing a database's geo backup

List restorable dropped databases on a server within their retention window

Get metadata for a single restorable dropped database including deletion date and earliest restore date

GET STARTED

Start building with Azure SQL Database Backup API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Azure SQL Database Backup, keeping it validated and agent-ready.

The Azure SQL Database Backup API provides read access to recoverable databases and restorable dropped databases under Azure SQL Server resources. Agents can list geo-redundant backups available for recovery, retrieve backup metadata for specific databases, and inspect dropped databases that remain restorable within their retention window. The API exposes 4 GET operations under the Microsoft.Sql resource provider and is intended for disaster-recovery discovery and audit workflows on Azure SQL Server.

Use Cases

Patterns agents use Azure SQL Database Backup API for, with concrete tasks.

★ Disaster Recovery Inventory

Before initiating a restore, an operations team needs to know which Azure SQL databases on a server have recoverable geo backups and which dropped databases are still within their restore window. This API returns recoverable database listings and per-database backup metadata under the Microsoft.Sql/servers resource path, scoped to a subscription and resource group. It is read-only and complements the broader Azure SQL Database management API used to perform the actual restore.

List all restorable dropped databases for resource group sales-prod on server sales-sql-east, and return any whose earliestRestoreDate is within the last 7 days

Compliance Audit of Backup Coverage

Compliance reviewers need evidence that production databases have valid geo-redundant backups. The recoverableDatabases endpoints surface lastAvailableBackupDate, edition, and serviceLevelObjective per database, which auditors can compare against retention SLOs. Read-only, no mutation risk during an audit pass.

For every database under server finance-sql-prod, fetch the recoverableDatabase resource and flag any whose lastAvailableBackupDate is older than 24 hours

Pre-Restore Validation by AI Agent

An AI agent handling a restore request first verifies the target database is actually restorable before invoking the disaster-recovery configuration or restore operation in the broader SQL management API. Through Jentic, the agent searches for backup-inspection operations, loads the schema, and calls RecoverableDatabases_Get or RestorableDroppedDatabases_Get to confirm eligibility, returning the earliestRestoreDate to the user.

Verify that database orders-prod on server orders-sql-east is recoverable and return its lastAvailableBackupDate and serviceLevelObjective

Key Endpoints

4 endpoints — the azure sql database backup api provides read access to recoverable databases and restorable dropped databases under azure sql server resources.

METHOD

PATH

DESCRIPTION

GET

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

List recoverable databases on a server

GET

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

Get a specific recoverable database

GET

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

List restorable dropped databases on a server

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/restorableDroppedDatabases/{restorableDroppededDatabaseId}

Get a specific restorable dropped database

GET

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

List recoverable databases on a server

GET

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

Get a specific recoverable database

GET

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

List restorable dropped databases on a server

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/restorableDroppedDatabases/{restorableDroppededDatabaseId}

Get a specific restorable dropped database

Why though Jentic?

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

Credential isolation

Azure AD OAuth 2.0 tokens are stored in the Jentic vault. Agents never see the user_impersonation token — Jentic injects it at execution time and rotates on expiry.

Intent-based discovery

An agent searches Jentic with 'list azure sql recoverable databases' and Jentic returns the RecoverableDatabases_ListByServer operation with its full input schema, so the agent calls it without parsing Azure ARM docs.

Time to first call

Direct Azure ARM integration: 1-2 days to wire up MSAL, token refresh, and ARM error handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure SQL Database

Full Azure SQL Database management API used to perform restores after backup discovery

Use this when the agent needs to actually restore or create a database from a backup identified by the Backup API

Complementary

Azure SQL Database Backup Long Term Retention Policy

Manages long-term retention policies that govern which backups remain available

Use when the agent needs to read or update the retention policy that determines what this Backup API can return

Complementary

Azure SQL Database disaster recovery configurations

Manage geo-replication and failover groups on Azure SQL Server

Use when the agent needs to configure or trigger failover for a server whose backup state was inspected via this API

Alternative

SQL Management Client

Newer consolidated Azure SQL management API covering backups across recent API versions

Choose this when the agent needs current API-version backup operations beyond the 2014-04-01 surface area

FAQs

Specific to using Azure SQL Database Backup API through Jentic.

What authentication does the Azure SQL Database Backup API use?

It uses Azure Active Directory OAuth 2.0 (the azure_auth scheme with the implicit flow and the user_impersonation scope at https://login.microsoftonline.com/common/oauth2/authorize). Through Jentic, the OAuth token is held in the vault and never exposed to the agent — the agent receives a scoped execution token instead.

Can I trigger a restore with the Azure SQL Database Backup API?

No. This API is read-only — it exposes 4 GET endpoints on RecoverableDatabases and RestorableDroppedDatabases for discovery only. To perform an actual restore or failover, use the broader Azure SQL Database management API or the disaster-recovery configurations API.

What are the rate limits for the Azure SQL Database Backup API?

The API is governed by Azure Resource Manager throttling: typically 12,000 read requests per hour per subscription and per region, with 429 responses including a Retry-After header. Limits are shared across all Microsoft.Sql operations in the subscription.

How do I list recoverable databases through Jentic?

Run pip install jentic, then search Jentic with the query 'list azure sql recoverable databases'. Jentic returns the RecoverableDatabases_ListByServer operation on the path /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/recoverableDatabases. Load its schema and execute with subscriptionId, resourceGroupName, and serverName.

What backup metadata does this API return?

For recoverable databases: edition, elasticPoolName, lastAvailableBackupDate, and serviceLevelObjective. For restorable dropped databases: creationDate, databaseName, deletionDate, earliestRestoreDate, edition, elasticPoolName, maxSizeBytes, and serviceLevelObjective.

Is the Azure SQL Database Backup API free?

The control-plane API itself does not incur direct call charges, but the underlying SQL Database service and its geo-redundant backup storage are billed per the database tier and storage consumed. See the Azure SQL Database pricing page for current rates.