Integrating Microsoft Azure virtual machine scale sets with Azure load balancers can help you provide high availability for your web applications and improve application performance through scaling. 01 Sign in to Azure Management Portal. 02 Navigate to All resources blade at https://portal.azure.com/#blade/HubsExtension/BrowseAll to access all your Microsoft Azure resources. 03 Choose the Azure subscription that you want to access from the Subscription filter box. 04 From the Type filter box, select Virtual machine scale set to list only the Azure virtual machine scale sets created in the selected subscription. 05 Click on the name of the virtual machine scale set that you want to examine. 06 In the navigation panel, under Settings, choose Networking and select the Load balancing tab to view the load balancer attached to the selected scale set. If there is no load balancer listed on the Load balancing panel, the selected Azure virtual machine scale set is not associated with a Microsoft Azure load balancer. 07 Repeat step no. 5 and 6 for each Azure virtual machine scale set available in the selected subscription. 08 Repeat steps no. 3 – 7 for each subscription created in your Microsoft Azure cloud account. 01 Run account list command (Windows/macOS/Linux) using custom query filters to list the IDs of the subscriptions available in your Azure account: az account list --query '[*].id' 02 The command output should return the requested subscription identifiers (IDs): [ "abcdabcd-1234-abcd-1234-abcdabcdabcd", "abcd1234-abcd-1234-abcd-abcd1234abcd", ] 03 Run vmss list command (Windows/macOS/Linux) using custom query filters to list the name and the associated resource group of each virtual machine scale set available in the selected Azure subscription: az vmss list --subscription abcdabcd-1234-abcd-1234-abcdabcdabcd --output table --query '[*].{name:name, resourceGroup:resourceGroup}' 04 The command output should return the requested virtual machine scale set identifiers: Name ResourceGroup --------------------- ------------------------------ cc-web-prod-scale-set cloud-shell-storage-westeurope cc-project5-scale-set cloud-shell-storage-westeurope 05 Run vmss show command (Windows/macOS/Linux) using the name of the virtual machine scale set that you want to examine as identifier parameter, to describe the ID of the load balancer backend pool associated with the selected VM scale set: az vmss show --name cc-web-prod-scale-set --resource-group cloud-shell-storage-westeurope --query 'virtualMachineProfile.networkProfile.networkInterfaceConfigurations[*].ipConfigurations[*].loadBalancerBackendAddressPools[*].id | []' 06 The command output should return the requested backend pool identifier: If the vmss show command output returns an empty array, as shown in the example above, the selected Azure virtual machine scale set is not associated with an Azure load balancer. 07 Repeat step no. 5 and 6 for each Azure virtual machine scale set deployed in the selected subscription. 08 Repeat steps no. 3 – 10 for each subscription created in your Microsoft Azure cloud account. 01 Sign in to Azure Management Portal. 02 Navigate to Load balancers blade at https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Network%2FLoadBalancers. 03 Click on the Add button available in the blade top menu to initiate the load balancer setup process. 04 On the Create load balancer page, perform the following actions:
05 Click on name of the newly created Microsoft Azure load balancer. 06 Under Settings, select Backend pools, then click Add to create the backend pool required to distribute traffic to the virtual machines within the scale set. 07 On the Add backend pool page, perform the following:
08 To allow the new load balancer to monitor virtual (VM) machine instances status, you can configure a health probe. The health probe dynamically adds or removes VMs from the load balancer rotation based on their response to health checks. Under Settings, select Health probes, then click Add to create the required health probe. 09 On the Add health probe page, perform the following:
10 Once the health probe is active, continue the setup process with creating load balancer rules. A load balancer rule defines how traffic is distributed to the virtual machines (VMs). The rule defines the front-end IP configuration for incoming traffic, the back-end IP pool to receive the traffic, and the necessary ports for source and destination. Under Settings, select Load balancer rules, then click Add to create a new rule. 11 On the Add load balancing rule page, perform the following:
12 To determine if your Azure load balancer delivers traffic across all VM instances within the associated virtual machine scale set, use the public IP address (frontend IP) to test the traffic distribution. 13 Repeat steps no. 3 – 12 to implement load balancers for other Azure virtual machine scale sets available in the selected subscription. 14 Repeat steps no. 3 – 13 for each subscription available in your Microsoft Azure cloud account.
Publication date Jul 8, 2020
Unlock the Remediation Steps Free 30-day Trial Automatically audit your configurations with Conformity No thanks, back to article You are auditing: Check for Associated Load Balancers Risk level: Medium What enables you to provision a group of matching and load balanced virtual machines in Azure?Azure Virtual Machine Scale Sets let you create and manage a group of load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. Scale sets provide the following key benefits: Easy to create and manage multiple VMs.
Which of these is important to provision a VM in Azure?These aspects of a virtual machine are important to think about before you start: The names of your application resources. The location where the resources are stored. The size of the virtual machine.
Which Azure technology allows you to manage virtual machines running in Azure in your own environment?Azure Arc provides a centralized, unified way to: Manage your entire environment together by projecting your existing non-Azure and/or on-premises resources into Azure Resource Manager. Manage virtual machines, Kubernetes clusters, and databases as if they are running in Azure.
Which two options can you use to connect Azure virtual networks to each other each correct answer presents a complete solution?6. Which two options can you use to connect Azure Virtual Networks (Vnets)? Each correct answer presents a complete solution. Rationale: You should use VNet peering or VPN gateways to connect Azure Virtual Networks (VNets) to each other.
|