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, referencing PowerShell-specific cmdlets and output, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots are tailored to PowerShell users, with no mention or guidance for Linux or macOS users who may prefer or require CLI/Bash. While the text briefly mentions that Azure CLI and REST API are also supported, no examples or step-by-step instructions are given for those methods.
Recommendations:
- Provide Azure CLI (az) command examples alongside PowerShell for all deployment and cleanup steps.
- Include Bash shell instructions or note that Azure CLI commands work cross-platform (Windows, Linux, macOS).
- Add screenshots or output examples from Azure CLI to ensure parity.
- Reorder or parallelize instructions so that CLI and PowerShell are presented equally, rather than PowerShell first or exclusively.
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and guide users to choose their preferred shell.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-13 21:37 | #48 | completed | ✅ Clean |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
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: