Document Details
Quickstart Create Expressroute Vnet Template
❌
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
⚠️
missing_linux_example
⚠️
windows_tools
⚠️
windows_first
Summary:
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots focus on PowerShell usage, which is more familiar to Windows users. While the Azure Cloud Shell is mentioned (which can run on any OS), the provided script is PowerShell-specific, and there is no mention of Bash or CLI alternatives. The 'Remove-AzResourceGroup' cmdlet is also used for cleanup, again with no CLI or Bash equivalent. Although the page briefly mentions that Azure CLI and REST API can be used, it does not provide any examples or guidance for those methods.
Recommendations:
- Add equivalent Azure CLI (az) examples for all deployment and cleanup steps, ideally in Bash syntax.
- Present both PowerShell and CLI examples side-by-side or allow the user to select their preferred shell.
- Ensure screenshots and instructions are not PowerShell-specific, or provide alternatives for Linux/macOS users.
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and show how to select the shell.
- Where possible, avoid using Windows-specific terminology or tools as the default or only option.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
Flagged Code Snippets
Wait until you see the prompt from the console.
1. Select **Copy** from the previous code block to copy the PowerShell script.
1. Right-click the shell console pane and then select **Paste**.
1. Enter the values.
The resource group name is the project name with **rg** appended.
It takes about 20 minutes to deploy the template. When completed, the output is similar to:
:::image type="content" source="./media/quickstart-create-expressroute-vnet/expressroute-powershell-output.png" alt-text="ExpressRoute Resource Manager template PowerShell deployment output":::
Azure PowerShell is used to deploy the template. In addition to Azure PowerShell, you can also use the Azure portal, Azure CLI, and REST API. To learn other deployment methods, see [Deploy templates](../azure-resource-manager/templates/deploy-portal.md).
## Validate the deployment
1. Sign in to the [Azure portal](https://portal.azure.com).
1. Select **Resource groups** from the left pane.
1. Select the resource group that you created in the previous section. The default resource group name is the project name with **rg** appended.
1. The resource group should contain the following resources seen here:
:::image type="content" source="./media/quickstart-create-expressroute-vnet/expressroute-resource-group.png" alt-text="ExpressRoute deployment resource group":::
1. Select the ExpressRoute circuit **er-ck01** to verify that the circuit status is **Enabled**, provider status is **Not provisioned** and private peering has the status of **Provisioned**.
:::image type="content" source="./media/quickstart-create-expressroute-vnet/expressroute-circuit.png" alt-text="ExpressRoute deployment circuit":::
> [!NOTE]
> You will need to call the provider to complete the provisioning process before you can link the virtual network to the circuit.
## Clean up resources
When you no longer need the resources that you created with the ExpressRoute circuit, delete the resource group to remove the ExpressRoute circuit and all the related resources.
To delete the resource group, call the `Remove-AzResourceGroup` cmdlet: