Merge pull request #263323 from MicrosoftDocs/release-branch-upgrade-policies

Standing PR for Upgrade Policies Work (Do Not Merge)

Author: huypub

articles/load-balancer/load-balancer-basic-upgrade-guidance.md

@@ -86,10 +86,10 @@ Suggested order of operations for manually upgrading a Basic Load Balancer in co
     1. Load balancing rules - use the temporary frontend configuration
     1. NAT rules - use the temporary frontend configuration
 1. For public load balancers, if you do not have one already, [create a new Network Security Group](../virtual-network/tutorial-filter-network-traffic.md) with allow rules for the traffic coming through the Load Balancer rules
-1. For Virtual Machine Scale Set backends, remove the Load Balancer association in the Networking settings and [update the instances](../virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-policy.md#performing-manual-upgrades) 
+1. For Virtual Machine Scale Set backends, remove the Load Balancer association in the Networking settings and [update the instances](../virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md) 
 1. Delete the Basic Load Balancer 
    > [!NOTE]
-   > For Virtual Machine Scale Set backends, you will need to remove the load balancer association in the Networking settings. Once removed, you will also need to [**update the instances**](../virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-policy.md#performing-manual-upgrades) 
+   > For Virtual Machine Scale Set backends, you will need to remove the load balancer association in the Networking settings. Once removed, you will also need to [**update the instances**](../virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md) 
 1. [Upgrade all Public IPs](../virtual-network/ip-services/public-ip-upgrade-portal.md) previously associated with the Basic Load Balancer and backend Virtual Machines to Standard SKU. For Virtual Machine Scale Sets, remove any instance-level public IP configuration, update the instances, then add a new one with Standard SKU and update the instances again. 
 1. Recreate the frontend configurations from the Basic Load Balancer on the newly created Standard Load Balancer, using the same public or private IP addresses as on the Basic Load Balancer
 1. Update the load balancing and NAT rules to use the appropriate frontend configurations

articles/virtual-machine-scale-sets/TOC.yml

@@ -80,6 +80,8 @@
   - name: Predictive autoscale
     href: ../azure-monitor/autoscale/autoscale-predictive.md
     maintainContext: true
+  - name: Autoscale using guest metrics
+    href: virtual-machine-scale-sets-mvss-guest-based-autoscale-linux.md
   - name: Troubleshoot autoscale
     href: virtual-machine-scale-sets-troubleshoot.md 
   - name: Scale-In Policy
@@ -125,22 +127,32 @@
       href: azure-hybrid-benefit-linux.md
 - name: Management
   items: 
-  - name: Manage Upgrade Policies
-    href: virtual-machine-scale-sets-upgrade-policy.md
+  - name: Modify a scale set
+    href: virtual-machine-scale-sets-upgrade-scale-set.md
+  - name: Upgrade Policies
+    items:
+    - name: Overview
+      href: virtual-machine-scale-sets-upgrade-policy.md
+    - name: Setting the upgrade policy
+      href: virtual-machine-scale-sets-set-upgrade-policy.md
+    - name: Changing the upgrade policy
+      href: virtual-machine-scale-sets-change-upgrade-policy.md
+    - name: Configure rolling upgrade policy
+      href: virtual-machine-scale-sets-configure-rolling-upgrades.md 
+    - name: Performing manual upgrades
+      href: virtual-machine-scale-sets-perform-manual-upgrades.md
+    - name: Reimage a virtual machine
+      href: virtual-machine-scale-sets-reimage-virtual-machine.md
   - name: Common management tasks
     items:
     - name: Use the Azure CLI
       href: virtual-machine-scale-sets-manage-cli.md
     - name: Use Azure PowerShell
       href: virtual-machine-scale-sets-manage-powershell.md
-    - name: Modify a scale set
-      href: virtual-machine-scale-sets-upgrade-scale-set.md
     - name: Using DSC and scale sets
       href: virtual-machine-scale-sets-dsc.md
     - name: Scale set templates
       href: virtual-machine-scale-sets-mvss-start.md
-    - name: Autoscale using guest metrics
-      href: virtual-machine-scale-sets-mvss-guest-based-autoscale-linux.md
     - name: Deploy your application
       href: virtual-machine-scale-sets-deploy-app.md
     - name: Custom image templates

articles/virtual-machine-scale-sets/media/upgrade-policy/change-upgrade-policy.png

@@ -0,0 +1,63 @@
+---
+title: Change the upgrade policy on Virtual Machine Scale Sets
+description: Learn how to change the upgrade policy on Virtual Machine Scale Sets
+author: mimckitt
+ms.author: mimckitt
+ms.topic: how-to
+ms.service: virtual-machine-scale-sets
+ms.date: 03/07/2024
+ms.reviewer: ju-shim
+ms.custom: upgradepolicy
+---
+# Change the upgrade policy on Virtual Machine Scale Sets
+
+> [!NOTE]
+> Automatic, manual and rolling upgrade policy is available for Virtual Machine Scale sets with Uniform Orchestration. 
+>
+>**Manual upgrade policy is currently available for Virtual Machine Scale Sets with Flexible Orchestration and is currently in preview**. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of these features may change prior to general availability (GA).
+
+The upgrade policy for a Virtual Machine Scale Set can be changed at any point in time. Depending on your scenario, you may want to use a particular upgrade policy when setting up and developing your workload and once you're ready to move to production, change it to another upgrade policy mode. 
+
+### [Portal](#tab/portal)
+
+Select the Virtual Machine Scale Set you want to change the upgrade policy for. In the menu under **Settings**, select **Upgrade Policy** and from the drop-down menu, select the upgrade policy you want to enable. 
+
+If using a rolling upgrade policy, see [configure rolling upgrade policy](virtual-machine-scale-sets-configure-rolling-upgrades.md) for more configuration options and suggestions.
+
+:::image type="content" source="../virtual-machine-scale-sets/media/upgrade-policy/change-upgrade-policy.png" alt-text="Screenshot showing changing the upgrade policy and enabling MaxSurge in the Azure portal.":::
+
+
+### [PowerShell](#tab/powershell)
+Update an existing Virtual Machine Scale Set using [Update-AzVmss](/powershell/module/az.compute/update-azvmss) and the `-UpgradePolicyMode` to set the upgrade policy mode. 
+
+If using a rolling upgrade policy, see [configure rolling upgrade policy](virtual-machine-scale-sets-configure-rolling-upgrades.md) for more configuration options and suggestions.
+
+```azurepowershell-interactive
+$vmss = Get-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet"
+
+Update-Azvmss `
+    -ResourceGroupName "myResourceGroup" `
+    -Name "myScaleSet" `
+    -UpgradePolicyMode "Manual" `
+    -VirtualMachineScaleSet $vmss
+```
+
+### [ARM Template](#tab/template)
+
+Update the properties section of your ARM template with the upgrade policy to set the upgrade policy mode. 
+
+If using a rolling upgrade policy, see [configure rolling upgrade policy](virtual-machine-scale-sets-configure-rolling-upgrades.md) for more configuration options and suggestions.
+
+
+```ARM
+"properties": {
+        "upgradePolicy": {
+            "mode": "manual",
+        }
+    }
+```
+---
+
+
+## Next steps
+Learn how to [configure rolling upgrade policy](virtual-machine-scale-sets-configure-rolling-upgrades.md) on Virtual Machine Scale Sets.