Document Details
Expressroute Howto Circuit Resource Manager 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
⚠️
windows_first
⚠️
missing_linux_example
Summary:
The documentation page demonstrates a strong Windows/Powershell bias. The primary example for deploying an ExpressRoute circuit using an ARM template is provided only in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. Instructions and workflow steps are written specifically for PowerShell users, and the guidance assumes use of the Azure Cloud Shell in PowerShell mode. While there is a brief mention of Azure CLI and REST API as alternative deployment methods, no concrete CLI or Bash examples are provided. This prioritization of PowerShell and lack of Linux-native or cross-platform command examples may hinder accessibility for Linux and macOS users.
Recommendations:
- Add equivalent Azure CLI (az) examples for all PowerShell scripts, especially for deploying and deleting ExpressRoute circuits.
- Include Bash shell instructions and examples where appropriate, or clarify that Azure Cloud Shell supports both Bash and PowerShell.
- Present CLI and PowerShell examples side-by-side or in tabs, ensuring neither platform is prioritized over the other.
- Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Review and update workflow steps to be platform-neutral, avoiding assumptions about the user's operating system or shell.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 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-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
* **SKU tier** determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*.
* **SKU family** determines the billing type. You can specify *Metereddata* for a metered data plan and *Unlimiteddata* for an unlimited data plan. You can change the billing type from *Metereddata* to *Unlimiteddata*, but you can't change the type from *Unlimiteddata* to *Metereddata*. A *Local* circuit is *Unlimiteddata* only.
* **Peering Location** is the physical location where you are peering with Microsoft.
> [!IMPORTANT]
> The Peering Location indicates the [physical location](expressroute-locations.md) where you are peering with Microsoft. This is **not** linked to "Location" property, which refers to the geography where the Azure Network Resource Provider is located. While they are not related, it is a good practice to choose a Network Resource Provider geographically close to the Peering Location of the circuit.
The resource group name is the service bus namespace name with **rg** appended.
2. Select **Copy** to copy the PowerShell script.
3. Right-click the shell console, and then select **Paste**.
It takes a few moments to create an event hub.
Azure PowerShell is used to deploy the template in this tutorial. For other template deployment methods, see:
* [By using the Azure portal](../azure-resource-manager/templates/deploy-portal.md).
* [By using Azure CLI](../azure-resource-manager/templates/deploy-cli.md).
* [By using REST API](../azure-resource-manager/templates/deploy-rest.md).
## <a name="delete"></a>Deprovisioning and deleting an ExpressRoute circuit
You can delete your ExpressRoute circuit by selecting the **delete** icon. Note the following information:
* You must unlink all virtual networks from the ExpressRoute circuit. If this operation fails, check whether any virtual networks are linked to the circuit.
* If the ExpressRoute circuit service provider provisioning state is **Provisioning** or **Provisioned** you must work with your service provider to deprovision the circuit on their side. We continue to reserve resources and bill you until the service provider completes deprovisioning the circuit and notifies us.
* If the service provider has deprovisioned the circuit (the service provider provisioning state is set to **Not provisioned**), you can delete the circuit. This stops billing for the circuit.
You can delete your ExpressRoute circuit by running the following PowerShell command: