About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
windows_tools
Summary:
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) instructions and examples before Azure CLI (cross-platform) equivalents. The structure and language prioritize PowerShell, and there is no mention of Linux-specific considerations, shells, or tooling. The use of PowerShell as the primary example and the presence of the 'devx-track-azurepowershell' custom metadata further reinforce the Windows-centric approach.
Recommendations:
- Alternate the order of examples so that Azure CLI (cross-platform) instructions are presented first in some sections, or present both equally without prioritizing one.
- Explicitly mention that Azure CLI works natively on Linux, macOS, and Windows, and provide shell-specific notes where relevant.
- Add a brief section or note on using Bash or other Linux shells with Azure CLI, including any differences in command syntax or environment setup.
- Review metadata and custom tags to ensure they do not reinforce a PowerShell/Windows bias (e.g., avoid 'devx-track-azurepowershell' unless equally tracking CLI).
- Where possible, provide guidance or troubleshooting tips for both Windows and Linux users, especially for environment setup and authentication steps.
Create pull request
Flagged Code Snippets
> [!NOTE]
> When create the resource group for your load balancer, use the same Azure region as the virtual network in **Azure Subscription A**.
---
## Create a global load balancer
In this section, you create the resources needed for the global load balancer.
A global standard sku public IP is used for the frontend of the global load balancer.
# [Azure PowerShell](#tab/azurepowershell)
With Azure PowerShell, you:
- Use [`New-AzPublicIpAddress`](/powershell/module/az.network/new-azpublicipaddress) to create the public IP address.
- Create a frontend IP configuration with [`New-AzLoadBalancerFrontendIpConfig`](/powershell/module/az.network/new-azloadbalancerfrontendipconfig).
- Create a backend address pool with [`New-AzLoadBalancerBackendAddressPoolConfig`](/powershell/module/az.network/new-azloadbalancerbackendaddresspoolconfig).
- Create a load balancer rule with [`Add-AzLoadBalancerRuleConfig`](/powershell/module/az.network/add-azloadbalancerruleconfig).
- Create a global load Balancer with [`New-AzLoadBalancer`](/powershell/module/az.network/new-azloadbalancer).
---
## Add load balancer frontends to global load balancer
In this section, you add a frontend IP configuration to the global load balancer.
# [Azure PowerShell](#tab/azurepowershell)
With Azure PowerShell, you:
- Use [`Set-AzLoadBalancerFrontendIpConfig`](/powershell/module/az.network/set-azloadbalancerfrontendipconfig) to add the regional load balancer frontend to the global backend pool.
- Use [`New-AzLoadBalancerBackendAddressConfig`](/powershell/module/az.network/new-azloadbalancerbackendaddressconfig) to create the backend address pool configuration for the load balancer.