SQL Server end-of-support dates
| Version | Extended support ended / ends | Status |
|---|---|---|
| SQL Server 2012 | 12 Jul 2022 | Out of support |
| SQL Server 2014 | 9 Jul 2024 | Out of support |
| SQL Server 2016 | 14 Jul 2026 | Out of support (ESUs available) |
| SQL Server 2017 | 12 Oct 2027 | Extended support |
| SQL Server 2019 | 8 Jan 2030 | Extended support |
| SQL Server 2022 | 11 Jan 2033 | Supported |
Choosing the right Azure target for SQL Server
| Azure SQL Managed Instance | SQL Server on Azure VM | Azure SQL Database | |
|---|---|---|---|
| Compatibility with existing apps | Very high | Complete | Moderate |
| Patching and backups | Managed by Microsoft | Your responsibility | Managed by Microsoft |
| High availability | Built in | You configure | Built in |
| OS access | No | Yes | No |
| Best for | Most line-of-business databases | Vendor-certified or complex set-ups | New or modernised apps |
For most UK organisations moving existing business applications, Azure SQL Managed Instance is the best balance. You get almost no code changes and no more patching or backup jobs.
How a SQL Server migration works
- Assess compatibility. Azure Migrate and the Azure SQL migration extension scan each instance for blockers and recommend a target and size.
- Choose the target per database. Some databases move to Managed Instance and others to VMs, depending on features used and vendor support.
- Migrate online. Azure Database Migration Service (or the Managed Instance link) keeps the Azure copy in sync with the source while you test.
- Cut over. Stop writes, let the final changes sync, repoint applications and go live. Usually this takes minutes.
- Optimise. Review performance tiers after go-live and apply reservations and Azure Hybrid Benefit.
Why move SQL Server to Azure now?
- Security. SQL Server 2016 and earlier no longer get free security updates on-premises.
- Less admin. Managed services remove patching, backups and HA configuration.
- Licensing value. Azure Hybrid Benefit and reserved capacity often make Azure cheaper than renewing on-premises hardware and licences.
- A path to modernise. Once in Azure, databases can connect to analytics and AI services such as Microsoft Fabric without another migration.
Planning a migration? Get a free assessment covering scope, ballpark cost and funding eligibility.
Get my free assessmentFrequently asked questions
What's the difference between Azure SQL Managed Instance and Azure SQL Database?
Azure SQL Managed Instance behaves like a full SQL Server instance, with SQL Agent, cross-database queries, CLR and linked servers, so most existing applications move unchanged. Azure SQL Database is a single-database service that suits new or cloud-native applications but may need code changes for legacy apps.
When should I choose SQL Server on an Azure VM instead?
Choose a VM when you need OS-level access, features Managed Instance doesn't support (for example some SSRS/SSIS set-ups or third-party agents), or a vendor-certified configuration. It's the closest like-for-like move, but you keep responsibility for patching and HA.
How much downtime does a SQL Server migration need?
With online migration (log replay or the Managed Instance link), the final cut-over is typically minutes. Offline backup-and-restore is simpler but needs a longer window, sized by database size.
Can I use my existing SQL Server licences?
Yes. SQL Server Enterprise or Standard licences with Software Assurance can be applied to Azure SQL Managed Instance, Azure SQL Database (vCore) and Azure VMs through Azure Hybrid Benefit.
Is SQL Server 2016 still safe to run?
Since 14 July 2026, SQL Server 2016 no longer receives security updates unless it's covered by Extended Security Updates. Running it in Azure gives you ESUs at no extra charge while you plan an upgrade.