Skip to content

Commit 265ffcf

Browse files
Merge pull request #265907 from halkazwini/ip-drct
Internet Peering: Freshness: Direct peering walkthrough
2 parents 9750fcc + d3ebe92 commit 265ffcf

File tree

1 file changed

+21
-20
lines changed

1 file changed

+21
-20
lines changed
Lines changed: 21 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: Direct peering walkthrough
33
titleSuffix: Internet Peering
4-
description: Get started with Direct peering.
5-
services: internet-peering
4+
description: Get started with Direct peering. Learn about the steps that you need to follow to provision and manage a Direct peering.
5+
ms.author: halkazwini
66
author: halkazwini
77
ms.service: internet-peering
88
ms.topic: how-to
9-
ms.date: 02/24/2023
10-
ms.author: halkazwini
11-
ms.custom: template-how-to, engagement-fy23
9+
ms.date: 02/09/2024
10+
11+
#CustomerIntent: As an administrator, I want to learn about the requirements to create a Direct peering so I can provision and manage Direct peerings.
1212
---
1313

1414
# Direct peering walkthrough
@@ -19,39 +19,40 @@ In this article, you learn how to set up and manage a Direct peering.
1919

2020
:::image type="content" source="./media/walkthrough-direct-all/direct-peering.png" alt-text="Diagram showing Direct peering workflow and connection states." lightbox="./media/walkthrough-direct-all/direct-peering.png":::
2121

22-
The following steps must be followed to provision a Direct peering:
22+
To provision a Direct peering, complete the following steps:
2323

2424
1. Review Microsoft [peering policy](policy.md) to understand requirements for Direct peering.
2525
1. Follow the instructions in [Create or modify a Direct peering](howto-direct-powershell.md) to submit a peering request.
2626
1. After you submit a peering request, Microsoft will contact using your registered email address to provide LOA (Letter Of Authorization) or for other information.
27-
1. Once peering request is approved, connection state changes to *ProvisioningStarted*.
28-
1. You need to:
29-
1. complete wiring according to the LOA
30-
1. (optionally) perform link test using 169.254.0.0/16
27+
1. Once peering request is approved, connection state changes to ***ProvisioningStarted***. Then, you need to:
28+
1. complete wiring according to the LOA.
29+
1. (optionally) perform link test using 169.254.0.0/16.
3130
1. configure BGP session and then notify Microsoft.
3231
1. Microsoft provisions BGP session with DENY ALL policy and validate end-to-end.
33-
1. If successful, you receive a notification that peering connection state is *Active*.
34-
1. Traffic will then be allowed through the new peering.
32+
1. If successful, you receive a notification that peering connection state is ***Active***.
33+
1. Traffic is then allowed through the new peering.
3534

3635
> [!NOTE]
3736
> Connection states are different from standard BGP session states.
3837
39-
## Convert a legacy Direct peering to Azure resource
38+
## Convert a legacy Direct peering to an Azure resource
39+
40+
To convert a legacy Direct peering to an Azure resource, complete the following steps:
4041

41-
The following steps must be followed to convert a legacy Direct peering to Azure resource:
4242
1. Follow the instructions in [Convert a legacy Direct peering to Azure resource](howto-legacy-direct-portal.md)
43-
1. After you submit the conversion request, Microsoft will review the request and contact you if necessary.
44-
1. Once approved, you see your Direct peering with a connection state as *Active*.
43+
1. After you submit the conversion request, Microsoft reviews the request and contacts you if necessary.
44+
1. Once approved, you see your Direct peering with a connection state as ***Active***.
4545

4646
## Deprovision Direct peering
4747

4848
Contact [Microsoft peering](mailto:[email protected]) team to deprovision a Direct peering.
4949

50-
When a Direct peering is set for deprovision, you see the connection state as *PendingRemove*.
50+
When a Direct peering is set for deprovision, the connection state changes to ***PendingRemove***.
5151

5252
> [!NOTE]
53-
> If you run PowerShell cmdlet to delete the Direct peering when the ConnectionState is *ProvisioningStarted* or *ProvisioningCompleted*, the operation will fail.
53+
> If you run PowerShell cmdlet to delete the Direct peering when the ConnectionState is ***ProvisioningStarted*** or ***ProvisioningCompleted***, the operation will fail.
5454
55-
## Next steps
55+
## Related content
5656

57-
* Learn about the [Prerequisites to set up peering with Microsoft](prerequisites.md).
57+
- Learn about the [Prerequisites to set up peering with Microsoft](prerequisites.md).
58+
- Learn about the [Peering policy](policy.md).

0 commit comments

Comments
 (0)