Document Details
Onboarding Requirements
❌
This page contains Windows bias
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
⚠️
missing_linux_example
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) command examples for onboarding and configuring Azure Large Instances, without offering equivalent Azure CLI or Linux shell examples. The instructions for enabling ExpressRoute Fast Path and related tasks are exclusively shown using PowerShell cmdlets, and there is no mention or example of how to perform these tasks using Linux-native tools or cross-platform CLI. Additionally, the guidance to install PowerShell modules is presented before any mention of Linux compatibility, and there is no explicit parity for Linux users.
Recommendations:
- Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all configuration steps, especially for ExpressRoute and networking setup.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links to relevant cross-platform documentation.
- Where PowerShell is required, clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide installation instructions for those platforms.
- Add Linux shell (bash) script examples for variable declaration and command execution, ensuring Linux users can follow the onboarding process without switching to Windows tools.
- Review all sections for implicit Windows-first language or assumptions, and ensure Linux and cross-platform scenarios are treated with equal prominence.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
New-AzureRmVirtualNetworkGatewayConnection -Name "Virtual Gateway connection name" -ResourceGroupName $RG1 -Location $Location1 -VirtualNetworkGateway1 $gw -PeerId $id -AuthorizationKey $Authkey -ConnectionType ExpressRoute -ExpressRouteGatewayBypass
$Sub = "Replace_With_Your_Subscription_ID"
$RG = "Your_Resource_Group_Name"
$CircuitName="ExpressRoute Circuit Name"
$Location="Location_Name" #Example: "East US"
$GWName="VNET_Gateway_Name"
$ConnectionName=”ER Gateway Connection Name”
$Authkey="ExpressRoute Circuit Authorization Key"
$gw = Get-AzVirtualNetworkGateway -Name $GWName1 -ResourceGroupName $RG1
Enable MSEEv2 using "ExpressRouteGatewayBypass" flag
$connection = New-AzVirtualNetworkGatewayConnection -Name $ConnectionName -ResourceGroupName $RG -ExpressRouteGatewayBypass -VirtualNetworkGateway1 $GW -PeerId $Circuit.Id -ConnectionType ExpressRoute -Location $Location -AuthorizationKey $Authkey