A desktop monitor displays a database interface beside an illustration of data syncing from a Docker container to secure cloud storage.
SQL Server Management Studio can now create a local Azure SQL Database container for you. Microsoft's SSMS 22.12.1 is the release that adds it, and the wizard is labeled preview. It saves developers some Docker typing, but it comes with caveats that matter before anyone trusts it as a stand-in for the cloud service.

A desktop monitor displays a database interface beside an illustration of data syncing from a Docker container to secure cloud storage. What Microsoft shipped​

The release notes list SSMS 22.12.0 as dated November 10, 2026. The 22.12.1 build arrived a week later. The SQL Server team announced it at Ignite on November 17, 2026. In the announcement, the release introduces local Azure SQL Database container creation and management (preview) alongside a new Copilot chat experience and other changes. That wording is from the Microsoft Community Hub post on SSMS 22.12.1. The Azure Updates entry that prompted this story labels the capability a public preview.

The announcement describes the feature this way:

  • It lets you create and manage a local development resource from SSMS without an Azure subscription.
  • It uses Docker Desktop as the container runtime.
  • You open the wizard by choosing Create Azure SQL Database container (preview) in the Object Explorer toolbar.
  • After that, you right-click the container in Object Explorer. The Container Tasks menu lets you deploy, start, stop and delete it without running Docker commands yourself.

The announcement doesn't list Docker Desktop version requirements, host OS support or configuration options for the wizard. I'm not going to guess at them.

Why it matters​

The container is the Azure SQL Database engine running locally. Microsoft's Azure SQL Dev Corner blog introduced it in private preview as the Azure SQL Database engine, on your laptop, in a container. Until now, using it meant pulling an image and running docker run by hand. The SSMS wizard moves that routine into a tool many SQL Server and Azure SQL developers already have open all day.

I'd call this a convenience feature, not a new capability. The engine, the image and the limits all come from the container project. SSMS adds a front end for it.

Caveats before you rely on it​

Microsoft's own documentation for the container is blunt about its boundaries. Several of these items could change how you use the wizard.

It is for development only​

The container is meant for development, testing, CI and demos. It is not a production database and is not meant to be deployed to Azure or run as a production service. For production, you deploy the same code to Azure SQL Database in the cloud, where backups, high availability, scaling and security are managed for you.

Passing locally doesn't guarantee passing in Azure​

The known-limitations page says some platform-as-a-service restrictions enforced in Azure SQL Database are not yet enforced by the container. In the page's own words, a query that works locally may fail against the cloud database at deployment time. Microsoft's workaround is to run your queries against a real Azure SQL Database instance once before you call them ready.

Session and database defaults can also differ. The page names collation, transaction isolation and ANSI defaults. Its advice is to set those explicitly in your connection string or session.

The SSMS UI itself has known issues​

This is the awkward part for a wizard that lives inside SSMS. The container documentation says graphical tools aren't yet fully compatible with the container, and that SSMS and the VS Code MSSQL extension can throw UI errors against it. Microsoft says it is working on full compatibility. Its stated workaround is sqlcmd, either on the host or the copy bundled in the container via docker exec, or any driver or ORM. Provisioning through the wizard doesn't mean every Object Explorer action will work cleanly afterward.

Provisioning is two-step for now​

The documentation says you provision a database over a connection to master, then reconnect directly to the new database. It adds that the public preview will let the container set a default startup database, such as MSSQL_DB=appdb. That page also says a connection to master is a provisioning session, and it advises using it only to create and drop databases. A connection to a user database is the one that enforces Azure SQL Database semantics.

Status labels don't match​

The container docs still carry a Private Preview label. The known-limitations text refers to a Private Preview license scoped to development, testing, CI and demos. The Azure Updates item and the SSMS post call the SSMS capability a preview. The docs also describe the image as not published to public registries such as MCR or Docker Hub. The pull credentials are shared, pull-only and may be rotated. The prerequisites page says you must be in the Private Preview to pull the image.

So I can't confirm from these sources whether the wizard works for someone outside the preview cohort. The documentation also says the container site is deprecated in favor of the Azure SQL Developer Hub, which suggests the guidance is moving. Check current guidance before you plan around it.

Other documented gaps​

  • No backup or restore. BACKUP DATABASE and RESTORE DATABASE aren't supported in the container. Azure SQL Database in the cloud doesn't support them either, since the platform manages backups. For local persistence, Microsoft suggests a Docker named volume.
  • No resource caps. The container doesn't enforce per-database DTU or vCore limits.
  • Auditing. Audit-to-file works. Audit-to-cloud targets such as Log Analytics or Storage don't apply.
  • Always Encrypted. Basic functionality works. Secure enclaves need host TEE support and aren't validated.
  • Cloud management tools. The Azure portal, CLI, ARM, Bicep and Terraform target the cloud service, not the container. Elastic pools, Hyperscale and serverless auto-pause are likewise cloud features.
  • SQL Server-only features. SQL Agent, FILESTREAM, full Service Broker, Windows Authentication/NTLM and cross-server distributed transactions are intentionally absent. That's because Azure SQL Database doesn't offer them either.
  • Vector indexes. The documentation lists several specific rules for CREATE VECTOR INDEX. It also says the measurements behind them are at prototype scale only.

A sensible way to use it​

If you already live in SSMS, a reasonable workflow looks like this:

  1. Install or update to SSMS 22.12.1.
  2. Make sure Docker Desktop is installed.
  3. Open the wizard from the Object Explorer toolbar and create the container.
  4. Create your database over a master connection, then reconnect directly to it for application work.
  5. Set collation, isolation and ANSI options explicitly in your connection string.
  6. If an SSMS UI action throws an error, fall back to sqlcmd or your driver.
  7. Before shipping, run the workload against a real Azure SQL Database instance.

Step 7 is not optional. Microsoft's own limitations page treats cloud validation as the safeguard against the restriction gaps.

The bottom line​

The wizard is a small, sensible quality-of-life addition for developers who work between SSMS and Azure SQL Database. It puts container lifecycle management into Object Explorer. It doesn't turn SSMS into a replacement for Docker Desktop, and it doesn't make the container production-ready. Given the UI-compatibility warnings and the mixed preview labeling, I'd try it for inner-loop work and keep a cloud database around for the final check.

The same release also brings a new Copilot chat experience, bring-your-own-model support and improved bacpac/dacpac workflows, all in preview. Those are separate from the container feature.

 

References

  1. (In preview) Public Preview: Azure SQL Database container provisioning in SQL Server Management Studio Azure Updates 2026-11-17T20:00:32Z
  2. Known limitations · Azure SQL Database container microsoft.github.io
  3. Build locally, ship to Azure: meet Azure SQL Database container - Azure SQL Dev Corner devblogs.microsoft.com