Skip to content

Commit 3abc141

Browse files
committed
add support for billing types change
1 parent b772674 commit 3abc141

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/expressroute/expressroute-circuit-peerings.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,10 +43,12 @@ Default quotas and limits apply for every ExpressRoute circuit. Refer to the [Az
4343
* Upgrade from Local to Standard or Premium SKU.
4444
* Can only be done using Azure CLI or Azure PowerShell.
4545
* Billing type must be **unlimited**.
46+
* Changing from *MeteredData* to *UnlimitedData*.
4647

4748
#### Unsupported workflow
4849

4950
* Downgrade from Premium to Standard SKU.
51+
* Changing from *UnlimitedData* to *MeteredData*.
5052

5153
## <a name="routingdomains"></a>ExpressRoute peering
5254

@@ -82,7 +84,7 @@ Each peering requires separate BGP sessions (one pair for each peering type). Th
8284

8385
ExpressRoute circuits can be monitored for availability, connectivity to VNets and bandwidth utilization using [ExpressRoute Network Insights](expressroute-network-insights.md).
8486

85-
Connection Monitor for Expressroute monitors the health of Azure private peering and Microsoft peering. For more information on configuration, see [Configure Connection Monitor for ExpressRoute](how-to-configure-connection-monitor).
87+
Connection Monitor for Expressroute monitors the health of Azure private peering and Microsoft peering. For more information on configuration, see [Configure Connection Monitor for ExpressRoute](how-to-configure-connection-monitor.md).
8688

8789
## Next steps
8890

0 commit comments

Comments
 (0)