Document Details
Hana Connect Vnet Express Route
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
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell instructions. The text refers to PowerShell as the primary scripting environment for automation, and there are no Linux-native tools or workflows mentioned. Although the service is for 'virtual-machines-linux', the documentation assumes the user is operating from a Windows or PowerShell environment. The Azure portal is mentioned, but when it comes to scripting, only PowerShell is covered.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Explicitly mention that all steps can be performed from Linux or macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where possible, include Bash shell script examples or guidance for Linux users.
- Reorder instructions or provide parallel sections so that Linux-native (CLI/Bash) instructions are not always secondary to Windows/PowerShell.
- Clarify in the prerequisites or introduction that the instructions are not limited to Windows environments, and highlight cross-platform options.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2025-09-11 00:00 | #108 | completed |
 Clean
|
| 2025-08-11 00:00 | #77 | completed |
Clean
|
| 2025-08-10 00:00 | #76 | completed |
Clean
|
| 2025-08-09 00:00 | #75 | completed |
Clean
|
| 2025-08-08 00:00 | #74 | completed |
Clean
|
| 2025-08-07 00:00 | #73 | completed |
Clean
|
| 2025-08-06 00:00 | #72 | completed |
Clean
|
| 2025-08-05 00:00 | #71 | completed |
Clean
|
| 2025-08-03 00:00 | #69 | completed |
Clean
|
| 2025-08-01 00:00 | #67 | completed |
Clean
|
| 2025-07-31 00:00 | #66 | completed |
Clean
|
| 2025-07-30 00:00 | #65 | completed |
Clean
|
| 2025-07-29 00:01 | #64 | completed |
Clean
|
| 2025-07-28 00:00 | #63 | completed |
Clean
|
| 2025-07-27 00:00 | #62 | completed |
Clean
|
| 2025-07-26 00:01 | #61 | completed |
Clean
|
| 2025-07-25 00:00 | #60 | completed |
Clean
|
| 2025-07-24 00:00 | #59 | completed |
Clean
|
| 2025-07-23 00:00 | #58 | completed |
Clean
|
| 2025-07-22 00:01 | #57 | completed |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
# Populate with information provided by Microsoft Onboarding team
$PeerID = "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/Customer-USE-Circuits/providers/Microsoft.Network/expressRouteCircuits/Customer-USE01"
$AuthGUID = "76d40466-c458-4d14-adcf-3d1b56d1cd61"
# Your ExpressRoute Gateway information
$myGroupName = "SAP-East-Coast"
$myGWName = "VNet01GW"
$myGWLocation = "East US"
# Define the name for your connection
$myConnectionName = "VNet01GWConnection"
# Create a new connection between the ER Circuit and your Gateway using the Authorization
$gw = Get-AzVirtualNetworkGateway -Name $myGWName -ResourceGroupName $myGroupName
New-AzVirtualNetworkGatewayConnection -Name $myConnectionName `
-ResourceGroupName $myGroupName -Location $myGWLocation -VirtualNetworkGateway1 $gw `
-PeerId $PeerID -ConnectionType ExpressRoute -AuthorizationKey $AuthGUID -ExpressRouteGatewayBypass
# These Values should already exist, update to match your environment
$myAzureRegion = "eastus"
$myGroupName = "SAP-East-Coast"
$myVNetName = "VNet01"
# These values are used to create the gateway, update for how you wish the GW components to be named
$myGWName = "VNet01GW"
$myGWConfig = "VNet01GWConfig"
$myGWPIPName = "VNet01GWPIP"
$myGWSku = "UltraPerformance" # Supported values for HANA large instances are: UltraPerformance
# These Commands create the Public IP and ExpressRoute Gateway
$vnet = Get-AzVirtualNetwork -Name $myVNetName -ResourceGroupName $myGroupName
$subnet = Get-AzVirtualNetworkSubnetConfig -Name 'GatewaySubnet' -VirtualNetwork $vnet
New-AzPublicIpAddress -Name $myGWPIPName -ResourceGroupName $myGroupName `
-Location $myAzureRegion -AllocationMethod Dynamic
$gwpip = Get-AzPublicIpAddress -Name $myGWPIPName -ResourceGroupName $myGroupName
$gwipconfig = New-AzVirtualNetworkGatewayIpConfig -Name $myGWConfig -SubnetId $subnet.Id `
-PublicIpAddressId $gwpip.Id
New-AzVirtualNetworkGateway -Name $myGWName -ResourceGroupName $myGroupName -Location $myAzureRegion `
-IpConfigurations $gwipconfig -GatewayType ExpressRoute `
-GatewaySku $myGWSku -VpnType PolicyBased -EnableBgp $true
# Populate with information provided by Microsoft Onboarding team
$PeerID = "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/Customer-USE-Circuits/providers/Microsoft.Network/expressRouteCircuits/Customer-USE01"
$AuthGUID = "76d40466-c458-4d14-adcf-3d1b56d1cd61"
# Your ExpressRoute Gateway information
$myGroupName = "SAP-East-Coast"
$myGWName = "VNet01GW"
$myGWLocation = "East US"
# Define the name for your connection
$myConnectionName = "VNet01GWConnection"
# Create a new connection between the ER Circuit and your Gateway using the Authorization
$gw = Get-AzVirtualNetworkGateway -Name $myGWName -ResourceGroupName $myGroupName
New-AzVirtualNetworkGatewayConnection -Name $myConnectionName `
-ResourceGroupName $myGroupName -Location $myGWLocation -VirtualNetworkGateway1 $gw `
-PeerId $PeerID -ConnectionType ExpressRoute -AuthorizationKey $AuthGUID -ExpressRouteGatewayBypass