Azure SQL Database Import/Export spec

Name: Azure SQL Database Import/Export spec API
Brand: Azure SQL Database Import/Export spec
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth23 EndpointsREST

For Agents

Export Azure SQL databases to BACPAC files in Blob Storage and import BACPACs back into new or existing databases.

Quickstart

Get started with Azure SQL Database Import/Export spec 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:
"export an azure sql database to a bacpac"

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

Capabilities

What an agent can do with Azure SQL Database Import/Export spec API.

Export an Azure SQL database to a BACPAC file in Azure Blob Storage

Import a BACPAC file from Blob Storage into a new Azure SQL database

Provide storage account credentials inline with the export request

GET STARTED

Start building with Azure SQL Database Import/Export spec API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Azure SQL Database Import/Export spec, keeping it validated and agent-ready. The API drives BACPAC-based import and export operations on Azure SQL Database, letting agents export a database to Azure Blob Storage, import a BACPAC into a new database, or register an extension that tracks the operation. It targets the Microsoft.Sql resource provider on Azure Resource Manager and is intended for migration, archival, and environment-cloning workflows rather than live data access.

Use Cases

Patterns agents use Azure SQL Database Import/Export spec API for, with concrete tasks.

★ Scheduled BACPAC export for archival

Run a nightly export of an Azure SQL database to Azure Blob Storage so the BACPAC sits alongside long-term retention backups in a separate storage account. The POST /databases/{databaseName}/export operation accepts inline storage credentials and returns an operation handle that callers poll until the BACPAC is written. Useful for compliance-driven archival where point-in-time backups alone are insufficient.

POST to /databases/{databaseName}/export with the target storage URI, key type, and admin credentials, then poll the returned operation until status is Succeeded

Environment cloning via BACPAC import

Clone a production database into a development or staging environment by importing a previously exported BACPAC into a freshly provisioned database. The PUT /servers/{serverName}/import operation creates the target database and loads the BACPAC in one call. This is the canonical pattern for spinning up isolated test environments without exposing them to production traffic.

PUT to /servers/{serverName}/import with the source BACPAC URI, target database name, edition Standard, and serviceObjective S1, then verify the new database appears in the server's database list

Cross-subscription database migration

Move a database between Azure subscriptions by exporting it to a shared blob container, then importing into a server in the destination subscription. The same import/export operations work in both directions, with the storage URI acting as the handoff point. Avoids the more complex geo-replication or DMS flows when a one-time migration is enough.

Export source database to blob://migration/db.bacpac, then issue PUT /servers/{newServerName}/import in the destination subscription pointing at the same URI

Agent-driven backup and restore

Let an AI agent execute a one-shot export or import in response to a developer request, without needing to know the exact ARM resource path or storage credential format. Through Jentic, the agent searches for the export operation, loads the storage URI and credential schema, and executes the call. Removes the need for ad hoc PowerShell or az CLI scripting.

Search Jentic for 'export azure sql database to bacpac', load the storage credential schema, and execute against the target database

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for azure sql database import/export spec, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

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

Export a database to a BACPAC in Blob Storage

POST

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

Import a BACPAC into a new database

PUT

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

POST

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

Export a database to a BACPAC in Blob Storage

POST

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

Import a BACPAC into a new database

PUT

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

Why though Jentic?

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

Credential isolation

Azure AD OAuth tokens and storage account keys are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens at execution time — storage keys are referenced by handle, never inlined into the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'export azure sql database') and Jentic returns the matching Microsoft.Sql import or export operation with its storage credential schema, so the agent does not need to assemble the long ARM path manually.

Time to first call

Direct ARM integration: 1-2 days for AAD app registration, storage credential plumbing, 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 point-in-time backups for the same databases this API exports

Choose backup for in-place point-in-time restore; choose import/export for portable BACPAC archives

Complementary

Azure SQL Database

Provisions the SQL databases that import/export operates against

Use the database API to provision the target server before importing a BACPAC into it

Alternative

Azure SQL Server Backup Long Term Retention Vault

Stores backups in a managed retention vault rather than BACPAC files

Pick the LTR vault for compliance-grade retention; pick import/export for portable, customer-managed BACPAC files

FAQs

Specific to using Azure SQL Database Import/Export spec API through Jentic.

Why is there no official OpenAPI spec for Azure SQL Database Import/Export 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 Database Import/Export 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 Database Import/Export 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 so service principal secrets never enter the agent's context.

Can I export a database to my own storage account with this API?

Yes. The POST /databases/{databaseName}/export request accepts a storageUri, storageKeyType (StorageAccessKey or SharedAccessKey), and storageKey, plus the admin login and password. The BACPAC is written to the URI you supply.

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. Import and export are long-running operations that return 202 Accepted; track completion via the Azure-AsyncOperation header rather than retrying.

How do I run a BACPAC import through Jentic?

Run pip install jentic, then search for 'import bacpac azure sql'. Jentic returns the PUT /servers/{serverName}/import operation, loads the storage credential and database settings schema, and executes against your target server.

Does this API restore from automated backups?

No. This API works with BACPAC files in Blob Storage only. For point-in-time restore from Azure-managed backups, use the azure-sql-database-backup API on the same Microsoft.Sql provider.