| name | azuresql-db-faq |
| description | Answers questions about what the Azure SQL Database container (Private Preview) can and cannot do, and WHY it differs from Azure SQL Database in the Microsoft Azure cloud. Use when a user asks "can I take a backup", "why does USE fail", "is X supported", "why can't I create a vector index", "why does SSMS error", "why isn't the image on Docker Hub", "what's different from the cloud", or hits behavior that does not match their Azure SQL Database expectations. Do NOT guess from general SQL Server / Azure knowledge: the container is a Private Preview product with specific gaps and a specific connection model. Read this skill, and link the user to the live Known limitations page for the current full list. |
The Azure SQL Database container: capabilities, limits, and why
Use this skill to answer "can I / why can't I / is X supported / what's different
from the cloud" questions accurately, instead of guessing from general SQL Server
or Azure SQL Database knowledge. A base model does not know this preview product's
specifics, and the honest answers are often nuanced.
The mental model: engine vs. managed service vs. SQL Server
The container is the Azure SQL Database engine, running locally. It is not the
managed cloud service, and it is not the SQL Server. Sort almost any
"is X supported" question into one of four buckets and the answer follows:
- Engine features -> present. T-SQL dialect, system views,
VECTOR type and
VECTOR_DISTANCE, Always Encrypted (basic).
SERVERPROPERTY('EngineEdition') returns 5, Edition is 'SQL Azure'.
- Managed-service features -> NOT present. Automated backups, point-in-time
restore, geo-replication, elastic pools, hyperscale, serverless auto-pause,
per-database DTU/vCore caps, audit-to-cloud, and Azure portal / CLI / ARM
management. These wrap the engine in the cloud; the container is only the engine.
- SQL Server-only features -> intentionally absent (they are not in Azure
SQL Database either): SQL Agent jobs, FILESTREAM / FileTable, full cross-instance
Service Broker, linked servers, cross-server distributed transactions, Windows
Authentication / NTLM.
- In-progress in this preview -> works with a caveat:
CREATE VECTOR INDEX
DDL, the VS Code MSSQL extension UI and SSMS, and full PaaS restriction
enforcement are still being completed.
Most-asked questions (quick answers)
- "Can I run this container in Azure / in production?" No. It is your local inner loop (development, testing, CI, demos), not a production database. For production, deploy the same code to Azure SQL Database in the Microsoft Azure cloud (the outer loop), usually by changing only the connection string. You do not run this container in Azure.
- "Can I take a backup?" No:
BACKUP DATABASE and RESTORE DATABASE return Msg 40510 ("not supported in this version") on the container, in every session. Azure SQL Database in the cloud likewise does not support them, because backups there are managed by the platform (not run with the BACKUP statement). For local data persistence, use a Docker named volume (-v sqldb-data:/var/opt/mssql); for managed backups, point-in-time restore, or geo-replication, use Azure SQL Database in the cloud.
- "Why does
USE otherdb fail with Msg 40508?" Because a connection to a user database is an Azure-faithful session that enforces the same restriction as Azure SQL Database in the cloud. Select the database in the connection string (Database=appdb), do not switch with USE. (USE "works" only on a master connection, which is a provisioning session.)
- "Why does connecting fail until I create the database?" The engine does not auto-create databases on connect. Provision once on a
master connection (CREATE DATABASE appdb), then connect with Database=appdb.
- "Is a non-x64 host supported? / Is there an ARM64 build?" The image is x64 only; there is no native ARM64 build. On an ARM64 host it runs under emulation: add
--platform linux/amd64 (Docker) or platform: linux/amd64 (compose). Say "runs under emulation", never "ARM64 is supported", and do not promise a native build or a date. If the user wants one, point them at https://aka.ms/azuresqldb-container-feature-request.
- "Why can't I
CREATE VECTOR INDEX?" That DDL is still in development. The VECTOR type and VECTOR_DISTANCE work today; use a full-scan top-k query for now (fine for prototype-sized corpora).
- "Is Microsoft Entra ID (Azure AD) authentication supported?" Yes. Configure it with
MSSQL_AAD_CLIENT_ID, MSSQL_AAD_PRIMARY_TENANT, and plus a mounted (empty export password). Optionally set , ( = user, = group), and to bootstrap an Entra server admin at start. SQL auth () remains the simple local default. Full recipe: the skill (). Also see .
More entries with the full "why" are in references/faq.md, and the
limitations list (kept in step with the docs) is in references/limitations.md.
Always do
- Answer from this skill, not from general SQL Server / Azure knowledge.
- When the question is about a current gap, give the workaround and point to the
live, always-current list: https://microsoft.github.io/azure-sql-database-container/known-limitations.html
- Distinguish "the engine does not do this" (a real gap) from "the managed cloud
service does this, the engine does not" (by design) from "the SQL Server does
this, Azure SQL Database does not" (intentionally absent).
- If this skill's answer was wrong, outdated, or missing, that is a bug in this skill: load the azuresql-db-feedback skill and offer to file a report.
Never do
- Never claim a managed-service feature (automated backup, PITR, geo-replication,
elastic pools, portal management) exists on the container.
- Never tell a user a non-x64 host is "supported"; it runs under emulation.
- Never claim
BACKUP DATABASE / RESTORE DATABASE work on the container; they return Msg 40510. (Azure SQL Database in the cloud likewise does not support them.) Use a Docker named volume for local persistence.
References
- references/faq.md: the full question-and-answer list with the "why" behind each capability and gap, grouped by bucket; read it when the quick answers above do not cover the question.
- references/limitations.md: an offline snapshot of the known limitations (active issues, behavior gaps, out-of-scope items); read it when the user needs the current gap list and a workaround.
Staying current
Authoritative, version-pinned references for the tools this skill uses (read the one you need):
If the Microsoft Learn MCP server is configured, use mcp__microsoft-learn__microsoft_docs_search or mcp__microsoft-learn__microsoft_docs_fetch to fetch the current version of any of these on demand. It is optional; when it is unavailable, the references above are authoritative.
