Quick verdict
Do not choose Azure Data Studio for anything new: Microsoft retired it on 28 February 2026, its GitHub repository is archived, and it gets no security patches. If you used it for querying, notebooks, schema compare, SQL projects or cross-platform work, move to VS Code with the MSSQL extension (Windows, macOS and Linux). If you used it alongside SSMS, or relied on the SQL Server Agent, Profiler or admin extensions, use SSMS 22 on Windows, which Microsoft calls the supported home for SQL Server Agent and general administration. Many SQL Server teams end up with both: SSMS for administration, VS Code for development.
Status, October 2026. Microsoft states: "Azure Data Studio is retired as of February 28, 2026 and no longer receives updates or security fixes." The last release was Azure Data Studio 1.52 (18 June 2025). Microsoft archived the microsoft/azuredatastudio repository on the retirement date, with a notice to migrate to Visual Studio Code and the MSSQL extension. See Microsoft's page What's happening with Azure Data Studio.
SQL Server Management Studio (SSMS) is Microsoft's free, Windows-only environment for configuring, administering and developing on SQL Server, Azure SQL Database, Azure SQL Managed Instance, Azure Synapse Analytics and SQL database in Fabric. SSMS 22 (22.10.2, released 28 September 2026) is built on Visual Studio 2026, runs on Windows x64 and Arm64, and is not open source. See our SSMS review.
Azure Data Studio (ADS) was Microsoft's free, MIT-licensed, cross-platform data tool built on the VS Code codebase. People used it for a lighter query editor on Windows, macOS and Linux, SQL notebooks, and extensions such as SQL Server Agent, SQL Server Profiler, schema compare, SQL database projects, the Azure SQL migration extension and PostgreSQL support. Microsoft retired it to consolidate SQL tooling into VS Code and SSMS.
Visual Studio Code with the MSSQL extension is the replacement Microsoft names. The extension (1.46.0, released 28 September 2026) runs on Windows, macOS and Linux and lists, as generally available, Object Explorer, a query plan visualiser, table and schema designers, schema compare, SQL notebooks, Query Profiler, backup and restore, DACPAC and BACPAC import and export, flat-file import and GitHub Copilot integration. See our VS Code MSSQL extension review.
Side by side
| Aspect | SSMS | Azure Data Studio |
|---|---|---|
| Status | Current and actively updated (22.10.2, 28 September 2026) | Retired 28 February 2026; final release 1.52 (June 2025); no updates or security fixes |
| Platforms | Windows only (x64 and Arm64) | Was Windows, macOS and Linux |
| Licence and cost | Free, proprietary, own licence terms; not open source | Was free and open source (MIT); repository now archived |
| Supported databases | SQL Server, Azure SQL Database and Managed Instance, Azure Synapse, SQL database in Fabric; SSIS, SSAS and SSRS administration | SQL Server and Azure SQL; PostgreSQL, MySQL and Azure Cosmos DB through extensions |
| SQL Server Agent and administration | Full: Agent jobs, alerts and operators, Activity Monitor, Always On dashboard, security, maintenance plans | Agent and admin features came from extensions; Microsoft now points these tasks to SSMS |
| Notebooks | Not listed among SSMS 22 features | Built-in SQL notebooks (.ipynb); now provided by SQL notebooks in the MSSQL extension |
| Schema compare and SQL projects | Schema Compare and the Database DevOps workload (SQL projects) generally available in 22.10.2 | Via extensions; replaced by the MSSQL and SQL Database Projects extensions for VS Code |
| Extensions | Microsoft components only; third-party extensions not supported | Had its own extension marketplace; no longer maintained |
| Git and AI | Git integration and GitHub Copilot (including Agent Mode) as optional components | Built-in source control from the VS Code base; no further updates |
| Main trade-off | Deepest SQL Server tooling, but Windows only and Microsoft engines only | No longer an option: unsupported software that should be replaced |
Key differences
What changed: retirement and Microsoft's guidance
Microsoft's retirement page gives a clear split by role. App and SQL developers should use the MSSQL extension for VS Code for daily work; Microsoft says existing queries, scripts and SQL database projects open in VS Code without conversion. Database administrators get database operations (create, back up, restore, rename, drop), Query Profiler, DACPAC and BACPAC, schema compare and SQL notebooks in the MSSQL extension, but Microsoft says to "keep job scheduling and classic administration tasks" in SSMS, "which remains the supported home for SQL Server Agent and general administration". Cross-database developers should replace ADS extensions with VS Code equivalents: the PostgreSQL extension, Azure Databases for VS Code for Cosmos DB (MongoDB API), and, for MySQL, a replacement Microsoft lists as pending announcement.
Microsoft explains the decision as consolidating SQL tools into VS Code and SSMS so the team can invest in fewer, more capable tools. Any copies still installed are unpatched, and running unpatched software that connects to production databases is a security risk, so plan the move rather than leaving it on desktops.
Where each Azure Data Studio feature now lives
Based on Microsoft's replacement tables, the SSMS 22 release notes and the MSSQL extension documentation:
- Query editor and Object Explorer, cross-platform: VS Code with the MSSQL extension (Windows, macOS, Linux). On Windows, SSMS also covers this.
- SQL notebooks: SQL notebooks in the MSSQL extension use the standard Jupyter
.ipynbformat with an MSSQL kernel; install the Jupyter extension for Python or other kernels. Each notebook connects to one server at a time. - SQL Server Agent extension: SSMS. The MSSQL extension does not list Agent job management.
- SQL Server Profiler extension: Query Profiler (Extended Events) in the MSSQL extension, or XEvent Profiler in SSMS.
- Database administration extension: database operations in the MSSQL extension for common tasks; SSMS for full administration.
- Schema compare: Schema Compare in the MSSQL extension, or Schema Compare in SSMS 22 (generally available since 22.10.2). Also in SQL Server Data Tools.
- SQL database projects: the SQL Database Projects extension for VS Code, Visual Studio with SSDT, or the Database DevOps workload in SSMS 22.
- DACPAC and flat-file import: the MSSQL extension (Data-tier Application and Import flat file) or the SqlPackage command line.
- PostgreSQL extension: Microsoft's PostgreSQL extension for VS Code (
ms-ossdata.vscode-pgsql), with Object Explorer, IntelliSense, a query plan visualiser, a schema visualiser, a server dashboard and Copilot integration. SSMS does not support PostgreSQL. - MySQL extension: no Microsoft replacement yet; use a dedicated MySQL client.
- SQL Server assessment and Azure SQL migration extensions: SQL Server enabled by Azure Arc migration assessment, and the dedicated migration tools for Azure SQL Managed Instance, SQL Server on Azure VMs and Azure SQL Database (for example Azure Database Migration Service, the Managed Instance link and Log Replay Service). See Azure SQL Database vs Managed Instance.
SSMS 22 or VS Code with MSSQL: which one to move to
SSMS 22 fits if you work on Windows and do administration: SQL Server Agent, security, Always On availability groups, Activity Monitor, Query Store reports, maintenance plans, or SSIS, SSAS and SSRS. Recent releases closed some of the gaps that sent people to ADS: SSMS 22.10.2 made Schema Compare, the Database DevOps workload for SQL projects, the SQL Formatter and GitHub Copilot Agent Mode generally available, and Git integration is an optional component. SSMS still does not run on macOS or Linux, does not support third-party extensions and does not work with PostgreSQL or MySQL.
VS Code with the MSSQL extension fits if you used ADS for development, notebooks or on a Mac or Linux machine. It keeps the VS Code editor model, the extension marketplace, built-in Git, and adds SQL-specific tools that Microsoft now updates regularly. It is not a full administration console: Microsoft points SQL Server Agent and classic administration back to SSMS.
If you used ADS mainly for PostgreSQL alongside SQL Server, VS Code with both the MSSQL and PostgreSQL extensions is the closest one-window replacement. Cross-engine desktop clients are an alternative; see DBeaver vs SSMS, DataGrip vs SSMS and DataGrip vs VS Code.
Migration checklist
- Inventory what you used in ADS: installed extensions (Agent, Profiler, admin pack, schema compare, SQL projects, PostgreSQL, MySQL, Cosmos DB, migration), notebooks, saved connections and server groups, and any scripts or tasks you run from it.
- Install the replacements: VS Code plus the MSSQL extension; add the SQL Database Projects extension if you use projects, the PostgreSQL extension if you use PostgreSQL, and the Jupyter extension if your notebooks use Python or other kernels. Install SSMS 22 on Windows if you manage SQL Server Agent or do administration.
- Import connections: the MSSQL extension's Azure Data Studio Migration feature imports saved connections, connection groups and settings from Azure Data Studio (Microsoft documents it in "Transition from Azure Data Studio"). In SSMS, use Registered Servers or the connection import added in SSMS 22. Move credentials into Microsoft Entra ID authentication where you can.
- Open projects, scripts and notebooks: Microsoft says SQL projects, queries and scripts work in VS Code without conversion. Open each
.ipynbnotebook, select the MSSQL kernel and re-run it to confirm the results before you rely on it. - Move Agent and admin work to SSMS: jobs, schedules, alerts and operators, and anything from the admin pack. Use Query Profiler in VS Code or XEvent Profiler in SSMS instead of the Profiler extension.
- Re-point schema compare and deployment pipelines to the MSSQL extension, SSMS 22 Schema Compare, or SqlPackage in CI/CD.
- Replace migration tooling: use Azure Arc migration assessment and Azure Database Migration Service, the Managed Instance link or Log Replay Service instead of the Azure SQL migration extension.
- Pick a MySQL client if you used the ADS MySQL extension, because Microsoft has not announced a replacement.
- Uninstall Azure Data Studio and remove it from machine images and software catalogues once the move is done, since it receives no security fixes.
Pricing and licensing
SSMS. Free. Microsoft's FAQ states SSMS is free for personal or enterprise use, has its own licence terms and does not need a Visual Studio subscription. GitHub Copilot in SSMS is an optional component, not installed by default.
Azure Data Studio. Was free and open source under the MIT licence. It is retired, so cost is not a factor: it should not be used.
VS Code with the MSSQL and PostgreSQL extensions. Free to download and install from Microsoft.
Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.
Where each one leads
SSMS strengths
- Current, supported and frequently updated (22.10.2 in September 2026)
- Microsoft's supported home for SQL Server Agent and full administration
- Schema Compare, SQL projects (Database DevOps) and SQL Formatter generally available in SSMS 22
- Activity Monitor, Query Store reports, Always On dashboard and SSIS, SSAS and SSRS administration
- Free for personal and enterprise use, on Windows x64 and Arm64
Azure Data Studio strengths
- Ran on Windows, macOS and Linux
- Built-in SQL notebooks in the standard .ipynb format
- Extension marketplace that covered Agent, Profiler, schema compare, SQL projects and PostgreSQL
- Open source under the MIT licence
Limitations
SSMS limitations
- Windows only; Microsoft states it does not run on macOS
- Works only with Microsoft SQL engines, not PostgreSQL or MySQL
- No notebook support listed in SSMS 22
- Third-party extensions are not supported, and SSMS is not open source
Azure Data Studio limitations
- Retired on 28 February 2026: no updates, security patches or maintenance
- GitHub repository archived and read-only; issues are no longer handled
- Extensions are frozen, and the MySQL extension has no Microsoft replacement yet
- Its Azure SQL migration extension has been superseded by dedicated migration tools
When to choose each
Choose SSMS if
- You manage SQL Server Agent jobs, security, backups or availability groups
- You work on Windows and want one tool for administration and querying
- You tune queries with execution plans and Query Store reports
- You administer SSIS, SSAS or SSRS alongside the Database Engine
Choose Azure Data Studio if
- No new scenario: Azure Data Studio is retired and should not be installed or chosen for new work
- If it is still installed, use it only briefly to list the extensions, notebooks and connections you need to move, then uninstall it
- For what you used it for, choose VS Code with the MSSQL extension (development, notebooks, macOS and Linux) or SSMS (administration)
When neither is right
- You used ADS for development, notebooks or on macOS or Linux: move to VS Code with the MSSQL extension, adding the PostgreSQL extension if you also work with PostgreSQL.
- You want one desktop client for SQL Server plus PostgreSQL, MySQL and other engines: see DBeaver vs SSMS and DataGrip vs SSMS.
- You want a wider shortlist of replacements: see the best SSMS alternatives and the best SQL Server GUI tools.
- You are also moving databases to the cloud: see Azure SQL Database vs SQL Server and AWS RDS vs Azure SQL Database.
Final recommendation
Azure Data Studio is no longer a contender: it was retired on 28 February 2026 and receives no security fixes, so remove it from your toolkit. For SQL Server administration on Windows, SSMS 22 is the answer, and it now includes Schema Compare and SQL projects as well. For everything ADS was liked for, namely a lighter editor, notebooks, extensions and macOS or Linux support, Microsoft's replacement is VS Code with the MSSQL extension, plus the PostgreSQL extension if you need it. Follow the checklist above, starting with an inventory of the ADS extensions you relied on.
Frequently asked questions
Is Azure Data Studio discontinued?
Yes. Microsoft retired Azure Data Studio on 28 February 2026. It no longer receives updates, security patches or maintenance, and the GitHub repository is archived. The last release was 1.52 in June 2025.
What replaces Azure Data Studio?
Microsoft recommends Visual Studio Code with the MSSQL extension for development and day-to-day work, and SSMS for SQL Server Agent and full administration. PostgreSQL users should install Microsoft's PostgreSQL extension for VS Code.
Can I still use Azure Data Studio?
Existing installations are unsupported and get no security fixes, so Microsoft advises migrating. Do not use it for new work or keep it on machines that connect to production databases.
Will my Azure Data Studio notebooks work in VS Code?
ADS notebooks are .ipynb files, and SQL notebooks in the MSSQL extension use the native VS Code Jupyter format with an MSSQL kernel. Open each notebook, select the MSSQL kernel (or install the Jupyter extension for Python cells) and re-run it to confirm the output.
Where do I manage SQL Server Agent jobs now?
In SSMS. Microsoft's retirement guidance names SSMS as the replacement for the Azure Data Studio SQL Server Agent extension; the MSSQL extension for VS Code does not list Agent job management.
Is there a Mac version of SSMS?
No. SSMS runs only on Windows (x64 and Arm64). On macOS or Linux, use VS Code with the MSSQL extension, or a cross-platform client such as DBeaver or DataGrip.
Sources
- Microsoft Learn: What's happening with Azure Data Studio
- Microsoft Learn: Azure Data Studio release notes
- Microsoft Learn: Transition from Azure Data Studio (MSSQL extension)
- GitHub: microsoft/azuredatastudio (archived)
- Microsoft Learn: SSMS FAQ
- Microsoft Learn: SSMS 22 release notes
- Microsoft Learn: MSSQL extension for Visual Studio Code
- Microsoft Learn: SQL notebooks in the MSSQL extension
- GitHub: microsoft/vscode-mssql releases
- Microsoft Learn: PostgreSQL extension for Visual Studio Code
Checked October 2026.
How we research comparisons: our editorial method.