Merge pull request #278296 from mimckitt/updates-9

updates

Author: prmerger-automator[bot]

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-change-upgrade-policy.md

@@ -1,5 +1,5 @@
 ---
-title: Change the upgrade policy on Virtual Machine Scale Sets
+title: Change the upgrade policy on Virtual Machine Scale Sets (Preview)
 description: Learn how to change the upgrade policy on Virtual Machine Scale Sets
 author: mimckitt
 ms.author: mimckitt
@@ -9,7 +9,7 @@ ms.date: 6/6/2024
 ms.reviewer: ju-shim
 ms.custom: upgradepolicy
 ---
-# Change the upgrade policy on Virtual Machine Scale Sets
+# Change the upgrade policy on Virtual Machine Scale Sets (Preview)
 
 > [!NOTE]
 > Automatic, manual and rolling upgrade policy for Virtual Machine Scale Sets with Uniform Orchestration are in general availability (GA) . 

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md

@@ -1,15 +1,15 @@
 ---
-title: Configure rolling upgrades on Virtual Machine Scale Sets
+title: Configure rolling upgrades on Virtual Machine Scale Sets (Preview)
 description: Learn about how to configure rolling upgrades on Virtual Machine Scale Sets.
 author: mimckitt
 ms.author: mimckitt
 ms.topic: how-to
 ms.service: virtual-machine-scale-sets
-ms.date: 6/6/2024
+ms.date: 6/14/2024
 ms.reviewer: ju-shim
 ms.custom: upgradepolicy, devx-track-azurepowershell
 ---
-# Configure rolling upgrades on Virtual Machine Scale Sets
+# Configure rolling upgrades on Virtual Machine Scale Sets (Preview)
 
 > [!NOTE]
 > Rolling upgrade policy for Virtual Machine Scale sets with Uniform Orchestration is in general availability (GA) . 
@@ -59,7 +59,7 @@ Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespac
 | **Max unhealthy upgrade %**| Specifies the total number of instances allowed to be marked as unhealthy after being upgraded. <br><br>Example: A max unhealthy upgrade % of 20 means if you have a scale set of 10 instances and more than two instances in the entire scale set report back as unhealthy after being upgraded, the rolling upgrade is canceled. <br><br>Max unhealthy upgrade % is an important setting because it allows the scale set to catch unstable or poor updates before they roll out to the entire scale set. |
 |**Prioritize unhealthy instances** | Tells the scale set to upgrade instances marked as unhealthy before upgrading instances marked as healthy. <br><br>Example: If some instances in your scale set that show as failed or unhealthy when a rolling upgrade begins, the scale set updates those instances first. |
 | **Enable cross-zone upgrade** | Allows the scale set to ignore Availability Zone boundaries when determining batches. |
-| **MaxSurge (preview)** | With MaxSurge enabled, new instances are created  in batches using the latest scale model. Once the batch of new instances are successfully created and marked as healthy, they begin taking traffic. The scale set then deletes instances in batches matching the old scale set model. This continues until all instances are brought up-to-date. rolling upgrades with MaxSurge can help improve service uptime during upgrade events. <br><br>With MaxSurge disabled, the existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances begin taking traffic again, and the next batch begins. This continues until all instances brought up-to-date. |
+| **MaxSurge (Preview)** | With MaxSurge enabled, new instances are created  in batches using the latest scale model. Once the batch of new instances are successfully created and marked as healthy, they begin taking traffic. The scale set then deletes instances in batches matching the old scale set model. This continues until all instances are brought up-to-date. rolling upgrades with MaxSurge can help improve service uptime during upgrade events. <br><br>With MaxSurge disabled, the existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances begin taking traffic again, and the next batch begins. This continues until all instances brought up-to-date. |
 
 
 ## Setting or updating the rolling upgrade policy

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md

@@ -1,15 +1,15 @@
 ---
-title: Performing manual upgrades on Virtual Machine Scale Sets
+title: Performing manual upgrades on Virtual Machine Scale Sets (Preview)
 description: Learn about how to perform a manual upgrade on Virtual Machine Scale Sets.
 author: mimckitt
 ms.author: mimckitt
 ms.topic: how-to
 ms.service: virtual-machine-scale-sets
-ms.date: 6/6/2024
+ms.date: 6/14/2024
 ms.reviewer: ju-shim
 ms.custom: upgradepolicy
 ---
-# Performing manual upgrades on Virtual Machine Scale Sets
+# Performing manual upgrades on Virtual Machine Scale Sets (Preview)
 
 > [!NOTE]
 > Manual upgrade policy for Virtual Machine Scale Sets with Uniform Orchestration is in general availability (GA) .

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-set-upgrade-policy.md

@@ -1,5 +1,5 @@
 ---
-title: Set the upgrade policy on Virtual Machine Scale Sets
+title: Set the upgrade policy on Virtual Machine Scale Sets (Preview)
 description: Learn about to set the upgrade policy on Virtual Machine Scale Sets
 author: mimckitt
 ms.author: mimckitt
@@ -9,7 +9,7 @@ ms.date: 6/6/2024
 ms.reviewer: ju-shim
 ms.custom: upgradepolicy
 ---
-# Set the upgrade policy on Virtual Machine Scale Sets
+# Set the upgrade policy on Virtual Machine Scale Sets (Preview)
 
 > [!NOTE]
 > Automatic, manual and rolling upgrade policy for Virtual Machine Scale Sets with Uniform Orchestration are in general availability (GA) . 

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-policy.md

@@ -1,15 +1,15 @@
 ---
-title: Upgrade policies for Virtual Machine Scale Sets
+title: Upgrade policies for Virtual Machine Scale Sets (Preview)
 description: Learn about the different upgrade policies available for Virtual Machine Scale Sets.
 author: mimckitt
 ms.author: mimckitt
 ms.topic: overview
 ms.service: virtual-machine-scale-sets
-ms.date: 6/6/2024
+ms.date: 6/14/2024
 ms.reviewer: ju-shim
 ms.custom: upgradepolicy
 ---
-# Upgrade policies for Virtual Machine Scale Sets
+# Upgrade policies for Virtual Machine Scale Sets (Preview)
 
 The upgrade policy of a Virtual Machine Scale Set determines how virtual machines can be brought up-to-date with the latest scale set model. 
 

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set.md

@@ -5,7 +5,7 @@ author: mimckitt
 ms.author: mimckitt
 ms.topic: how-to
 ms.service: virtual-machine-scale-sets
-ms.date: 6/6/2024
+ms.date: 6/14/2024
 ms.reviewer: ju-shim
 ms.custom: upgradepolicy
 

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones.md

@@ -6,7 +6,7 @@ ms.author: mimckitt
 ms.topic: conceptual
 ms.service: virtual-machine-scale-sets
 ms.subservice: availability
-ms.date: 5/22/2024
+ms.date: 6/14/2024
 ms.reviewer: jushiman
 ms.custom: mimckitt, devx-track-azurecli, devx-track-azurepowershell, devx-track-arm-template
 ---
@@ -290,7 +290,7 @@ You can update the zones parameter and the scale set capacity in the same ARM te
 
 When you are satisfied that the new instances are ready, scale in your scale set to remove the original regional instances. You can either manually delete the specific regional instances, or scale in by reducing the scale set capacity. When scaling in via reducing scale set capacity, the platform will always prefer removing the regional instances, then follow the scale in policy.
 
-#### Automate with rolling upgrades + MaxSurge (preview)
+#### Automate with rolling upgrades + MaxSurge (Preview)
 
 With [rolling upgrades + MaxSurge](virtual-machine-scale-sets-upgrade-policy.md), new zonal instances are created and brought up-to-date with the latest scale model in batches. Once a batch of new instances is added to the scale set and report as healthy, a batch of old instances are automated removed from the scale set. Upgrades continue until all instances are brought up-to-date.