Merge pull request #105258 from ju-shim/vmss-mon

VMSS preview article updates

Author: Jak-MS

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

@@ -247,11 +247,11 @@
       href: virtual-machine-scale-sets-networking.md
     - name: Automatic OS upgrades
       href: virtual-machine-scale-sets-automatic-upgrade.md
-    - name: Instance protection (Preview)
+    - name: Instance protection
       href: virtual-machine-scale-sets-instance-protection.md
-    - name: Scale-In Policy (Preview)
+    - name: Scale-In Policy
       href: virtual-machine-scale-sets-scale-in-policy.md
-    - name: Terminate notification on delete (Preview)
+    - name: Terminate notification on delete
       href: virtual-machine-scale-sets-terminate-notification.md
     - name: Shared image galleries
       items:

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-instance-protection.md

@@ -1,24 +1,22 @@
 ---
 title: Instance Protection for Azure virtual machine scale set instances
 description: Learn how to protect Azure virtual machine scale set instances from scale-in and scale-set operations.
-author: mayanknayar
+author: avirishuv
 tags: azure-resource-manager
 ms.service: virtual-machine-scale-sets
 ms.topic: conceptual
-ms.date: 05/22/2019
-ms.author: manayar
+ms.date: 02/26/2020
+ms.author: avverma
 
 ---
-# Instance Protection for Azure virtual machine scale set instances (Preview)
+# Instance Protection for Azure virtual machine scale set instances
+
 Azure virtual machine scale sets enable better elasticity for your workloads through [Autoscale](virtual-machine-scale-sets-autoscale-overview.md), so you can configure when your infrastructure scales-out and when it scales-in. Scale sets also enable you to centrally manage, configure, and update a large number of VMs through different [upgrade policy](virtual-machine-scale-sets-upgrade-scale-set.md#how-to-bring-vms-up-to-date-with-the-latest-scale-set-model) settings. You can configure an update on the scale set model and the new configuration is applied automatically to every scale set instance if you've set the upgrade policy to Automatic or Rolling.
 
 As your application processes traffic, there can be situations where you want specific instances to be treated differently from the rest of the scale set instance. For example, certain instances in the scale set could be performing long-running operations, and you don't want these instances to be scaled-in until the operations complete. You might also have specialized a few instances in the scale set to perform additional or different tasks than the other members of the scale set. You require these 'special' VMs not to be modified with the other instances in the scale set. Instance protection provides the additional controls to enable these and other scenarios for your application.
 
 This article describes how you can apply and use the different instance protection capabilities with scale set instances.
 
-> [!NOTE]
->Instance protection is currently in Public Preview. No opt-in procedure is needed to use the public preview functionality described below. Instance protection preview is only supported with API version 2019-03-01 and on scale sets using managed disks.
-
 ## Types of instance protection
 Scale sets provide two types of instance protection capabilities:
 
@@ -40,6 +38,17 @@ Instance protection can be applied to scale set instances after the instances ar
 
 There are multiple ways of applying scale-in protection on your scale set instances as detailed in the examples below.
 
+### Azure portal
+
+You can apply scale-in protection through the Azure portal to an instance in the scale set. You cannot adjust more than one instance at a time. Repeat the steps for each instance you want to protect.
+ 
+1. Go to an existing virtual machine scale set.
+1. Select **Instances** from the menu on the left, under **Settings**.
+1. Select the name of the instance you want to protect.
+1. Select the **Protection Policy** tab.
+1. In the **Protection Policy** blade, select the **Protect from scale-in** option.
+1. Select **Save**. 
+
 ### REST API
 
 The following example applies scale-in protection to an instance in the scale set.
@@ -97,6 +106,17 @@ Protecting an instance from scale set actions also protects the instance from Au
 
 There are multiple ways of applying scale set actions protection on your scale set instances as detailed in the examples below.
 
+### Azure portal
+
+You can apply protection from scale set actions through the Azure portal to an instance in the scale set. You cannot adjust more than one instance at a time. Repeat the steps for each instance you want to protect.
+ 
+1. Go to an existing virtual machine scale set.
+1. Select **Instances** from the menu on the left, under **Settings**.
+1. Select the name of the instance you want to protect.
+1. Select the **Protection Policy** tab.
+1. In the **Protection Policy** blade, select the **Protect from scale set actions** option.
+1. Select **Save**. 
+
 ### REST API
 
 The following example applies protection from scale set actions to an instance in the scale set.

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

@@ -1,30 +1,30 @@
 ---
 title: Use custom scale-in policies with Azure virtual machine scale sets
 description: Learn how to use custom scale-in policies with Azure virtual machine scale sets that use autoscale configuration to manage instance count
-author: avverma
+services: virtual-machine-scale-sets
+author: avirishuv
+manager: vashan
 tags: azure-resource-manager
 
 ms.service: virtual-machine-scale-sets
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm
 ms.topic: conceptual
-ms.date: 10/11/2019
+ms.date: 02/26/2020
 ms.author: avverma
 
 ---
 
-# Preview: Use custom scale-in policies with Azure virtual machine scale sets
+# Use custom scale-in policies with Azure virtual machine scale sets
 
-A virtual machine scale set deployment can be scaled-out or scaled-in based on an array of metrics, including platform and user-defined custom metrics. While a scale-out creates new Virtual Machines based on the scale set model, a scale-in affects running virtual machines that may have different configurations and/or functions as the scale set workload evolves. 
+A virtual machine scale set deployment can be scaled-out or scaled-in based on an array of metrics, including platform and user-defined custom metrics. While a scale-out creates new virtual machines based on the scale set model, a scale-in affects running virtual machines that may have different configurations and/or functions as the scale set workload evolves. 
 
-The scale-in policy feature provides users a way to configure the order in which virtual machines are scaled-in. The Preview introduces three scale-in configurations: 
+The scale-in policy feature provides users a way to configure the order in which virtual machines are scaled-in, by way of three scale-in configurations: 
 
 1. Default
 2. NewestVM
 3. OldestVM
 
-***This preview feature is provided without a service level agreement, and it's not recommended for production workloads.***
-
 ### Default scale-in policy
 
 By default, virtual machine scale set applies this policy to determine which instance(s) will be scaled in. With the *Default* policy, VMs are selected for scale-in in the following order:
@@ -35,7 +35,7 @@ By default, virtual machine scale set applies this policy to determine which ins
 
 Users do not need to specify a scale-in policy if they just want the default ordering to be followed.
 
-Note that balancing across availability zones or fault domains does not move instances across availability zones or fault domains. The balancing is achieved through deletion of virtual machines from the unbalanced availability zones or fault domains till the distribution of virtual machines becomes balanced.
+Note that balancing across availability zones or fault domains does not move instances across availability zones or fault domains. The balancing is achieved through deletion of virtual machines from the unbalanced availability zones or fault domains until the distribution of virtual machines becomes balanced.
 
 ### NewestVM scale-in policy
 
@@ -51,6 +51,17 @@ A scale-in policy is defined in the virtual machine scale set model. As noted in
 
 A scale-in policy can be defined on the virtual machine scale set model in the following ways:
 
+### Azure portal
+ 
+The following steps define the scale-in policy when creating a new scale set. 
+ 
+1. Go to **Virtual machine scale sets**.
+1. Select **+ Add** to create a new scale set.
+1. Go to the **Scaling** tab. 
+1. Locate the **Scale-in policy** section.
+1. Select a scale-in policy from the drop-down.
+1. When you are done creating the new scale set, select **Review + create** button.
+
 ### Using API
 
 Execute a PUT on the virtual machine scale set using API 2019-03-01:
@@ -68,6 +79,33 @@ https://management.azure.com/subscriptions/<sub-id>/resourceGroups/<myRG>/provid
     }    
 } 
 ```
+### Azure PowerShell
+
+Create a resource group, then create a new scale set with scale-in policy set as *OldestVM*.
+
+```azurepowershell-interactive
+New-AzResourceGroup -ResourceGroupName "myResourceGroup" -Location "<VMSS location>"
+New-AzVmss `
+  -ResourceGroupName "myResourceGroup" `
+  -Location "<VMSS location>" `
+  -VMScaleSetName "myScaleSet" `
+  -ScaleInPolicy “OldestVM”
+```
+
+### Azure CLI 2.0
+
+The following example adds a scale-in policy while creating a new scale set. First create a resource group, then create a new scale set with scale-in policy as *OldestVM*. 
+
+```azurecli-interactive
+az group create --name <myResourceGroup> --location <VMSSLocation>
+az vmss create \
+  --resource-group <myResourceGroup> \
+  --name <myVMScaleSet> \
+  --image UbuntuLTS \
+  --admin-username <azureuser> \
+  --generate-ssh-keys \
+  --scale-in-policy OldestVM
+```
 
 ### Using Template
 
@@ -91,6 +129,15 @@ The same process applies when using ‘NewestVM’ in the above scale-in policy.
 
 Modifying the scale-in policy follows the same process as applying the scale-in policy. For example, if in the above example, you want to change the policy from ‘OldestVM’ to ‘NewestVM’, you can do so by:
 
+### Azure portal
+
+You can modify the scale-in policy of an existing scale set through the Azure portal. 
+ 
+1. In an existing virtual machine scale set, select **Scaling** from the menu on the left.
+1. Select the **Scale-In Policy** tab.
+1. Select a scale-in policy from the drop-down.
+1. When you are done, select **Save**. 
+
 ### Using API
 
 Execute a PUT on the virtual machine scale set using API 2019-03-01:
@@ -108,6 +155,27 @@ https://management.azure.com/subscriptions/<sub-id>/resourceGroups/<myRG>/provid
     }    
 }
 ```
+### Azure PowerShell
+
+Update the scale-in policy of an existing scale set:
+
+```azurepowershell-interactive
+Update-AzVmss `
+ -ResourceGroupName "myResourceGroup" `
+ -VMScaleSetName "myScaleSet" `
+ -ScaleInPolicy “OldestVM”
+```
+
+### Azure CLI 2.0
+
+The following is an example for updating the scale-in policy of an existing scale set: 
+
+```azurecli-interactive
+az vmss update \  
+  --resource-group <myResourceGroup> \
+  --name <myVMScaleSet> \
+  --scale-in-policy OldestVM
+```
 
 ### Using Template
 
@@ -167,11 +235,11 @@ For non-zonal virtual machine scale sets, the policy selects the newest VM acros
 ## Troubleshoot
 
 1. Failure to enable scaleInPolicy
-    If you get a ‘BadRequest’ error with an error message stating "Could not find member 'scaleInPolicy' on object of type 'properties'”, then check the API version used for virtual machine scale set. API version 2019-03-01 or higher is required for this preview.
+    If you get a ‘BadRequest’ error with an error message stating "Could not find member 'scaleInPolicy' on object of type 'properties'”, then check the API version used for virtual machine scale set. API version 2019-03-01 or higher is required for this feature.
 
 2. Wrong selection of VMs for scale-in
     Refer to the examples above. If your virtual machine scale set is a Zonal deployment, scale-in policy is applied first to the imbalanced Zones and then across the scale set once it is zone balanced. If the order of scale-in is not consistent with the examples above, raise a query with the virtual machine scale set team for troubleshooting.
 
 ## Next steps
 
-Learn how to [deploy your application](virtual-machine-scale-sets-deploy-app.md) on virtual machine scale sets.
+Learn how to [deploy your application](virtual-machine-scale-sets-deploy-app.md) on virtual machine scale sets.