A laptop displays data tools beside an illustration of cloud servers, compatibility checks, and a sandbox testing environment.
Microsoft has put a local-to-cloud deployment wizard into public preview in the MSSQL extension for Visual Studio Code. Its job is to move a database from a developer's machine into Azure SQL. This is a preview, so Microsoft's own definition says it is for non-production use and testing. Microsoft's description of the destination also varies between its pages, so read the details below before you plan around it.

A laptop displays data tools beside an illustration of cloud servers, compatibility checks, and a sandbox testing environment. What Microsoft announced​

The Azure Updates entry is labeled "In preview" and was published on November 17, 2026. Microsoft's listing defines that status as available to all Azure customers for non-production use and testing. The listing text itself has no feature detail.

The detail comes from Microsoft's Azure SQL blog post on its Ignite 2026 database news. That post places the wizard in a laptop-to-cloud story with two parts:

  • The local side. The Azure SQL Database container is also in public preview. It brings the SQL engine to local development without needing an Azure subscription. Microsoft says it offers familiar T-SQL, system views and driver behavior, plus vector support and AI_GENERATE_EMBEDDINGS.
  • The cloud side. When developers are ready to deploy, the blog says the wizard offers a streamlined path from the laptop to Azure SQL Database Hyperscale.

Microsoft frames Hyperscale as the target for modernizing SQL applications and building new AI-driven ones. It describes Hyperscale as an architecture that separates compute from storage so applications can scale with demand.

The destination: Hyperscale or free tier?​

Microsoft's sources describe the wizard's target differently:

  • The Ignite blog names Azure SQL Database Hyperscale.
  • Microsoft Learn's MSSQL extension overview lists the wizard as public preview. It describes it as deploying a local database schema, or schema and data, to a free-tier Azure SQL Database with compatibility checks.
  • The extension's GitHub README describes a wizard that deploys a local database to a free-tier Azure SQL database.
  • The extension roadmap separately lists "Azure SQL database Hyperscale provisioning - Preview" as a later item, under the December 16, 2026 (v1.49) milestone.

These may describe different stages of the same feature, or different wording for the same thing. I can't tell which from the evidence, so I'm not stating a definitive destination. Check the wizard's own screens before you assume either tier.

What the wizard appears to do​

The GitHub pull request that added the feature describes it as a local-to-cloud deployment wizard that integrates source selection and compatibility checks with Azure SQL provisioning. The Learn documentation adds that it can deploy schema only, or schema and data.

That fits the extension's existing Azure workflow. The extension already provisions free-tier Azure SQL databases through its Deployments view. Microsoft's docs describe that as a guided wizard where you pick a subscription, resource group, server and database on a single page. The extension's August 2026 release notes add that it can export ARM, Bicep and Terraform templates. I haven't confirmed that the new wizard shares those export options.

Roadmap and availability​

The MSSQL extension's public roadmap lists "Local to Cloud Deployment wizard - Preview" under the November 17, 2026 (v1.48) milestone, marked as ongoing work. It lists the wizard again under a later milestone with "Preview - GA" status. Treat that as a plan, not a date. The roadmap also shows its January entry as 2026 even though it follows December 2026, which looks like a typo.

Microsoft hasn't documented these points, so I'm not claiming them:

  • an exact extension build that guarantees the wizard is enabled
  • regional availability or charges
  • how authentication, networking and firewall rules are handled
  • rollback behavior, or what happens to a database that fails its compatibility checks

The extension itself runs on Windows 10 and 11 (x64 and Arm64), macOS and Linux, according to Learn. I haven't seen confirmation that the preview wizard is enabled on every platform.

What to do with it​

  1. Keep it to dev and test. The preview label means non-production use.
  2. Start with a throwaway database. Use a small local database, not one you care about.
  3. Read the compatibility checks. Microsoft says they are part of the flow. They are the most useful guardrail for finding features that won't carry over to Azure SQL Database.
  4. Confirm the target tier and cost. Because Microsoft's pages differ on free tier versus Hyperscale, verify the tier and any charges before you click deploy.
  5. Don't treat it as a migration or CI/CD tool. Nothing in the reviewed material calls it that, and the roadmap lists built-in ALM and environment promotion tools as future initiatives.

Why it matters​

The extension has become Microsoft's main SQL tool in VS Code. The Azure Data Studio retirement post says support for that tool ended on February 28, 2026, and recommends VS Code with the MSSQL extension. Pairing a local Azure SQL container with a deployment wizard gives SQL developers a straight route from a laptop to Azure.

The counterargument is that the announcement is thin. A wizard that moves schema and data to the cloud is only as good as its compatibility checks and its handling of credentials and networking. Microsoft hasn't published those details yet. Until it does, treat this as one to try in a sandbox, not a pipeline to build on.

 

References

  1. (In preview) Public Preview: MSSQL extension for Visual Studio Code - local-to-cloud deployment wizard Azure Updates 2026-11-17T20:00:32Z
  2. Added local to cloud deployment experience by laurenastrid1 · Pull Request #23168 · microsoft/vscode-mssql · GitHub github.com
  3. Overview - MSSQL Extension for Visual Studio Code | Microsoft Learn learn.microsoft.com