@@ -88,6 +88,8 @@ Select the subscription for which you want to create an ExpressRoute circuit.
88
88
az account set --subscription "<subscription ID>"
89
89
```
90
90
91
+ ---
92
+
91
93
## Get a list of prefixes and BGP community values
92
94
93
95
# [ ** Portal** ] ( #tab/portal )
@@ -112,6 +114,8 @@ Find the BGP community values associated with services accessible through Micros
112
114
az network route-filter rule list-service-communities
113
115
```
114
116
117
+ ---
118
+
115
119
## Make a list of the values you want to use
116
120
117
121
List the [BGP community values](expressroute-routing.md#bgp) you want to use in the route filter.
@@ -176,6 +180,8 @@ A route filter can have only one rule, and the rule must be of type 'Allow'. Thi
176
180
az network route-filter rule create --filter-name MyRouteFilter -n CRM --communities 12076:5040 --access Allow -g MyResourceGroup
177
181
```
178
182
183
+ ---
184
+
179
185
## Attach the route filter to an ExpressRoute circuit
180
186
181
187
# [**Portal**](#tab/portal)
@@ -207,6 +213,8 @@ Run the following command to attach the route filter to the ExpressRoute circuit
207
213
az network express-route peering update --circuit-name MyCircuit -g ExpressRouteResourceGroupName --name MicrosoftPeering --route-filter MyRouteFilter
208
214
```
209
215
216
+ ---
217
+
210
218
## Common tasks
211
219
212
220
### To get the properties of a route filter
@@ -241,6 +249,8 @@ To get the properties of a route filter, use the following command:
241
249
az network route-filter show -g ExpressRouteResourceGroupName --name MyRouteFilter
242
250
```
243
251
252
+ ---
253
+
244
254
### To update the properties of a route filter
245
255
246
256
# [ ** Portal** ] ( #tab/portal )
@@ -269,6 +279,8 @@ If the route filter is already attached to a circuit, updates to the BGP communi
269
279
az network route-filter rule update --filter-name MyRouteFilter -n CRM -g ExpressRouteResourceGroupName --add communities '12076:5040' --add communities '12076:5010'
270
280
```
271
281
282
+ ---
283
+
272
284
### To detach a route filter from an ExpressRoute circuit
273
285
274
286
# [ ** Portal** ] ( #tab/portal )
@@ -294,6 +306,8 @@ Once a route filter is detached from the ExpressRoute circuit, no prefixes are a
294
306
az network express-route peering update --circuit-name MyCircuit -g ExpressRouteResourceGroupName --name MicrosoftPeering --remove routeFilter
295
307
```
296
308
309
+ ---
310
+
297
311
## Clean up resources
298
312
299
313
# [ ** Portal** ] ( #tab/portal )
@@ -318,6 +332,8 @@ You can only delete a route filter if it isn't attached to any circuit. Ensure t
318
332
az network route-filter delete -n MyRouteFilter -g MyResourceGroup
319
333
```
320
334
335
+ ---
336
+
321
337
## Next Steps
322
338
323
339
For information about router configuration samples, see:
0 commit comments