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 exclusively providing onboarding and configuration examples using Azure PowerShell cmdlets and Windows-style variable declarations. There are no equivalent CLI (az), Bash, or Linux-native examples for onboarding, managing ExpressRoute, or enabling features. The only mention of Linux is in the context of installing a Red Hat Satellite server, but no Linux command-line or automation examples are provided. The documentation assumes familiarity with PowerShell and Windows-centric tooling, which may disadvantage Linux users.
Recommendations:
- Provide equivalent Azure CLI (az) and Bash examples for all PowerShell commands and workflows, especially for ExpressRoute and network configuration.
- When introducing command-line examples, present both Windows/PowerShell and Linux/Bash/CLI options, or clearly indicate which platforms each example applies to.
- Explicitly mention Linux-compatible tools and patterns (such as Bash scripting, cloud-init, or Ansible) where appropriate.
- Ensure that references to enabling features (like Accelerated Networking) include links and steps for both Windows and Linux VMs.
- Review the order of presentation so that Linux and Windows are treated equally, or alternate which platform is presented first in examples.
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
Login-AzAccount
$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"
Get-AzSubscription
Select-AzSubscription -SubscriptionId $Sub1
$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
New-AzureRmVirtualNetworkGatewayConnection -Name "Virtual Gateway connection name" -ResourceGroupName $RG1 -Location $Location1 -VirtualNetworkGateway1 $gw -PeerId $id -AuthorizationKey $Authkey -ConnectionType ExpressRoute -ExpressRouteGatewayBypass