Merge pull request #221771 from mimckitt/final-updates-before-merge

Final Updates before Merging

Author: Stacyrch140

articles/virtual-machine-scale-sets/tutorial-autoscale-cli.md

@@ -6,13 +6,12 @@ ms.author: jushiman
 ms.topic: tutorial
 ms.service: virtual-machine-scale-sets
 ms.subservice: autoscale
-ms.date: 11/22/2022
+ms.date: 12/16/2022
 ms.reviewer: mimckitt
 ms.custom: avverma, devx-track-azurecli
 
 ---
 # Tutorial: Automatically scale a Virtual Machine Scale Set with the Azure CLI
-
 When you create a scale set, you define the number of VM instances that you wish to run. As your application demand changes, you can automatically increase or decrease the number of VM instances. The ability to autoscale lets you keep up with customer demand or respond to application performance changes throughout the lifecycle of your app. In this tutorial you learn how to:
 
 > [!div class="checklist"]
@@ -28,14 +27,13 @@ When you create a scale set, you define the number of VM instances that you wish
 - This tutorial requires version 2.0.32 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
 
 ## Create a scale set
-
-Create a resource group with [az group create](/cli/azure/group) as follows:
+Create a resource group with [az group create](/cli/azure/group).
 
 ```azurecli-interactive
 az group create --name myResourceGroup --location eastus
 ```
 
-Now create a Virtual Machine Scale Set with [az vmss create](/cli/azure/vmss). The following example creates a scale set with an instance count of *2*, and generates SSH keys if they don't exist:
+Now create a Virtual Machine Scale Set with [az vmss create](/cli/azure/vmss). The following example creates a scale set with an instance count of *2*, and generates SSH keys if they don't exist.
 
 ```azurecli-interactive
 az vmss create \
@@ -49,7 +47,6 @@ az vmss create \
 ```
 
 ## Define an autoscale profile
-
 To enable autoscale on a scale set, you first define an autoscale profile. This profile defines the default, minimum, and maximum scale set capacity. These limits let you control cost by not continually creating VM instances, and balance acceptable performance with a minimum number of instances that remain in a scale-in event. Create an autoscale profile with [az monitor autoscale create](/cli/azure/monitor/autoscale#az-monitor-autoscale-create). The following example sets the default, and minimum, capacity of *2* VM instances, and a maximum of *10*:
 
 ```azurecli-interactive
@@ -64,7 +61,6 @@ az monitor autoscale create \
 ```
 
 ## Create a rule to autoscale out
-
 If your application demand increases, the load on the VM instances in your scale set increases. If this increased load is consistent, rather than just a brief demand, you can configure autoscale rules to increase the number of VM instances in the scale set. When these VM instances are created and your applications are deployed, the scale set starts to distribute traffic to them through the load balancer. You control what metrics to monitor, how long the application load must meet a given threshold, and how many VM instances to add to the scale set.
 
 Create a rule with [az monitor autoscale rule create](/cli/azure/monitor/autoscale/rule#az-monitor-autoscale-rule-create) that increases the number of VM instances in a scale set when the average CPU load is greater than 70% over a 5-minute period. When the rule triggers, the number of VM instances is increased by three.
@@ -78,10 +74,9 @@ az monitor autoscale rule create \
 ```
 
 ## Create a rule to autoscale in
-
 On an evening or weekend, your application demand may decrease. If this decreased load is consistent over a period of time, you can configure autoscale rules to decrease the number of VM instances in the scale set. This scale-in action reduces the cost to run your scale set as you only run the number of instances required to meet the current demand.
 
-Create another rule with [az monitor autoscale rule create](/cli/azure/monitor/autoscale/rule#az-monitor-autoscale-rule-create) that decreases the number of VM instances in a scale set when the average CPU load then drops below 30% over a 5-minute period. The following example defines the rule to scale in the number of VM instances by one:
+Create another rule with [az monitor autoscale rule create](/cli/azure/monitor/autoscale/rule#az-monitor-autoscale-rule-create) that decreases the number of VM instances in a scale set when the average CPU load then drops below 30% over a 5-minute period. The following example defines the rule to scale in the number of VM instances by one.
 
 ```azurecli-interactive
 az monitor autoscale rule create \
@@ -92,7 +87,6 @@ az monitor autoscale rule create \
 ```
 
 ## Generate CPU load on scale set
-
 To test the autoscale rules, generate some CPU load on the VM instances in the scale set. This simulated CPU load causes the autoscales to scale out and increase the number of VM instances. As the simulated CPU load is then decreased, the autoscale rules scale in and reduce the number of VM instances.
 
 To connect to an individual instance, see [Tutorial: Connect to Virtual Machine Scale Set instances](tutorial-connect-to-instances-cli.md)
@@ -142,7 +136,6 @@ exit
 ```
 
 ## Monitor the active autoscale rules
-
 To monitor the number of VM instances in your scale set, use **watch**. It takes 5 minutes for the autoscale rules to begin the scale-out process in response to the CPU load generated by **stress** on each of the VM instances:
 
 ```azurecli-interactive
@@ -169,21 +162,19 @@ Every 2.0s: az vmss list-instances --resource-group myResourceGroup --name mySca
 Once **stress** stops on the initial VM instances, the average CPU load returns to normal. After another 5 minutes, the autoscale rules then scale in the number of VM instances. Scale in actions remove VM instances with the highest IDs first. When a scale set uses Availability Sets or Availability Zones, scale in actions are evenly distributed across those VM instances. The following example output shows one VM instance deleted as the scale set autoscales in:
 
 ```output
-           6  True                  eastus      myScaleSet_6  Deleting             myResourceGroup  9e4133dd-2c57-490e-ae45-90513ce3b336
+6  True                  eastus      myScaleSet_6  Deleting             myResourceGroup  9e4133dd-2c57-490e-ae45-90513ce3b336
 ```
 
 Exit *watch* with `Ctrl-c`. The scale set continues to scale in every 5 minutes and remove one VM instance until the minimum instance count of two is reached.
 
 ## Clean up resources
-
 To remove your scale set and additional resources, delete the resource group and all its resources with [az group delete](/cli/azure/group). The `--no-wait` parameter returns control to the prompt without waiting for the operation to complete. The `--yes` parameter confirms that you wish to delete the resources without an additional prompt to do so.
 
 ```azurecli-interactive
 az group delete --name myResourceGroup --yes --no-wait
 ```
 
 ## Next steps
-
 In this tutorial, you learned how to automatically scale in or out a scale set with the Azure CLI:
 
 > [!div class="checklist"]

articles/virtual-machine-scale-sets/tutorial-autoscale-powershell.md

@@ -16,8 +16,6 @@ ms.custom: avverma, devx-track-azurepowershell
 > [!NOTE]
 > This tutorial uses Uniform Orchestration mode. We recommend using Flexible Orchestration for new workloads. For more information, see [Orchestration modes for Virtual Machine Scale Sets in Azure](virtual-machine-scale-sets-orchestration-modes.md).
 
-[!INCLUDE [requires-azurerm](../../includes/requires-azurerm.md)]
-
 When you create a scale set, you define the number of VM instances that you wish to run. As your application demand changes, you can automatically increase or decrease the number of VM instances. The ability to autoscale lets you keep up with customer demand or respond to application performance changes throughout the lifecycle of your app. In this tutorial you learn how to:
 
 > [!div class="checklist"]
@@ -244,7 +242,6 @@ To remove your scale set and additional resources, delete the resource group and
 Remove-AzureRmResourceGroup -Name "myResourceGroup" -Force -AsJob
 ```
 
-
 ## Next steps
 In this tutorial, you learned how to automatically scale in or out a scale set with Azure PowerShell:
 

articles/virtual-machine-scale-sets/tutorial-connect-to-instances-cli.md

@@ -5,14 +5,13 @@ author: ju-shim
 ms.author: jushiman
 ms.topic: tutorial
 ms.service: virtual-machine-scale-sets
-ms.date: 11/29/2022
+ms.date: 12/16/2022
 ms.reviewer: mimckitt
 ms.custom: mimckitt, devx-track-azurecli
 
 ---
 
 # Tutorial: Connect to Virtual Machine Scale Set instances using the Azure CLI
-
 A Virtual Machine Scale Set allows you to deploy and manage a set of virtual machines. Throughout the lifecycle of a Virtual Machine Scale Set, you may need to run one or more management tasks. In this tutorial you learn how to:
 
 > [!div class="checklist"]
@@ -25,9 +24,7 @@ A Virtual Machine Scale Set allows you to deploy and manage a set of virtual mac
 
 This article requires version 2.0.29 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed. 
 
-
 ## List instances in a scale set
-
 If you do not have a scale set already created, see [Tutorial: Create and manage a Virtual Machine Scale Set with the Azure CLI](tutorial-create-and-manage-cli.md)
 
 List all the instances in your Virtual Machine Scale Set. 
@@ -46,10 +43,8 @@ eastus      myScaleSet_0e7d4d21  myResourceGroup
 eastus      myScaleSet_39379fc3  myResourceGroup
 ```
 
-
 ## Get NIC information
-
-Using the VM name of the instance you want to connect to, use [az vm nic list](/cli/) to find the NIC name.
+Use [az vm nic list](/cli/azure/vm/nic#az-vm-nic-list) and the name of the individual VM instance to find the NIC name.
 
 ```azurecli-interactive
 az vm nic list \
@@ -68,7 +63,7 @@ az vm nic list \
 ]
 ```
 
-Using the VM name and NIC name, get the private IP address of the NIC, the Inbound NAT rule name and load balancer name using [az vm nic show](/cli).
+Using the VM name and NIC name, get the private IP address of the NIC, the Inbound NAT rule name and load balancer name using [az vm nic show](/cli/azure/vm/nic#az-vm-nic-show).
 
 
 ```azurecli-interactive
@@ -114,16 +109,14 @@ az vm nic show --resource-group myResourceGroup --vm-name myScaleSet_0e7d4d21 --
   "tapConfigurations": [],
   "type": "Microsoft.Network/networkInterfaces",
   "virtualMachine": {
-    "id": "/subscriptions/resourceGroups/MYRESOURCEGROUP/providers/Microsoft.Compute/virtualMachines/myScaleSet_0e7d4d21",
-    "resourceGroup": "MYRESOURCEGROUP"
+    "id": "/subscriptions/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myScaleSet_0e7d4d21",
+    "resourceGroup": "myResourceGroup"
   },
 }
 ```
 
-
 ## Get backend pool details
-Using the backend pool name and load balancer name, get the port for the private IP address of the instance you want to connect to.
-
+Using the backend pool name and load balancer name, get the port for the private IP address of the instance you want to connect to with [az network lb list-mapping](/cli/azure/network/lb#az-network-lb-list-mapping).
 
 ```azurecli-interactive
 az network lb list-mapping --backend-pool-name myScaleSetLBBEPool --resource-group myResourceGroup --name myScaleSetLB --request ip=10.0.0.5
@@ -143,8 +136,7 @@ az network lb list-mapping --backend-pool-name myScaleSetLBBEPool --resource-gro
 ```
 
 ## Get public IP of load balancer
-
-Get the public IP of the load balancer
+Get the public IP of the load balancer using [az network public-ip list](/cli/azure/network/public-ip#az-network-public-ip-list).
 
 ```azurecli-interactive
 az network public-ip list --resource-group myResourceGroup

articles/virtual-machine-scale-sets/tutorial-connect-to-instances-powershell.md

@@ -5,14 +5,13 @@ author: ju-shim
 ms.author: jushiman
 ms.topic: tutorial
 ms.service: virtual-machine-scale-sets
-ms.date: 11/29/2022
+ms.date: 12/16/2022
 ms.reviewer: mimckitt
 ms.custom: mimckitt, devx-track-azurepowershell
 
 ---
 
 # Tutorial: Connect to Virtual Machine Scale Set instances using Azure PowerShell
-
 A Virtual Machine Scale Set allows you to deploy and manage a set of virtual machines. Throughout the lifecycle of a Virtual Machine Scale Set, you may need to run one or more management tasks. In this tutorial you learn how to:
 
 > [!div class="checklist"]
@@ -21,13 +20,9 @@ A Virtual Machine Scale Set allows you to deploy and manage a set of virtual mac
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
-[!INCLUDE [updated-for-az.md](../../includes/updated-for-az.md)]
-
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
-
 ## List instances in a scale set
-
 If you don't have a scale set already created, see [Tutorial: Create and manage a Virtual Machine Scale Set with Azure PowerShell](tutorial-create-and-manage-powershell.md).
 
 List all the instances in your Virtual Machine Scale Set using [Get-AzVM](/powershell/module/az.compute/get-azvm).
@@ -43,11 +38,8 @@ myResourceGroup   myScaleSet_Instance1   eastus     Standard_DS1_v2    Windows
 myResourceGroup   myScaleSet_Instance2   eastus     Standard_DS1_v2    Windows    myScaleSet-instance2-nic    
 ```
 
-
 ## Get NIC information
-
-
-Using the NIC name, get the private IP address of the NIC, the backend address pool name and load balancer name using [Get-AzNetworkInterface](/powershell/module/az.network/get-aznetworkinterface).
+Using the NIC name, get the private IP address of the NIC, the backend address pool name and load balancer name with [Get-AzNetworkInterface](/powershell/module/az.network/get-aznetworkinterface).
 
 ```azurepowershell-interactive
 Get-AzNetworkInterface -Name myScaleSet-instance1-nic
@@ -97,10 +89,10 @@ Using the backend pool name, load balancer name and private IP address, get the
 
 ```azurepowershell-interactive
 Get-AzLoadBalancerBackendAddressInboundNatRulePortMapping `
-    -ResourceGroupName myResourceGroup `
-    -LoadBalancerName myScaleSet `
-    -Name myScaleSet `
-    -IpAddress 192.168.1.5
+  -ResourceGroupName myResourceGroup `
+  -LoadBalancerName myScaleSet `
+  -Name myScaleSet `
+  -IpAddress 192.168.1.5
 ```
 
 If you run the above command and find your load balancer doesn't have any inbound NAT rules, you can add inbound NAT rules using [Add-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/add-azloadbalancerinboundnatruleconfig). Once complete, run [Get-AzLoadBalancerBackendAddressInboundNatRulePortMapping](/powershell/module/az.network/add-azloadbalancerinboundnatruleconfig) again.
@@ -111,7 +103,6 @@ $slb | Add-AzLoadBalancerInboundNatRuleConfig -Name "myNatRule" -FrontendIPConfi
 $slb | Set-AzLoadBalancer
 ```
 
-    
 ```output
 InboundNatRuleName : myNatRule
 Protocol           : Tcp
@@ -120,7 +111,6 @@ BackendPort        : 3389
 ```
 
 ## Get public IP of load balancer
-
 Get the public IP of the load balancer using [GetAzPublicIpAddress](/powershell/module/az.network/get-azpublicipaddress).
 
 ```azurepowershell-interactive
@@ -152,7 +142,6 @@ Sku                      : {
 ```
 
 ## Connect to your instance
-
 Remote Desktop to your machine using the Public IP address of the load balancer and the Port mapping to the machine instance you want to connect to.
 
 :::image type="content" source="media/virtual-machine-scale-sets-connect-to-instances/tutorial-connect-to-instances-powershell-rdp.png" alt-text="Screenshot of remote desktop application from Windows machine.":::
@@ -167,4 +156,4 @@ In this tutorial, you learned how to list the instances in your scale set and co
 
 
 > [!div class="nextstepaction"]
-> [Modify a scale set](tutorial-modify-scale-sets-cli.md)
+> [Modify a scale set](tutorial-modify-scale-sets-powershell.md)