Skip to content

Commit 60c8194

Browse files
authored
Merge pull request #205448 from halkazwini/er-filters-cli
ExpressRoute: Freshness: Tutorial: Configure route filters for Microsoft peering using the Azure CLI
2 parents 64bfa48 + 324b661 commit 60c8194

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/expressroute/how-to-routefilter-cli.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ author: duongau
66

77
ms.service: expressroute
88
ms.topic: tutorial
9-
ms.date: 10/08/2020
9+
ms.date: 08/20/2022
1010
ms.author: duau
11-
ms.custom: devx-track-azurecli
11+
ms.custom: devx-track-azurecli, template-tutorial
1212

1313
---
1414
# Tutorial: Configure route filters for Microsoft peering: Azure CLI
@@ -44,7 +44,7 @@ A route filter lets you identify services you want to consume through your Expre
4444
To attach route filters with Microsoft 365 services, you must have authorization to consume Microsoft 365 services through ExpressRoute. If you aren't authorized to consume Microsoft 365 services through ExpressRoute, the operation to attach route filters fails. For more information about the authorization process, see [Azure ExpressRoute for Microsoft 365](/microsoft-365/enterprise/azure-expressroute).
4545

4646
> [!IMPORTANT]
47-
> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit.
47+
> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all Microsoft Office service prefixes advertised through Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit.
4848
>
4949
5050
## Prerequisites
@@ -57,11 +57,11 @@ To successfully connect to services through Microsoft peering, you must complete
5757

5858
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
5959

60-
If you choose to install and use the CLI locally, this quickstart requires Azure CLI version 2.0.28 or later. To find the version, run `az --version`. If you need to install or upgrade, see [Install the Azure CLI]( /cli/azure/install-azure-cli).
60+
If you choose to install and use the CLI locally, this tutorial requires Azure CLI version 2.0.28 or later. To find the version, run `az --version`. If you need to install or upgrade, see [Install the Azure CLI]( /cli/azure/install-azure-cli).
6161

6262
### Sign in to your Azure account and select your subscription
6363

64-
To begin your configuration, sign in to your Azure account. If you're using the "Try It", you're signed in automatically and can skip the login step. Use the following examples to help you connect:
64+
To begin your configuration, sign in to your Azure account. If you're using the "Try It", you're signed in automatically and can skip the sign in step. Use the following examples to help you connect:
6565

6666
```azurecli
6767
az login

0 commit comments

Comments
 (0)