Azure SQL Server Backup Long Term Retention Vault

Name: Azure SQL Server Backup Long Term Retention Vault API
Brand: Azure SQL Server Backup Long Term Retention Vault
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth23 EndpointsREST

For Agents

Quickstart

Get started with Azure SQL Server Backup Long Term Retention Vault 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:
"register a long term retention vault for an azure sql server"

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

Capabilities

What an agent can do with Azure SQL Server Backup Long Term Retention Vault API.

List backup long-term retention vaults registered on a SQL server

Retrieve a specific named vault registration on a server

Update the vault used for long-term retention on a server

GET STARTED

Start building with Azure SQL Server Backup Long Term Retention Vault API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Azure SQL Server Backup Long Term Retention Vault, keeping it validated and agent-ready. The API associates an Azure SQL logical server with a Recovery Services vault that holds long-term retention backups, letting agents list current vault associations, retrieve a specific vault registration, or attach a new vault to a server. It targets the Microsoft.Sql resource provider on Azure Resource Manager and is intended for compliance and retention workflows that exceed the default backup window.

Use Cases

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

★ Enable long-term backup retention for compliance

Register a Recovery Services vault on a SQL server so that database backups can be retained for years rather than the default 35 days. The PUT /backupLongTermRetentionVaults/{vaultName} operation associates a vault id with the server in a single call. Required for industries with long retention mandates such as financial services and healthcare.

PUT /servers/{serverName}/backupLongTermRetentionVaults/RetentionVault with the recoveryServicesVaultResourceId and verify the GET returns the new association

Compliance audit of LTR coverage

Walk every SQL server in a subscription and report which have an LTR vault registered and which fall back to the default backup window. The GET /backupLongTermRetentionVaults collection returns each server's vault association in a single call. Output supports auditor reports demonstrating retention coverage.

Iterate every SQL server in subscriptionId X, GET its backupLongTermRetentionVaults, and emit a CSV of servers without a registered vault

Re-target backups to a new vault

Move LTR backups for a server to a different Recovery Services vault, for example to consolidate vaults across regions or migrate from a legacy vault. The same PUT operation accepts the new vault id, replacing the existing association. Use during vault consolidation initiatives.

PUT /servers/{serverName}/backupLongTermRetentionVaults/RetentionVault with the new recoveryServicesVaultResourceId and verify the previous vault no longer appears in the GET list

Agent-driven retention setup

Let an AI agent register an LTR vault as part of an environment bring-up workflow without an operator hand-coding the long ARM URL. Through Jentic the agent searches by intent, loads the vault id schema, and executes the PUT. Removes a class of typos when constructing nested resource paths.

Search Jentic for 'register long term retention vault azure sql', load the vault association schema, and execute against the named server

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

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

List LTR vaults on a SQL server

GET

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

Get a named vault registration

PUT

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

GET

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

List LTR vaults on a SQL server

GET

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

Get a named vault registration

PUT

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

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., 'register long term retention vault') and Jentic returns the matching Microsoft.Sql backupLongTermRetentionVaults operation with the vault id schema, so the agent does not need to construct the long ARM path manually.

Time to first call

Direct ARM integration: 1-2 days for AAD app registration, vault id discovery, and async polling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure SQL Database backup

Manages individual database backups that the LTR vault retains

Use the backup API for restore points; use the LTR vault API to set the storage target

Alternative

Azure SQL Database Import/Export spec

Customer-managed BACPAC archives in Blob Storage rather than vault-based retention

Choose import/export for portable customer-managed archives; choose LTR vault for managed compliance retention

Complementary

Azure SQL Database backup long-term retention policy

Defines the per-database retention policy that uses the registered vault

Pair the policy API with the vault API: register the vault, then attach a retention policy to a database

FAQs

Specific to using Azure SQL Server Backup Long Term Retention Vault API through Jentic.

Why is there no official OpenAPI spec for Azure SQL Server Backup Long Term Retention Vault?

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 Backup Long Term Retention Vault 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 this 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 register more than one vault on a server?

At this API version (2014-04-01) the backupLongTermRetentionVaults collection holds a single named registration per server, addressed as /backupLongTermRetentionVaults/{backupLongTermRetentionVaultName}. Subsequent versions of the broader long-term retention API expose richer policy controls.

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. The PUT operation may return 202 Accepted; track completion via the Azure-AsyncOperation header.

How do I register a vault through Jentic?

Run pip install jentic, then search for 'register long term retention vault azure sql'. Jentic returns the PUT /backupLongTermRetentionVaults/{name} operation, loads the recoveryServicesVaultResourceId schema, and executes against the server you specify.

Does this API trigger or restore individual backups?

No. This API only manages the vault association on a SQL server. Triggering a backup, listing recovery points, or restoring to a point in time is handled by the related backup and Recovery Services APIs.