You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sign in to the [Azure portal](https://portal.azure.com).
30
27
31
-
### <aname=create></a>Convert a legacy Direct peering
28
+
##Convert a legacy Direct peering
32
29
33
-
As an Internet Service Provider, you can convert legacy direct peering connections by using [Creating a Peering](https://go.microsoft.com/fwlink/?linkid=2129593).
30
+
As an Internet Service Provider, you can convert a legacy direct peering connection to an Azure resource using the Azure portal:
34
31
35
-
1.On the **Create a Peering** page, on the **Basics** tab, fill in the boxes as shown here:
32
+
1.In the search box at the top of the portal, enter ***peering***. Select **Peerings** from the search results.
1. On the **Basics** tab of **Create a Peering** page, enter, or select the following values:
41
37
42
-
* 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.
38
+
| Setting | Value |
39
+
| --- | --- |
40
+
|**Project Details**||
41
+
| Subscription | Select your Azure subscription. |
42
+
| Resource Group | Select a resource group or create a new one. |
43
+
|**Instance details**||
44
+
| Name | Enter a name for the peering you're creating. |
45
+
| Peer ASN | Select your ASN. |
43
46
44
-
* Name corresponds to the resource name and can be anything you choose.
47
+
:::image type="content" source="./media/howto-legacy-direct-portal/peering-basics.png" alt-text="Screenshot that shows the Basics tab of creating a peering in the Azure portal." lightbox="./media/howto-legacy-direct-portal/peering-basics.png":::
45
48
46
-
* 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.
49
+
>[!IMPORTANT]
50
+
>You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your Peer ASN 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 Peer ASN by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
47
51
48
-
>[!NOTE]
49
-
>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.
52
+
1. Select **Next : Configuration >**.
50
53
51
-
* Select your ASN in the **Peer ASN**box.
54
+
1. On the **Configuration**tab, enter or select the following values:
52
55
53
-
>[!IMPORTANT]
54
-
>You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your Peer ASN 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 Peer ASN by using **[Associate Peer ASN to Azure subscription](https://go.microsoft.com/fwlink/?linkid=2129592)**.
56
+
| Setting | Value |
57
+
| --- | --- |
58
+
| Peering type | Select **Direct**. |
59
+
| Microsoft network | Select **AS8075**. |
60
+
| SKU | Select **Basic Free**. Don't select **Premium Free** as it's reserved for special applications. |
61
+
| Metro | Select the metro location where you want to convert a peering to an Azure resource. If you have peering connections with Microsoft in the selected location that aren't converted, you can see them listed in the **Peering connections**. |
55
62
56
-
#### Launch the resource and configure basic settings
:::image type="content" source="./media/howto-legacy-direct-portal/peering-configuration.png" alt-text="Screenshot that shows the Configuration tab of creating a peering in the Azure portal." lightbox="./media/howto-legacy-direct-portal/peering-configuration.png":::
> If you want to add additional peering connections with Microsoft in the selected **Metro** location, select **Create new**. For more information, see [Create or modify a Direct peering by using the portal](howto-direct-portal.md).
1. Review the settings, and then select **Create**.
71
+
72
+
## Verify Direct peering
73
+
74
+
1. Go to the **Peering** resource you created in the previous section.
75
+
76
+
1. Under **Settings**, select **Connections** to see a summary of peering connections between your ASN and Microsoft.
77
+
78
+
:::image type="content" source="./media/howto-legacy-direct-portal/peering-connections.png" alt-text="Screenshot that shows the peering connections in the Azure portal." lightbox="./media/howto-legacy-direct-portal/peering-connections.png":::
79
+
80
+
-**Connection State** corresponds to the state of the peering connection setup. The states displayed in this field follow the state diagram shown in the [Direct peering walkthrough](walkthrough-direct-all.md).
81
+
-**IPv4 Session State** and **IPv6 Session State** correspond to the IPv4 and IPv6 BGP session states, respectively.
64
82
65
83
## Related content
66
84
67
-
-[Create or modify a Direct peering by using the portal](howto-direct-portal.md).
0 commit comments