Changes / Databases & SQL tools / Microsoft SQL Server
End of supportmedium impact
Azure Data Studio retired
Azure Data Studio was retired on February 28, 2026 and no longer receives updates or security fixes; Microsoft directs users to Visual Studio Code with the MSSQL extension.
Who’s affected
Anyone still using Azure Data Studio to query, administer or script against SQL Server or Azure SQL, including individual developers, DBAs and shared jump-box or golden-image setups.
Not affected: Teams already on Visual Studio Code with the MSSQL extension, SSMS, or another SQL client, and users who never installed Azure Data Studio.
What it costs
No license or price change in the record. The cost is migration effort and security exposure: the tool no longer gets updates or security fixes, so each remaining install carries growing risk.
When to act
The retirement date (2026-02-28) has already passed, so remaining installs are running unpatched; plan to move users and shared scripts off it within a quarter or so.
Blast radius: Saved connections, notebooks, extensions, shared how-to docs and onboarding guides that assume Azure Data Studio, plus unpatched installs on shared machines or VDI images.
What should you do? decision tree
- you are not sure who still uses Azure Data StudioInventory installs across laptops, VDI images and jump boxes, plus any docs or runbooks that tell people to use it.
- users only run queries and light admin tasksMove them to Visual Studio Code with the MSSQL extension, which Microsoft recommends, and share a standard settings profile.
- you depend on notebooks, saved connections or extensions that may not carry overTest those workflows in VS Code with the MSSQL extension first, and keep a list of gaps before you retire the old tool.
- compliance or security policy forbids unpatched softwareRemove Azure Data Studio from managed images now and block it through endpoint management.
- A workflow cannot move yetIsolate the installs on restricted machines with limited network access and set a firm removal date.
Options
- OptimizeUninstall Azure Data Studio from managed images and standardize on VS Code with the MSSQL extension for everyday querying.
- MigrateMove saved connections, snippets and scripts into VS Code workspaces and source control so teams share one setup.
- Re-architectShift admin and deployment tasks from GUI clicks into scripts or CI pipelines so they don't depend on any one desktop client.
- WaitKeep Azure Data Studio only on isolated, low-risk machines for a short, dated period; it gets no security fixes.
Alternatives editorial picks, not sponsored
The facts straight from the source
Facts above are extracted from the source and checked word-for-word before publishing. The guidance sections are AI-assisted analysis based only on those facts: a starting point, not legal or procurement advice. Spotted an error? Tell us.
Related changes
- Microsoft SQL ServerSQL Server 2016 (incl. SSIS/SSAS/SSRS 2016) reaches end of support
SQL Server 2016 reached end of support on July 14, 2026, so Microsoft no longer provides regular security updates or technical support; paid ESU is offered as a bridge.
End of support - Microsoft SQL ServerNo new SSRS versions: Power BI Report Server replaces SSRS from SQL Server 2025
Microsoft will release no new SSRS versions from SQL Server 2025 on and consolidates on-premises reporting under Power BI Report Server.
End of support - Microsoft SQL ServerPower BI Report Server rights on SQL Server 2022 Enterprise now tied to active SA
For SQL Server 2022 and earlier, PBIRS usage rights apply only to Enterprise core licenses with active Software Assurance and end when SA expires.
License