What runs locally runs in Azure
It is the Azure SQL Database engine itself, with the same defaults, the same T-SQL, and the same error messages. When you deploy to the Microsoft Azure cloud, there are no behavior surprises.
Private Preview
The Azure SQL Database engine,
running locally.
Build and test against the same engine you run in the Microsoft Azure cloud. Try Azure SQL Database before you deploy, and run your tests in CI. Free for local development. No Azure subscription.
< 1 minFrom
docker pull to your first queryFreeFor local development and CI. No subscription, no credit card.
Same engineIdentical to Azure SQL Database in the cloud
Works with the drivers, ORMs, and editors you already use
Drivers
ORMs
Why the container
Cloud parity, in your local environment.#
This is the Azure SQL Database engine itself, running locally, for development. Build in your local inner loop, then deploy the same code to Azure SQL Database in the Microsoft Azure cloud for production.
AI-ready, like Azure SQL Database
Native vector type, VECTOR_DISTANCE search, AI_GENERATE_EMBEDDINGS, and CREATE EXTERNAL MODEL (DiskANN vector indexes are in development). Build RAG locally with a local model, then switch to Azure OpenAI in the cloud.
One codebase, two endpoints
Same drivers, same T-SQL, same migrations. When you are ready, point the connection at Azure SQL Database and deploy the same app to the Microsoft Azure cloud. The application does not change.
Quickstart
Up and running in three commands.#
New to containers? Sign up for the Private Preview to get your registry credentials, then sign in, start the container, and run your first query. The credentials are pull-only and may be rotated during the preview.
0
Sign up for the Private Preview
Signing up is how you get the registry username and password. Sign up →
1
Sign in to the preview registry
Use the username and password you received when you signed up.
$ docker login sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io -u <username>
2
Start the container
Run it on port 1433 with a strong SA password.
$ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=YourStr0ng_Passw0rd" \
-p 1433:1433 -d sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io/azure-sql/db-dev:latest
3
Connect and query
Open a session with sqlcmd and run your first query.
$ sqlcmd -S localhost,1433 -U sa -C -h-1 \
-Q "SET NOCOUNT ON; SELECT @@VERSION AS Version;"
Want your AI agent to set it up, or prefer the full step-by-step? Read the full Get started guide →
Built for AI-assisted development
Bring your AI coding agent.#
Point your agent at Azure SQL Developer and let it scaffold the schema, write the migrations, and build the data layer against a real local database. The repo ships ready-to-use agent skills.
GitHub Copilot
App, CLI, and VS Code
Claude Code
Container skill included
Codex
Terminal and IDE
Cursor
AI-native editor
Install the agent skills once. They work across Claude Code, GitHub Copilot, Codex, and Cursor, then you just ask your agent in plain English.
$ npx skills add microsoft/azure-sql-database-container
Agent skills
A collection of skills your agent loads on demand. Each one teaches it to use the engine the right way, so it does not reach for the SQL Server image or invent behavior the engine does not have.
azuresql-db-container
Start the engine →
Free host port, --platform linux/amd64 on non-x64 hosts, a ready-wait loop, and CREATE DATABASE appdb (the engine does not auto-create databases).
Convert from SQL Server →
Move a project off the mcr.microsoft.com/mssql/server SQL Server image to the real Azure SQL Database engine.
Local to cloud →
Ship the same code to Azure SQL Database in the cloud; only the connection string changes.
azuresql-db-schema-migrationSchema migrations →
Apply EF Core, Prisma, Alembic, or SqlPackage migrations against the user database.
azuresql-db-importImport a database →
Load an existing .bacpac / .dacpac into the container with SqlPackage.
RAG and vector search →
Native VECTOR type and VECTOR_DISTANCE, with a local embedding model.
CI →
Run the engine as a service in GitHub Actions, with the right readiness and provisioning.
azuresql-db-sidecarSidecar →
Add it to a docker compose stack or Dev Container, wired by service name.
azuresql-db-scaffoldScaffold →
Bootstrap a new app with Azure SQL Developer as the default local database.
azuresql-db-faqAnswer questions →
What Azure SQL Developer can and can't do, and why it differs from the cloud: backups, USE, vector index, x64-only, tooling.
Use cases
What can you build with it?#
The everyday jobs a cloud-only database makes slow or expensive. Pick one, copy the prompt, and let your AI agent build it against Azure SQL Developer.
Already using the SQL Server image?
Convert a project on the mcr.microsoft.com/mssql/server SQL Server image to the Azure SQL Database engine: swap the image, fix the connection model, and flag SQL Server-only features. Azure-faithful local dev.
Build locally, ship to Azure
Develop and test at local-disk speed with no cloud round trip, then deploy the same code to Azure SQL Database. Lift and shift is a connection-string change.
Prototype AI and RAG apps
Build vector search and embeddings against a local database with a local model like Ollama, then switch to Azure OpenAI in the cloud. No cloud spend while you experiment.
Run integration tests in CI
Spin the container up as a service in GitHub Actions or Azure Pipelines. Real end-to-end tests, with no Azure subscription and no shared-instance flakiness.
Develop offline
Run demos, classes, and workshops with no internet. After the first pull, the container runs fully offline on a laptop.
Drop in as a sidecar
Add SQL Database to a docker compose stack or a Dev Container as a sidecar service, wire-compatible with the drivers and ORMs you already use.
Scaffold new projects
Start a new .NET Aspire, FastAPI, Next.js, or NestJS project with Azure SQL Database as the default local development resource.
Get involved
You shape this preview.#
Your bugs and feature requests set the priorities. Reach the team directly, or pick the channel that fits your question.