Azure SQL Database Backup Long Term Retention Policy

Name: Azure SQL Database Backup Long Term Retention Policy API
Brand: Azure SQL Database Backup Long Term Retention Policy
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth23 EndpointsREST

For Agents

Quickstart

Get started with Azure SQL Database Backup Long Term Retention Policy 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 ltr policies on a database"

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

Capabilities

What an agent can do with Azure SQL Database Backup Long Term Retention Policy API.

Read the long-term retention policy currently applied to an Azure SQL database

Create or update the long-term retention policy with a recoveryServicesBackupPolicyResourceId

List the backup long-term retention policies attached to a single database

Wire LTR policies into infrastructure-as-code so retention is provisioned with the database

GET STARTED

Start building with Azure SQL Database Backup Long Term Retention Policy API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Azure SQL Database Backup Long Term Retention Policy, keeping it validated and agent-ready. The API reads and updates the long-term retention policy applied to a single Azure SQL database, the policy that pins backups beyond the default short-term retention window. It exposes 3 endpoints under Microsoft.Sql for listing the policy on a database, getting a named policy, and creating or updating one.

Use Cases

Patterns agents use Azure SQL Database Backup Long Term Retention Policy API for, with concrete tasks.

★ Apply LTR Policy as Part of Database Provisioning

After creating an Azure SQL database, attach a long-term retention policy by PUTting to /backupLongTermRetentionPolicies/{backupLongTermRetentionPolicyName} with the recoveryServicesBackupPolicyResourceId of an existing Recovery Services vault policy. This pins backups for years rather than the default 7-35 day short-term window, satisfying compliance regimes that mandate multi-year retention. The single API call is the standard way to apply LTR in IaC pipelines.

PUT a backup long-term retention policy on database 'orders-db' under server 'prod-sql-eus' referencing the recovery services backup policy id 'arm-id-of-vault-policy'

Audit LTR Coverage Across a Subscription

Walk the SQL servers and databases in a subscription, GET the LTR policy on each, and flag any database whose policy is missing or points at a deprecated vault. The list endpoint returns the policies attached to a single database, and an aggregated audit identifies coverage gaps before an external compliance review. Pair with PUT to remediate gaps in the same automation pass.

List the LTR policies for every database under server 'prod-sql-eus' and emit a report flagging any database without a configured policy

Re-point LTR to a New Recovery Services Vault Policy

When a Recovery Services vault retention policy is replaced, update each database's LTR policy to reference the new id so retention continues uninterrupted. PUT on /backupLongTermRetentionPolicies/{name} with the new recoveryServicesBackupPolicyResourceId atomically swaps the link without losing prior backups. This pattern supports vault consolidation projects and policy rationalisation across business units.

Update the LTR policy on database 'orders-db' to reference the new recovery services backup policy id 'arm-id-of-new-vault-policy'

Agent-Driven LTR Compliance via Jentic

An AI agent uses Jentic to enforce LTR coverage policy: enumerating databases, reading their LTR policies, and applying a default policy where coverage is missing. The agent searches Jentic for 'list azure sql ltr policies on a database', loads the schema, and chains the response into PUT operations where required. Azure AD bearer tokens are sourced from the Jentic vault per call.

Search Jentic for 'list azure sql ltr policies on a database', list policies on every database under server 'prod-sql-eus', and PUT the default LTR policy on any that lack one

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for azure sql database backup long term retention policy, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

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

Get a long-term retention policy on a database

PUT

Create or update a long-term retention policy

GET

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

List long-term retention policies on a database

GET

Get a long-term retention policy on a database

PUT

Create or update a long-term retention policy

GET

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

List long-term retention policies on a database

Why though Jentic?

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

Credential isolation

Azure AD client credentials are stored encrypted in the Jentic vault. A short-lived bearer token scoped to https://management.azure.com/ is fetched per call; raw client secrets and refresh tokens never reach the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'enable ltr on an azure sql database') and receive the matching Microsoft.Sql backupLongTermRetentionPolicies operation with its full input schema so the agent calls the right endpoint without browsing the ARM reference.

Time to first call

Direct integration: half a day for ARM auth and PUT/GET wiring against Microsoft.Sql. Through Jentic: under an hour from search to first successful call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure SQL Database Backup

Manages short-term backups and restore operations on Azure SQL databases.

Use this for short-term automated backups and point-in-time restore; LTR pins backups beyond the short-term window.

Complementary

Azure SQL Database Disaster Recovery Configuration

Configures failover groups and disaster recovery on Azure SQL databases.

Use alongside LTR when the agent needs to configure DR replication in addition to long-term backup retention.

Complementary

Azure SQL Database (checkNameAvailability)

Validates Azure SQL server names before provisioning the server that hosts the database.

Use during provisioning before a database exists; this LTR API operates on already-provisioned databases.

FAQs

Specific to using Azure SQL Database Backup Long Term Retention Policy API through Jentic.

Why is there no official OpenAPI spec for Azure SQL Database Backup Long Term Retention Policy?

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 Backup Long Term Retention Policy 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 Backup Long Term Retention Policy API use?

The API uses Azure Active Directory OAuth 2.0 (the azure_auth scheme) with the user_impersonation scope on https://management.azure.com/. Through Jentic, the bearer token is fetched from the Jentic vault and injected at call time so the agent never sees the raw client secret.

How do I attach a long-term retention policy to an existing Azure SQL database?

PUT to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/backupLongTermRetentionPolicies/{backupLongTermRetentionPolicyName} with a body that includes the recoveryServicesBackupPolicyResourceId of an existing Recovery Services vault policy.

What are the rate limits for the Azure SQL Database Backup Long Term Retention Policy API?

The spec does not declare per-API limits; calls are throttled by Azure Resource Manager's per-subscription budget for read and write operations on Microsoft.Sql. On HTTP 429, honour the Retry-After header before retrying.

How do I list LTR policies on a database through Jentic?

Search Jentic for 'list azure sql ltr policies on a database', load the schema for GET /servers/{serverName}/databases/{databaseName}/backupLongTermRetentionPolicies, and execute it. Jentic injects the Azure AD bearer token automatically.

Is the Azure SQL LTR API free?

Control plane calls are free. The underlying long-term retention storage is billed against the Recovery Services vault that the policy references, at standard Azure backup storage rates.