Merge pull request #221884 from MicrosoftDocs/release-vmss-tutorials

Merge VMSS Tutorials

Author: Stacyrch140

articles/virtual-machine-scale-sets/.openpublishing.redirection.virtual-machine-scale-sets.json

@@ -55,6 +55,11 @@
             "redirect_url": "/azure/virtual-machine-scale-sets/quick-create-template-linux",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/virtual-machine-scale-sets/tutorial-install-apps-template.md",
+            "redirect_url": "/azure/virtual-machine-scale-sets/tutorial-install-apps-cli",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-deploy-scaling-app-template.md",
             "redirect_url": "/azure/virtual-machine-scale-sets/quick-create-template-linux",

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

@@ -26,33 +26,43 @@
     href: flexible-virtual-machine-scale-sets-rest-api.md
 - name: Tutorials
   items: 
-  - name: 1 - Create / manage scale set
+  - name: Create and manage
     items:
     - name: Azure CLI
       href: tutorial-create-and-manage-cli.md
     - name: Azure PowerShell
       href: tutorial-create-and-manage-powershell.md
-  - name: 2 - Use data disks
+  - name: Connect to Instances
+    items: 
+    - name: Azure CLI
+      href: tutorial-connect-to-instances-cli.md
+    - name: Azure PowerShell
+      href: tutorial-connect-to-instances-powershell.md
+  - name: Modify a scale set
+    items:
+    - name: Azure CLI
+      href: tutorial-modify-scale-sets-cli.md
+    - name: Azure PowerShell
+      href: tutorial-modify-scale-sets-powershell.md
+  - name: Use data disks
     items:
     - name: Azure CLI
       href: tutorial-use-disks-cli.md
     - name: Azure PowerShell
       href: tutorial-use-disks-powershell.md
-  - name: 3 - Use a custom VM image
+  - name: Use a custom VM image
     items:
     - name: Azure CLI
       href: tutorial-use-custom-image-cli.md
     - name: Azure PowerShell
       href: tutorial-use-custom-image-powershell.md
-  - name: 4 - Deploy apps to a scale set
+  - name: Deploy apps to a scale set
     items:
     - name: Azure CLI
       href: tutorial-install-apps-cli.md
     - name: Azure PowerShell
       href: tutorial-install-apps-powershell.md
-    - name: Template
-      href: tutorial-install-apps-template.md
-  - name: 5 - Autoscale a scale set
+  - name: Autoscale a scale set
     items:
     - name: Azure CLI
       href: tutorial-autoscale-cli.md

articles/virtual-machine-scale-sets/media/virtual-machine-scale-sets-connect-to-instances/tutorial-connect-to-instances-powershell-rdp.png

@@ -6,16 +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
-
-> [!NOTE]
-> This tutorial uses Uniform Orchestration mode. We recommend using Flexible Orchestration for new workloads. For more information, see [Orchesration modes for Virtual Machine Scale Sets in Azure](virtual-machine-scale-sets-orchestration-modes.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"]
@@ -31,28 +27,26 @@ 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 do not 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 \
   --resource-group myResourceGroup \
   --name myScaleSet \
   --image UbuntuLTS \
-  --upgrade-policy-mode automatic \
+  --orchestration-mode Flexible \
   --instance-count 2 \
   --admin-username azureuser \
   --generate-ssh-keys
 ```
 
 ## 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
@@ -67,10 +61,9 @@ 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.
 
-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, such as CPU or disk, how long the application load must meet a given threshold, and how many VM instances to add to the scale set.
-
-Let's 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.
+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.
 
 ```azurecli-interactive
 az monitor autoscale rule create \
@@ -81,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 \
@@ -95,31 +87,9 @@ 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.
 
-First, list the address and ports to connect to VM instances in a scale set with [az vmss list-instance-connection-info](/cli/azure/vmss):
-
-```azurecli-interactive
-az vmss list-instance-connection-info \
-  --resource-group myResourceGroup \
-  --name myScaleSet
-```
-
-The following example output shows the instance name, public IP address of the load balancer, and port number that the Network Address Translation (NAT) rules forward traffic to:
-
-```json
-{
-  "instance 1": "13.92.224.66:50001",
-  "instance 3": "13.92.224.66:50003"
-}
-```
-
-SSH to your first VM instance. Specify your own public IP address and port number with the `-p` parameter, as shown from the preceding command:
-
-```console
-ssh [email protected] -p 50001
-```
+To connect to an individual instance, see [Tutorial: Connect to Virtual Machine Scale Set instances](tutorial-connect-to-instances-cli.md)
 
 Once logged in, install the **stress** utility. Start *10* **stress** workers that generate CPU load. These workers run for *420* seconds, which is enough to cause the autoscale rules to implement the desired action.
 
@@ -166,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
@@ -193,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-cli.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: