Skip to content

Commit a1d8484

Browse files
authored
Bandwidth Guidance
Add guidance to open a support request when bandwidth is unavailable in the target peering location.
1 parent 49bad09 commit a1d8484

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/expressroute/expressroute-howto-erdirect.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,9 @@ Once enrolled, verify that the **Microsoft.Network** resource provider is regist
102102
}
103103
]
104104
```
105+
> [!NOTE]
106+
> If bandwidth is unavailable in the target location, open a [support request in the Azure Portal](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) and select the ExpressRoute Direct Support Topic.
107+
>
105108
5. Create an ExpressRoute Direct resource based on the location chosen above
106109

107110
ExpressRoute Direct supports both QinQ and Dot1Q encapsulation. If QinQ is selected, each ExpressRoute circuit will be dynamically assigned an S-Tag and will be unique throughout the ExpressRoute Direct resource. Each C-Tag on the circuit must be unique on the circuit, but not across the ExpressRoute Direct.

0 commit comments

Comments
 (0)