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:
⚠️
windows_first
⚠️
powershell_heavy
Summary:
The documentation consistently presents Azure PowerShell (a Windows-centric tool) instructions and examples before Azure CLI (cross-platform) equivalents in every section. The structure and language reinforce PowerShell as the primary or default approach, which can be perceived as a Windows-first bias. However, both PowerShell and CLI examples are provided throughout, and there are no missing Linux examples or exclusive references to Windows-only tools beyond PowerShell.
Recommendations:
- Alternate the order of PowerShell and CLI tabs in different sections to avoid always privileging PowerShell.
- Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and that users on Linux/macOS can use the CLI or PowerShell Core.
- Add a short note at the start clarifying that all steps can be performed on Linux, macOS, or Windows using the Azure CLI or PowerShell Core.
- Consider providing Bash script examples or references for Linux users where appropriate.
- Avoid language that implies PowerShell is the default or preferred method, and instead present both options as equally valid.
Create pull request
Flagged Code Snippets
# Sign in to Azure
Connect-AzAccount
# Set the subscription context to Azure Subscription A
Set-AzContext -Subscription '<Subscription ID of Subscription A>'
# Get the Virtual Network information with Get-AzVirtualNetwork
$rlb= @{
Name = 'load-balancer-regional'
ResourceGroupName = 'resource-group-a'
}
$rlbinfo = Get-AzLoadBalancer @rlb
$rlbfe = Get-AzLoadBalancerFrontendIpConfig @rlbinfo
---
## Create a resource group
In this section, you create a resource group in **Azure Subscription B**. This resource group is for all of your resources associate with your load balancer.
# [Azure PowerShell](#tab/azurepowershell)
With Azure PowerShell, you switch the subscription context with [`Set-AzContext`](/powershell/module/az.accounts/set-azcontext) and create a resource group with [`New-AzResourceGroup`](/powershell/module/az.resources/new-azresourcegroup).
> [!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.