Merge pull request #37014 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-03 22:30 UTC

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

azure-sql/database/scale-resources.md

@@ -73,6 +73,12 @@ Scaling resources is the easiest and the most effective way to improve performan
 - [Read scale-out](read-scale-out.md) is an available feature where you are getting one read-only replica of your data where you can execute demanding read-only queries such as reports. A read-only replica will handle your read-only workload without affecting resource usage on your primary database.
 - [Database sharding](elastic-scale-introduction.md) is a set of techniques that enables you to split your data into several databases and scale them independently.
 
+## Scaling operations for geo-replicas
+
+When your Azure SQL resource has a geo-replica, consider the following guidance for your scaling operations:
+- Azure SQL Database: [Active geo-replication](active-geo-replication-overview.md#scale-primary-database), [failover groups](failover-group-configure-sql-db.md#upgrading-or-downgrading-primary-database)
+- Azure SQL Managed Instance: [Failover groups](../managed-instance/failover-group-configure-sql-mi.md#scaling-instances)
+
 ## Related content
 
 - For information about improving database performance by changing database code, see [Find and apply performance recommendations](database-advisor-find-recommendations-portal.md).

azure-sql/includes/virtual-machines-2014-end-of-support.md

@@ -6,4 +6,4 @@ ms.service: azure-vm-sql-server
 ms.topic: include
 ---
 > [!NOTE]
-> SQL Server 2012 and SQL Server 2014 are out of mainstream support and no longer available from the Azure Marketplace.
+> SQL Server 2012 and SQL Server 2014 are out of mainstream support and no longer available from Azure Marketplace.

azure-sql/managed-instance/failover-group-configure-sql-mi.md

@@ -471,7 +471,9 @@ Instances in a failover group remain separate Azure resources, and no changes ma
 This section is duplicated in /managed-instance/failover-group-sql-mi.md.. Please ensure changes are made to both documents.  
 -->
 
-The configuration of your primary and secondary instance should be the same. This includes the compute size, storage size, and service tier. If you need to change the configuration of your failover group, you can do so by scaling each instance to the same configuration accordingly. 
+The configuration of your primary and secondary instance should be the same. This includes the compute size, storage size, and service tier. If you need to change the configuration of your failover group, you can do so by scaling each instance to the same configuration accordingly.
+
+Downgrading the secondary instance to a lower service tier or compute size than the primary instance can cause performance degradation after failover.
 
 To avoid problems from a lower service tier or under-resourced geo-secondary getting overloaded, or having to reseed during an upgrade or downgrade process, consider the following: 
 
@@ -484,7 +486,12 @@ To avoid problems from a lower service tier or under-resourced geo-secondary get
   - Scaling the storage size.
   - [Changing the memory allocation](resource-limits.md#flexible-memory) of your [Next-gen General Purpose](service-tiers-next-gen-general-purpose-use.md) instance.
 
+When trying to scale the service tier, vCores, and storage at the same time (for example, scaling up vCores and service tier while scaling down storage), don't change all three simultaneously. Instead, use one of the following approaches:
+
+- **Option 1**: Scale the service tier first (keep storage and vCores the same), following the upgrade/downgrade order described previously. Then scale storage and vCores separately.
+- **Option 2**: Scale storage first (keep service tier and vCores the same), following the upgrade/downgrade order described previously. Then scale the service tier and vCores separately.
 
+This two-step approach prevents the secondary replica with fewer resources from becoming overloaded, which can cause reseeding during the scaling process.
 
 ## Permissions
 

azure-sql/toc.yml

@@ -1615,6 +1615,8 @@
           href: virtual-machines/windows/change-sql-server-edition.md
         - name: Change version
           href: virtual-machines/windows/change-sql-server-version.md
+        - name: Updating SQL Server
+          href: virtual-machines/windows/servicing-updates-guidelines.md
       - name: SQL IaaS Agent extension
         displayName: resource provider, registration, sql vm rp
         items:

azure-sql/virtual-machines/windows/automated-patching.md

@@ -129,5 +129,6 @@ If you're currently using Automated Patching, you can [migrate to Azure Update M
 
 ## Related content
 
+- [Updating SQL Server on Azure VMs](servicing-updates-guidelines.md)
 - [Automate management with the Windows SQL Server IaaS Agent extension](sql-server-iaas-agent-extension-automate-management.md)
 - [What is SQL Server on Azure Windows Virtual Machines?](sql-server-on-azure-vm-iaas-what-is-overview.md)

azure-sql/virtual-machines/windows/create-sql-vm-portal.md

@@ -207,11 +207,11 @@ If you chose a free license image, such as the developer edition, the **SQL Serv
 
 ### Automated patching
 
-**Automated patching** is disabled by default. [Automated Patching](automated-patching.md) allows Azure to automatically apply SQL Server and operating system security updates. If yoou want Azure to automatically patch SQL Server and the operating system, select **Enable**. Specify a day of the week, time, and duration for a maintenance window. Azure performs patching in this maintenance window. 
+**Automated patching** is disabled by default. [Automated Patching](automated-patching.md) allows Azure to automatically apply SQL Server and operating system security updates. If you want Azure to automatically patch SQL Server and the operating system, select **Enable**. Specify a day of the week, time, and duration for a maintenance window. Azure performs patching in this maintenance window. 
 
 :::image type="content" source="./media/create-sql-vm-portal/azure-sqlvm-automated-patching.png" alt-text="Screenshot from the Azure portal of SQL VM automated patching.":::
 
-For improved patching management, which also includes Cumulative Updates, try the integrated [Azure Update Manager](../azure-update-manager-sql-vm.md) experience after your SQL Server VM finishes deployment.
+For improved patching management, which also includes Cumulative Updates, try the integrated [Azure Update Manager](../azure-update-manager-sql-vm.md) experience after your SQL Server VM finishes deployment. For more information about all supported update methods, see [Updating SQL Server on Azure VMs](servicing-updates-guidelines.md).
 
 ### Automated backup
 
@@ -284,6 +284,7 @@ SQL Server images from Azure Marketplace install the SQL Server binaries to the
 
 ## Related content
 
+- [Updating SQL Server on Azure VMs](servicing-updates-guidelines.md)
 - [What is SQL Server on Azure Windows Virtual Machines?](sql-server-on-azure-vm-iaas-what-is-overview.md)
 - [Frequently asked questions for SQL Server on Azure VMs](frequently-asked-questions-faq.yml)
 - [Checklist: Best practices for SQL Server on Azure VMs](performance-guidelines-best-practices-checklist.md)

azure-sql/virtual-machines/windows/doc-changes-updates-release-notes-whats-new.md

@@ -4,7 +4,7 @@ description: Learn about the new features for and improvements to SQL Server on
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest, dpless
-ms.date: 03/16/2026
+ms.date: 04/01/2026
 ms.service: azure-vm-sql-server
 ms.topic: whats-new
 ms.custom:
@@ -56,13 +56,18 @@ The following table lists features of SQL Server on Azure VMs that have been mad
 
 Learn about significant changes to the SQL Server on Azure VMs documentation. For previous years, see the [What's new archive](doc-changes-updates-release-notes-whats-new-archive.md).
 
+### April 2026
+
+| Changes | Details |
+| --- | --- |
+| **SQL Server servicing and updates guidance** | New article that describes the supported methods to keep SQL Server up to date on Azure VMs, including Azure Update Manager, Automated Patching, custom images, winget for client tools, and post-deployment automation. SQL Server images from Azure Marketplace are deployed at RTM and aren't updated over time. For more information, see [Updating SQL Server on Azure VMs](servicing-updates-guidelines.md). |
+
 ### March 2026
 
 | Changes | Details |
 | --- | --- | --- |
 | **Unified inventory preview** | You can now view your SQL Server on Azure VM and SQL Server enabled by Azure Arc resources in a single pane in the Azure portal. With unified inventory, you can view your *SQL Server instance* resources, making it easier to monitor and maintain your SQL Server workloads in Azure. This feature is now in preview. For more information, see [Unified inventory for SQL Server on Azure VMs](unified-inventory-sql-vm.md). |
 
-
 ### January 2026
 
 | Changes | Details |
@@ -78,7 +83,6 @@ Learn about significant changes to the SQL Server on Azure VMs documentation. Fo
 
 ## Archive
 
-
 For updates made in previous years, see the [What's new archive](doc-changes-updates-release-notes-whats-new-archive.md). 
 
 ## Contribute to content

azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md

@@ -543,13 +543,20 @@ If you are on Windows Server 2019 and you don't see a Windows Cluster IP, you ha
 
 Review other Windows Failover [Failover Clustering system log events](/windows-server/failover-clustering/system-events) and their solutions.
 
-## Next steps
+## Related content
 
-To learn more, see:
+For detailed guidance on each optimization area:
+
+- **[Quick checklist](performance-guidelines-best-practices-checklist.md)** - Review the full best practices checklist
+- **[VM size](performance-guidelines-best-practices-vm-size.md)** - Choose the right VM series and configuration
+- **[Storage](performance-guidelines-best-practices-storage.md)** - Optimize disk configuration and performance
+- **[Security](security-considerations-best-practices.md)** - Implement security best practices
+- **[Collect baseline](performance-guidelines-best-practices-collect-baseline.md)** - Establish performance baselines
+- **[Updating SQL Server](servicing-updates-guidelines.md)** - Keep SQL Server up to date
+
+For more information about HADR:
 
-- [HADR settings for SQL Server on Azure VMs](hadr-cluster-best-practices.md)
 - [Windows Server Failover Cluster with SQL Server on Azure VMs](hadr-windows-server-failover-cluster-overview.md)
 - [Always On availability groups with SQL Server on Azure VMs](availability-group-overview.md)
-- [Windows Server Failover Cluster with SQL Server on Azure VMs](hadr-windows-server-failover-cluster-overview.md)
 - [Failover cluster instances with SQL Server on Azure VMs](failover-cluster-instance-overview.md)
 - [Failover cluster instance overview](/sql/sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server)

azure-sql/virtual-machines/windows/manage-sql-vm-portal.md

@@ -151,6 +151,7 @@ From the **SQL IaaS Agent Extension Settings** page, you can [repair the extensi
 
 ## Related content
 
+- [Updating SQL Server on Azure VMs](servicing-updates-guidelines.md)
 - [What is SQL Server on Azure Windows Virtual Machines?](sql-server-on-azure-vm-iaas-what-is-overview.md)
 - [FAQ for SQL Server on Windows VMs](frequently-asked-questions-faq.yml)
 - [Pricing guidance for SQL Server on Azure VMs](pricing-guidance.md)

azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist.md

@@ -99,7 +99,7 @@ The following checklist summarizes best practices for SQL Server configuration s
 - Set max [SQL Server memory limit](/sql/database-engine/configure-windows/server-memory-server-configuration-options#use-) to leave enough memory for the operating system. ([Use Memory\Available Bytes](/sql/relational-databases/performance-monitor/monitor-memory-usage) to monitor the operating system memory health).
 - Enable [lock pages in memory](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows).
 - Enable [optimize for adhoc workloads](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) for OLTP heavy environments.
-- Evaluate and apply the [latest cumulative updates](/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server) for the installed versions of SQL Server.
+- Evaluate and apply the [latest cumulative updates](/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server) for the installed versions of SQL Server. For more information, see [Updating SQL Server on Azure VMs](servicing-updates-guidelines.md).
 - Enable [Query Store](/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store) on all production SQL Server databases [following best practices](/sql/relational-databases/performance/best-practice-with-the-query-store).
 - Enable [automatic tuning](/sql/relational-databases/automatic-tuning/automatic-tuning) on mission critical application databases.
 - Ensure that all [tempdb best practices](/sql/relational-databases/databases/tempdb-database#optimizing-tempdb-performance-in-sql-server) are followed.
@@ -125,6 +125,7 @@ The following checklist covers best practices for Azure-specific guidance when r
 - Implement a high availability and disaster recovery (HADR) solution that meets your business continuity SLAs. See the [HADR options](business-continuity-high-availability-disaster-recovery-hadr-overview.md#business-continuity-features) available for SQL Server on Azure VMs.
 - Use the Azure portal (support + troubleshooting) to evaluate [resource health](/azure/service-health/resource-health-overview) and history. Submit new support requests when needed.
 
+
 ## HADR configuration
 
 The checklist in this section covers the [HADR best practices](hadr-cluster-best-practices.md) for SQL Server on Azure VMs.
@@ -147,11 +148,12 @@ When you encounter SQL Server performance problems, use these diagnostic resourc
 
 For detailed guidance on each optimization area, see:
 
-- **[VM size](performance-guidelines-best-practices-vm-size.md)** - Choose the right VM series and configuration.
-- **[Storage](performance-guidelines-best-practices-storage.md)** - Optimize disk configuration and performance.
-- **[Security](security-considerations-best-practices.md)** - Implement security best practices.
-- **[HADR settings](hadr-cluster-best-practices.md)** - Configure high availability and disaster recovery.
-- **[Collect baseline](performance-guidelines-best-practices-collect-baseline.md)** - Establish performance baselines.
+- **[VM size](performance-guidelines-best-practices-vm-size.md)** - Choose the right VM series and configuration
+- **[Storage](performance-guidelines-best-practices-storage.md)** - Optimize disk configuration and performance
+- **[Security](security-considerations-best-practices.md)** - Implement security best practices
+- **[HADR settings](hadr-cluster-best-practices.md)** - Configure high availability and disaster recovery
+- **[Collect baseline](performance-guidelines-best-practices-collect-baseline.md)** - Establish performance baselines
+- **[Updating SQL Server](servicing-updates-guidelines.md)** - Keep SQL Server up to date
 
 **Recommended tool:** [Enable SQL Assessment for SQL Server on Azure VMs](sql-assessment-for-sql-vm.md) to automatically evaluate your configuration against these best practices.