Merge pull request #262818 from mbender-ms/lb-ado198522

Load Balancer - configure-vm-scale-set-portal.md - freshness

Author: JamesJBarnett

.openpublishing.redirection.json

@@ -12833,6 +12833,17 @@
             "redirect_url": "/azure/load-balancer/load-balancer-multiple-ip-powershell",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/load-balancer/configure-vm-scale-set-cli.md",
+            "redirect_url": "/azure/load-balancer/configure-vm-scale-set-portal",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/load-balancer/configure-vm-scale-set-powershell.md",
+            "redirect_url": "/azure/load-balancer/configure-vm-scale-set-portal",
+            "redirect_document_id": true
+        },
+
         {
             "source_path_from_root": "/articles/dms/tutorial-sql-server-azure-sql-online.md",
             "redirect_url": "/azure/dms/tutorial-sql-server-to-azure-sql",

articles/load-balancer/TOC.yml

@@ -188,12 +188,8 @@
       href: configure-inbound-NAT-rules-vm-scale-set.md
     - name: Add multiple Virtual Machine Scale Set instances behind one Azure Load Balancer
       href: load-balancer-multiple-virtual-machine-scale-set.md
-    - name: Use with an existing Azure Load Balancer - Portal
+    - name: Use Virtual Machine Scale Set instance with an existing Azure Load Balancer
       href: configure-vm-scale-set-portal.md
-    - name: Use with an existing Azure Load Balancer - PowerShell
-      href: configure-vm-scale-set-powershell.md
-    - name: Use with an existing Azure Load Balancer - CLI
-      href: configure-vm-scale-set-cli.md
   - name: Upgrade from a basic to standard load balancer
     items:
     - name: Upgrade options and guidance

articles/load-balancer/configure-vm-scale-set-cli.md

@@ -1,17 +1,19 @@
 ---
-title: Configure Virtual Machine Scale Set with an existing Azure Load Balancer - Azure portal
-description: Learn how to configure a Virtual Machine Scale Set with an existing Azure Load Balancer using the Azure portal.
+title: Configure Virtual Machine Scale Set with an existing Azure Load Balancer - Azure portal/CLI/PowerShell
+description: Learn to configure a Virtual Machine Scale Set with an existing Azure standard Load Balancer using the Azure portal, Azure CLI or Azure PowerShell.
 author: mbender-ms
 ms.author: mbender
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 12/15/2022
+ms.date: 01/11/2024
 ms.custom: template-quickstart, engagement-fy23
 ---
 
-# Configure a Virtual Machine Scale Set with an existing Azure Load Balancer using the Azure portal
+# Configure a Virtual Machine Scale Set with an existing Azure Standard Load Balancer
 
-In this article, you'll learn how to configure a Virtual Machine Scale Set with an existing Azure Load Balancer. 
+In this article, you'll learn how to configure a Virtual Machine Scale Set with an existing Azure Load Balancer. With an existing virtual network and standard sku load balancer, you can deploy a Virtual Machine Scale Set with a few clicks in the Azure portal, or with a few lines of code in the Azure CLI or Azure PowerShell using the tabs below.
+
+# [Azure Portal](#tab/portal)
 
 ## Prerequisites
 
@@ -23,8 +25,6 @@ In this article, you'll learn how to configure a Virtual Machine Scale Set with
 
 Sign in to the [Azure portal](https://portal.azure.com).
 
-
-
 ## Deploy Virtual Machine Scale Set with existing load balancer
 
 In this section, you'll create a Virtual Machine Scale Set in the Azure portal with an existing Azure load balancer.
@@ -87,6 +87,138 @@ In this section, you'll create a Virtual Machine Scale Set in the Azure portal w
 
 9. Review the settings and select the **Create** button.
 
+# [Azure CLI](#tab/cli)
+
+## Prerequisites 
+
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
+- You need an existing standard sku load balancer in the subscription where the Virtual Machine Scale Set will be deployed.
+
+- You need an Azure Virtual Network for the Virtual Machine Scale Set.
+ 
+[!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/articles/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
+
+- This article requires version 2.0.28 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
+
+## Deploy a Virtual Machine Scale Set with existing load balancer
+
+Deploy a Virtual Machine Scale Set with [`az vmss create`](/cli/azure/vmss#az-vmss-create).
+Replace the values in brackets with the names of the resources in your configuration.
+
+```azurecli-interactive
+az vmss create \
+    --resource-group <resource-group> \
+    --name <vmss-name>\
+    --image <your-image> \
+    --admin-username <admin-username> \
+    --generate-ssh-keys  \
+    --upgrade-policy-mode Automatic \
+    --instance-count 3 \
+    --vnet-name <virtual-network-name> \
+    --subnet <subnet-name> \
+    --lb <load-balancer-name> \
+    --backend-pool-name <backend-pool-name>
+```
+
+The below example deploys a Virtual Machine Scale Set with:
+
+- Virtual Machine Scale Set named **myVMSS**
+- Azure Load Balancer named **myLoadBalancer**
+- Load balancer backend pool named **myBackendPool**
+- Azure Virtual Network named **myVnet**
+- Subnet named **mySubnet**
+- Resource group named **myResourceGroup**
+- Ubuntu Server image for the Virtual Machine Scale Set
+
+```azurecli-interactive
+az vmss create \
+    --resource-group myResourceGroup \
+    --name myVMSS \
+    --image Canonical:UbuntuServer:18.04-LTS:latest \
+    --admin-username adminuser \
+    --generate-ssh-keys \
+    --upgrade-policy-mode Automatic \
+    --instance-count 3 \
+    --vnet-name myVnet\
+    --subnet mySubnet \
+    --lb myLoadBalancer \
+    --backend-pool-name myBackendPool
+```
+> [!NOTE]
+> After the scale set has been created, the backend port cannot be modified for a load balancing rule used by a health probe of the load balancer. To change the port, you can remove the health probe by updating the Azure virtual machine scale set, update the port and then configure the health probe again.
+
+
+# [Azure PowerShell](#tab/powershell)
+
+## Prerequisites
+
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- An existing resource group for all resources.
+- An existing standard sku load balancer in the subscription where the Virtual Machine Scale Set will be deployed.
+- An Azure Virtual Network for the Virtual Machine Scale Set.
+
+[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
+
+[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
+
+## Sign in to Azure CLI
+
+Sign into Azure with [`Connect-AzAccount`](/powershell/module/az.accounts/connect-azaccount#example-1-connect-to-an-azure-account)
+
+```azurepowershell-interactive
+Connect-AzAccount
+```
+
+## Deploy a Virtual Machine Scale Set with existing load balancer
+Deploy a Virtual Machine Scale Set with [`New-AzVMss`](/powershell/module/az.compute/new-azvmss). Replace the values in brackets with the names of the resources in your configuration.
+
+```azurepowershell-interactive
+
+$rsg = <resource-group>
+$loc = <location>
+$vms = <vm-scale-set-name>
+$vnt = <virtual-network>
+$sub = <subnet-name>
+$lbn = <load-balancer-name>
+$pol = <upgrade-policy-mode>
+$img = <image-name>
+$bep = <backend-pool-name>
+
+$lb = Get-AzLoadBalancer -ResourceGroupName $rsg -Name $lbn
+
+New-AzVmss -ResourceGroupName $rsg -Location $loc -VMScaleSetName $vms -VirtualNetworkName $vnt -SubnetName $sub -LoadBalancerName $lb -UpgradePolicyMode $pol
+
+```
+
+The below example deploys a Virtual Machine Scale Set with the following values:
+
+- Virtual Machine Scale Set named **myVMSS**
+- Azure Load Balancer named **myLoadBalancer**
+- Load balancer backend pool named **myBackendPool**
+- Azure Virtual Network named **myVnet**
+- Subnet named **mySubnet**
+- Resource group named **myResourceGroup**
+
+```azurepowershell-interactive
+
+$rsg = "myResourceGroup"
+$loc = "East US 2"
+$vms = "myVMSS"
+$vnt = "myVnet"
+$sub = "mySubnet"
+$pol = "Automatic"
+$lbn = "myLoadBalancer"
+$bep = "myBackendPool"
+
+$lb = Get-AzLoadBalancer -ResourceGroupName $rsg -Name $lbn
+
+New-AzVmss -ResourceGroupName $rsg -Location $loc -VMScaleSetName $vms -VirtualNetworkName $vnt -SubnetName $sub -LoadBalancerName $lb -UpgradePolicyMode $pol -BackendPoolName $bep
+
+```
+> [!NOTE]
+> After the scale set has been created, the backend port cannot be modified for a load balancing rule used by a health probe of the load balancer. To change the port, you can remove the health probe by updating the Azure virtual machine scale set, update the port and then configure the health probe again.
+
 ## Next steps
 
 In this article, you deployed a Virtual Machine Scale Set with an existing Azure Load Balancer.  To learn more about Virtual Machine Scale Sets and load balancer, see: