Merge pull request #33433 from MashaMSFT/2025_sqlvmsss

Azure VMSS supportability

Author: AnnaMHuff

azure-sql/includes/virtual-machines-best-practices-vm-size.md

@@ -18,3 +18,4 @@ ms.custom:
    - The [M-series family](../virtual-machines/windows/performance-guidelines-best-practices-vm-size.md#memory-optimized-m-series-vms) offers VMs with the highest memory allocation in Azure. 
    - The [Mbsv3 and Mbdsv3 series](../virtual-machines/windows/performance-guidelines-best-practices-vm-size.md#mbsv3-and-mbdsv3-series) VMs provide a high memory allocation and the highest I/O throughput-to-vCore ratio amongst the M-series family, along with a consistent memory-to-vCore ratio of at least 8:1. 
 - Start development environments with the lower-tier D-Series, B-Series, or Av2-series and grow your environment over time.
+- Check [VM supportability](../virtual-machines/windows/performance-guidelines-best-practices-vm-size.md#supportability) to avoid unsupported configurations.

azure-sql/virtual-machines/windows/frequently-asked-questions-faq.yml

@@ -107,7 +107,15 @@ sections:
           How can I migrate my on-premises SQL Server database to the cloud?
         answer: |
              First create an Azure virtual machine with a SQL Server instance. Then migrate your on-premises databases to that instance. For data migration strategies, see [Migration guide: SQL Server to SQL Server on Azure Virtual Machines](../../migration-guides/virtual-machines/sql-server-to-sql-on-azure-vm-individual-databases-guide.md).
-          
+
+      - question: |
+          Can I use Azure Virtual Machine Scale Sets (Azure VMSS) with SQL Server on Azure VMs?
+        answer: |
+             No. Using [Azure VMSS](/azure/virtual-machine-scale-sets/overview) is not supported with SQL Server on Azure VMs. Additionally, enabling the [Automatic guest patching feature](/azure/virtual-machines/automatic-vm-guest-patching) can lead to potential corruption, data loss, and availability issues. 
+
+
+
+
   - name: Licensing
     questions:
       - question: |
@@ -315,7 +323,7 @@ sections:
         answer:    Yes, for specific virtual machines in supported regions. Review [Premium SSDv2 with SQL Server on Azure VMs](storage-configuration-premium-ssd-v2.md) to learn more. If you would like to use Premium SSD v2 with a virtual machine type or region that isn't in the list, you might be able to do so by first deploying the VM, and then adding the Premium SSD v2 drives after the VM is created.
 
       - question: |
-          Why do I see **Not extendable** when I try to make changes to my storage in the SQL virtual machines resource? 
+          Why do I see "Not extendable" when I try to make changes to my storage in the SQL virtual machines resource? 
         answer:   Storage is only extendable for SQL Server VMs that were deployed from a SQL Server image in Azure Marketplace, and not currently supported for [Premium SSD v2](storage-configuration-premium-ssd-v2.md#adjust-performance-values) disks. 
 
   - name: SQL Server IaaS Agent extension

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

@@ -57,7 +57,7 @@ The following lists the capabilities of the M-series VMs:
 
 The Mbsv3 and Mbdsv3 series are memory optimized VMs designed for large in-memory databases and workloads with high memory-to-CPU ratio needs. The VMs in this series are built on the 4th generation Intel® Xeon® Scalable and offer a range of memory sizes and vCPU counts to meet the needs of your SQL Server workloads. The Mbsv3 and Mbdsv3 series VMs are recommended for mission critical and data warehouse workloads.
 
-The Mbsv3 and Mbdsv3 series VMs support support large in-memory databases and workloads with a high memory-to-CPU ratio perfect for relational database servers, data warehousing, heavy reporting, large caches, and in-memory analytics.
+The Mbsv3 and Mbdsv3 series VMs support large in-memory databases and workloads with a high memory-to-CPU ratio perfect for relational database servers, data warehousing, heavy reporting, large caches, and in-memory analytics.
 
 
 The following are characteristics of VMs in this series: 
@@ -202,6 +202,10 @@ For example, the [M64-32ms](/azure/virtual-machines/constrained-vcpu) requires l
 > - Medium to large data warehouse workloads may still benefit from [constrained vCore VMs](/azure/virtual-machines/constrained-vcpu), but data warehouse workloads are commonly characterized by fewer users and processes addressing larger amounts of data through query plans that run in parallel.
 > - The compute cost, which includes operating system licensing, will remain the same as the parent virtual machine.
 
+## Supportability
+
+[Azure Virtual Machine Scale Sets (VMSS)](/azure/virtual-machine-scale-sets/overview) are not supported with SQL Server on Azure VMs. If you decide to use VMSS with your SQL Server on Azure VM against this recommendation, and enable the [Automatic guest patching feature](/azure/virtual-machines/automatic-vm-guest-patching), which replaces the OS disk when a new image version is released, you will likely disrupt SQL Server, leading to potential corruption, data loss, and availability issues. 
+
 ## Next steps
 
 To learn more, see the other articles in this best practices series: