Skip to content

Commit f9319c1

Browse files
authored
Merge pull request #116062 from derekolo/peering-update
Peering update
2 parents 70542ea + b42c1ce commit f9319c1

File tree

7 files changed

+62
-31
lines changed

7 files changed

+62
-31
lines changed

articles/internet-peering/howto-exchange-portal.md

Lines changed: 27 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: Create or modify an Exchange peering by using the Azure portal
33
titleSuffix: Azure
44
description: Create or modify an Exchange peering by using the Azure portal
55
services: internet-peering
6-
author: prmitiki
6+
author: derekolo
77
ms.service: internet-peering
88
ms.topic: article
9-
ms.date: 11/27/2019
10-
ms.author: prmitiki
9+
ms.date: 5/21/2020
10+
ms.author: derekol
1111
---
1212

1313
# Create or modify an Exchange peering by using the Azure portal
@@ -27,10 +27,31 @@ If you prefer, you can complete this guide by using [PowerShell](howto-exchange-
2727

2828
### <a name=create></a>Create an Exchange peering
2929

30-
You can create a new peering request by using the **Peering** resource.
3130

32-
#### Launch the resource and configure basic settings
33-
[!INCLUDE [direct-peering-basic](./includes/direct-portal-basic.md)]
31+
As an Internet Exchange Provider, you can create a direct peering request by [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
32+
33+
1. On the **Create a Peering** page, on the **Basics** tab, fill in the boxes as shown here:
34+
35+
> [!div class="mx-imgBorder"]
36+
> ![Register Peering Service](./media/setup-basics-tab.png)
37+
38+
* Select your Azure Subscription.
39+
40+
* For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.
41+
42+
* Name corresponds to the resource name and can be anything you choose.
43+
44+
* Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.
45+
46+
>[!NOTE]
47+
The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
48+
49+
* Select your ASN in the **PeerASN** box.
50+
51+
>[!IMPORTANT]
52+
You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
53+
54+
* Select **Next: Configuration** to continue.
3455

3556
#### Configure connections and submit
3657
[!INCLUDE [exchange-peering-configuration](./includes/exchange-portal-configuration.md)]

articles/internet-peering/howto-legacy-exchange-portal.md

Lines changed: 27 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: Convert a legacy Exchange peering to an Azure resource by using the Azure
33
titleSuffix: Azure
44
description: Convert a legacy Exchange peering to an Azure resource by using the Azure portal
55
services: internet-peering
6-
author: prmitiki
6+
author: derekolo
77
ms.service: internet-peering
88
ms.topic: article
9-
ms.date: 11/27/2019
10-
ms.author: prmitiki
9+
ms.date: 5/21/2020
10+
ms.author: derekol
1111
---
1212

1313
# Convert a legacy Exchange peering to an Azure resource by using the Azure portal
@@ -21,8 +21,30 @@ If you prefer, you can complete this guide by using [PowerShell](howto-legacy-ex
2121

2222
## Convert a legacy Exchange peering to an Azure resource
2323

24-
### Sign in to the portal and select your subscription
25-
[!INCLUDE [Account](./includes/account-portal.md)]
24+
As an Internet Exchange Provider, you can create a direct peering request by [Creating a Peering]( https://go.microsoft.com/fwlink/?linkid=2129593).
25+
26+
1. On the **Create a Peering** page, on the **Basics** tab, fill in the boxes as shown here:
27+
28+
> [!div class="mx-imgBorder"]
29+
> ![Register Peering Service](./media/setup-basics-tab.png)
30+
31+
* Select your Azure Subscription.
32+
33+
* For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.
34+
35+
* Name corresponds to the resource name and can be anything you choose.
36+
37+
* Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.
38+
39+
>[!NOTE]
40+
The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.
41+
42+
* Select your ASN in the **PeerASN** box.
43+
44+
>[!IMPORTANT]
45+
You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
46+
47+
* Select **Next: Configuration** to continue.
2648

2749
### <a name=create></a>Convert legacy Exchange peering
2850

articles/peering-service/azure-portal.md

Lines changed: 4 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -34,26 +34,9 @@ You must have a valid and active Microsoft Azure account. This account is requir
3434

3535
You can work with an internet service provider or internet exchange partner to obtain Peering Service to connect your network with the Microsoft network.
3636

37-
Make sure the connectivity providers are partnered with Microsoft.
37+
Make sure the [connectivity providers](location-partners.md) are partnered with Microsoft.
3838

39-
### Register your subscription with the resource provider and feature flag
4039

41-
Before you proceed to the steps of registering the Peering Service, you need to register your subscription with the resource provider and feature flag either via Azure PowerShell or the Azure CLI.
42-
43-
**Azure PowerShell**
44-
45-
```azurepowershell-interactive
46-
Register-AzProviderFeature -FeatureName AllowPeeringService -ProviderNamespace Microsoft.Peering
47-
48-
Register-AzResourceProvider -ProviderNamespace Microsoft.Peering
49-
50-
```
51-
52-
**Azure CLI**
53-
54-
```azurecli-interactive
55-
az feature register --namespace Microsoft.Peering --name AllowPeeringService
56-
```
5740

5841
## Sign in to the Azure portal
5942

@@ -89,6 +72,9 @@ From a browser, go to the Azure portal and sign in with your Azure account.
8972

9073
1. When you see the **Validation passed** message as shown, select **Create**.
9174

75+
> ![Register Peering Service configuration tab](./media/peering-service-portal/peering-service-prefix.png)
76+
77+
9278
1. After you register a Peering Service connection, additional validation is performed on the included prefixes. You can review the validation status under the **Prefixes** section of the resource name. If the validation fails, one of the following error messages is displayed:
9379

9480
- Invalid Peering Service prefix, the prefix should be valid format, only Ipv4 prefix is supported.

articles/peering-service/create-connection.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,8 @@ This tutorial shows you how to create a Peering Service resource and how to conf
4343

4444
1. When you see the **Validation passed** message as shown, select **Create**.
4545

46+
> ![Register Peering Service configuration tab](./media/peering-service-portal/peering-service-prefix.png)
47+
4648
1. After you register a Peering Service connection, additional validation is performed on the included prefixes. You can review the validation status under the **Prefixes** section of the resource name. If the validation fails, one of the following error messages is displayed:
4749

4850
- Invalid Peering Service prefix, the prefix should be valid format, only Ipv4 prefix is supported.

articles/peering-service/location-partners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This article provides information on the connectivity providers that are partner
2121

2222
## Peering Service partners list
2323

24-
The table in this article provides information on the Peering Service connectivity partners (Preview) and their associated markets.
24+
The table in this article provides information on the Peering Service connectivity partners and their associated markets.
2525

2626
| **Partners** | **Market**|
2727
|-----------|---------|
-249 KB
Loading

articles/peering-service/onboarding-model.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To onboard Peering Service connection, do the following:
3636

3737
Work with Internet Service provider (ISP) or Internet Exchange (IX) Partner to obtain Peering Service to connect your network with the Microsoft network.
3838

39-
Ensure the connectivity providers are partnered with Microsoft for Peering Service.
39+
Ensure the [connectivity providers](location-partners.md) are partnered with Microsoft for Peering Service.
4040

4141
## Onboarding Peering Service connection telemetry
4242

0 commit comments

Comments
 (0)