Merge pull request #36487 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-27 23:30 UTC

Author: learn-build-service-prod[bot]

azure-sql/virtual-machines/windows/sql-server-extend-end-of-support.md

@@ -1,10 +1,10 @@
 ---
 title: Extend support for SQL Server
-description: Extend support for SQL Server 2012 by migrating your SQL Server instance to Azure, or purchasing extended support to keep instances on-premises.
+description: Extend support for SQL Server 2014 by migrating your SQL Server instance to Azure, or purchasing extended support to keep instances on-premises.
 author: dplessMSFT
 ms.author: dpless
 ms.reviewer: mathoma, randolphwest
-ms.date: 06/12/2025
+ms.date: 12/20/2025
 ms.service: azure-vm-sql-server
 ms.subservice: management
 ms.topic: concept-article
@@ -14,70 +14,61 @@ tags: azure-service-management
 
 [!INCLUDE[appliesto-sqlvm](../../includes/appliesto-sqlvm.md)]
 
-SQL Server 2012 has reached the [end of its support (EOS) life cycle](/lifecycle/products/microsoft-sql-server-2012). Because many customers are still using this version, we're providing several options to continue getting support. You can migrate your on-premises SQL Server instances to Azure virtual machines (VMs), migrate to Azure SQL Database, or stay on-premises and purchase extended security updates.
+SQL Server 2014 reached the [end of its support (EOS) life cycle](/lifecycle/products/sql-server-2014). This article describes how you can extend support for SQL Server 2014 at no extra cost by migrating your workload to SQL Server on Azure Virtual Machines (VMs). 
 
-Unlike with Azure SQL Managed Instance, migrating to an Azure VM doesn't require your applications to be recertified. And unlike with staying on-premises, you receive free extended security patches by migrating to an Azure VM.
-
-The rest of this article provides considerations for migrating your SQL Server instance to an Azure VM.
+Unlike with Azure SQL Managed Instance and Azure SQL Database, migrating to an Azure VM doesn't require your applications to be recertified. 
 
 For more information about end of support options, see [End of support](/sql/sql-server/end-of-support/sql-server-end-of-support-overview).
 
 ## Provisioning
 
-Customers who are on an earlier version of SQL Server need to either self-install or upgrade to SQL Server 2012. Likewise, customers on an earlier version of Windows Server need to either deploy their VM from a custom VHD or upgrade to Windows Server 2012 R2.
+Customers who use an earlier version of SQL Server need to either self-install or upgrade to SQL Server 2014. Likewise, customers who use an earlier version of Windows Server need to either deploy their VM from a custom VHD or upgrade to Windows Server 2012 R2.
 
 Images deployed through Azure Marketplace come with the SQL IaaS Agent extension preinstalled. The SQL IaaS Agent extension is a requirement for flexible licensing and automated patching. Customers who deploy self-installed VMs need to manually install the SQL IaaS Agent extension.
 
-> [!NOTE]
->  
-> Although the SQL Server **Manage** options work with SQL Server 2012, the following features aren't supported_: Automatic backups, and Azure Key Vault integration.
-
 ## Licensing
 
-Pay-as-you-go SQL Server 2012 deployments can convert to [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/).
+You can convert pay-as-you-go SQL Server 2014 deployments to [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/).
+To convert a Software Assurance (SA)-based license to pay-as-you-go, register with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md). After registration, the SQL license type is interchangeable between Azure Hybrid Benefit and pay-as-you-go.
 
-To convert a Software Assurance (SA)-based license to pay-as-you-go, customers should register with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md). After registration, the SQL license type is interchangeable between Azure Hybrid Benefit and pay-as-you-go.
-
-Self-installed SQL Server 2012 instances on an Azure VM can register with the SQL IaaS Agent extension and convert their license type to pay-as-you-go.
+You can register self-installed SQL Server 2014 instances on an Azure VM with the SQL IaaS Agent extension and convert their license type to pay-as-you-go.
 
 ## Migration
 
-You can migrate end of support SQL Server instances to an Azure VM with manual backup/restore methods. This is the most common migration method from on-premises to an Azure VM.
+You can migrate end of support SQL Server instances to an Azure VM by using manual backup and restore methods. This method is the most common migration method from on-premises to an Azure VM.
 
 ### Azure Site Recovery
 
-For bulk migrations, we recommend the [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) service. With Azure Site Recovery, customers can replicate the whole VM, including SQL Server from on-premises to Azure VM.
+For bulk migrations, use the [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) service. By using Azure Site Recovery, you can replicate the whole VM, including SQL Server, from on-premises to an Azure VM.
 
 SQL Server requires app-consistent Azure Site Recovery snapshots to guarantee recovery. Azure Site Recovery supports app-consistent snapshots with a minimum 1-hour interval. The minimum recovery point objective (RPO) possible for SQL Server with Azure Site Recovery migrations is 1 hour. The recovery time objective (RTO) is 2 hours plus SQL Server recovery time.
 
 ### Database Migration Service
 
-The [Azure Database Migration Service](/azure/dms/dms-overview) is an option for customers if they're migrating from on-premises to an Azure VM by upgrading SQL Server to the 2012 version or later.
+Use the [Azure Database Migration Service](/azure/dms/dms-overview) if you're migrating from on-premises to an Azure VM and upgrading SQL Server to the 2014 version or later.
 
 ## Disaster recovery
 
 Disaster recovery solutions for end of support SQL Server on an Azure VM are as follows:
 
-- **SQL Server backups**: Use Azure Backup to help protect your end of support SQL Server 2012 against ransomware, accidental deletion, and corruption with a 15-minute RPO and point-in-time recovery. For more information, see [this article](/azure/backup/sql-support-matrix#scenario-support).
+- **SQL Server backups**: Use Azure Backup to help protect your end of support SQL Server 2014 instances against ransomware, accidental deletion, and corruption with a 15-minute RPO and point-in-time recovery. For more information, see [this article](/azure/backup/sql-support-matrix#scenario-support).
 
 - **Log shipping**: You can create a log shipping replica in another zone or Azure region with continuous restores to reduce the RTO. You need to manually configure log shipping.
 
 - **Azure Site Recovery**: You can replicate your VM between zones and regions through Azure Site Recovery replication. SQL Server requires app-consistent snapshots to guarantee recovery if there's a disaster. Azure Site Recovery offers a minimum 1-hour RPO and a 2-hour (plus SQL Server recovery time) RTO for end of support SQL Server disaster recovery.
 
 ## Security patching
 
-Extended security updates for SQL Server VMs are delivered through the Microsoft Windows Update channels after the SQL Server VM has been registered with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md). Patches can be downloaded manually or automatically.
+After you register a SQL Server VM with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md), Microsoft delivers extended security updates for SQL Server VMs through the Microsoft Windows Update channels. You can manually or automatically download patches.
 
-*Automated patching* is enabled by default. Automated patching allows Azure to automatically patch SQL Server and the operating system. You can specify a day of the week, time, and duration for a maintenance window if the SQL Server IaaS extension is installed. Azure performs patching in this maintenance window. The maintenance window schedule uses the VM locale for time. For more information, see [Automated patching for SQL Server on Azure Virtual Machines](automated-patching.md).
+*Automated patching* is enabled by default. By using automated patching, Azure automatically patches SQL Server and the operating system. You can specify a day of the week, time, and duration for a maintenance window if the SQL Server IaaS extension is installed. Azure performs patching during this maintenance window. The maintenance window schedule uses the VM locale for time. For more information, see [Automated patching for SQL Server on Azure Virtual Machines](automated-patching.md).
 
 For improved patching management, which also includes Cumulative Updates, try the integrated [Azure Update Manager](../azure-update-manager-sql-vm.md) experience. 
 
 > [!NOTE]
-> Registration with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md) isn't required for _manual_ installation of extended security updates on Azure virtual machines. Microsoft Update automatically detects the VM is running in Azure and presents relevant updates for download even if the extension isn't installed.
-
-
+> You don't need to register with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md) for _manual_ installation of extended security updates on Azure virtual machines. Microsoft Update automatically detects the VM is running in Azure and presents relevant updates for download even if the extension isn't installed.
 
-[Azure Update management](/azure/automation/update-management/overview) as of today doesn't detect patches for SQL Server Marketplace images. You should look under Windows Updates to apply SQL Server updates in this case.
+As of today, [Azure Update management](/azure/automation/update-management/overview) doesn't detect patches for SQL Server Marketplace images. You should look under Windows Updates to apply SQL Server updates in this case.
 
 ## Next steps
 

data-migration/sql-server/managed-instance/guide.md

@@ -27,12 +27,11 @@ Migrate your data using your chosen [migration method](overview.md#compare-migra
 
 *This section provides general migration steps for the following recommended migration options*:
 
-- SQL Server migration experience in Azure Arc
-
-- Azure Database Migration Service (DMS), which offers migration with near-zero downtime
-- Managed Instance link
-- Log Replay Service (LRS)
-- Native `RESTORE DATABASE FROM URL`, which uses native backups from SQL Server and requires some downtime
+- [SQL Server migration in Azure Arc](#sql-server-migration-in-azure-arc)
+- [Azure Database Migration Service (Azure DMS)](#azure-database-migration-service-azure-dms), which offers migration with near-zero downtime
+- [Managed Instance link](#managed-instance-link)
+- [Log Replay Service (LRS)](#log-replay-service-lrs)
+- [Native `RESTORE DATABASE FROM URL`](#backup-and-restore), which uses native backups from SQL Server and requires some downtime
 
 SQL Managed Instance targets user scenarios that require mass database migration from on-premises or SQL Server on Azure Virtual Machines implementations. It's the optimal choice when you need to lift and shift the back end of applications that regularly use instance level and cross-database functionalities. If this is your scenario, you can move an entire instance to a corresponding environment in Azure without the need to rearchitect your applications.
 
@@ -43,13 +42,8 @@ To move SQL Server instances, you need to plan carefully:
 
 SQL Managed Instance is a managed service that allows you to delegate some of the regular database administration activities to the platform as they're built in. Therefore, you don't need to migrate some instance-level data, such as maintenance jobs for regular backups or Always On configuration, as [high availability](/azure/azure-sql/database/high-availability-sla-local-zone-redundancy) is built in.
 
-### Database migration
-
-Migrate your SQL Server enabled by Azure Arc instance to Azure SQL Managed Instance directly through the Azure portal. For detailed instructions, see [Migrate SQL Server instance to Azure SQL Managed Instance](/sql/sql-server/azure-arc/migrate-to-azure-sql-managed-instance).
-
-Database migration provides a built-in migration experience, using the Managed Instance link or Log Replay Service (LRS) methods behind the scenes, while simplifying configuration, management, and monitoring of the migration process.
 
-## SQL Server migration in Azure Arc
+### SQL Server migration in Azure Arc
 
 Migrate SQL Server instances enabled by Azure Arc to SQL Managed Instance through the Azure portal. SQL Managed Instance provides a fully managed PaaS solution for lift-and-shift migrations. The process includes assessing readiness, selecting a target, migrating data, and monitoring progress.
 

docs/includes/applies-to-version/sql-migration-end-of-support.md

@@ -5,4 +5,4 @@ ms.date: 07/10/2024
 ms.service: sql
 ms.topic: include
 ---
-[!INCLUDE [Applies to](../../includes/applies-md.md)] :::image type="icon" source="../media/yes-icon.svg" border="false"::: [!INCLUDE [sssql11-md](../sssql11-md.md)] :::image type="icon" source="../media/yes-icon.svg" border="false"::: [!INCLUDE [sssql14-md](../sssql14-md.md)]
+[!INCLUDE [Applies to](../../includes/applies-md.md)] :::image type="icon" source="../media/yes-icon.svg" border="false"::: [!INCLUDE [sssql14-md](../sssql14-md.md)]