Skip to content

Commit 50baefc

Browse files
authored
Merge pull request #289993 from ktoliver/330777
[AQ] edit pass: Azure Peering Service how-to articles (task 330777)
2 parents 84defd2 + c6b596b commit 50baefc

8 files changed

+558
-510
lines changed

articles/internet-peering/walkthrough-communications-services-partner.md

Lines changed: 135 additions & 123 deletions
Large diffs are not rendered by default.

articles/internet-peering/walkthrough-device-maintenance-notification.md

Lines changed: 65 additions & 68 deletions
Large diffs are not rendered by default.
Lines changed: 36 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,64 @@
11
---
2-
title: Direct peering walkthrough
3-
titleSuffix: 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.
2+
title: Set up and monitor a direct peering
3+
titleSuffix: Internet peering
4+
description: Learn how to provision and manage a direct peering in Azure Peering Service.
55
ms.author: halkazwini
66
author: halkazwini
77
ms.service: internet-peering
88
ms.topic: how-to
99
ms.date: 02/09/2024
1010

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.
11+
#CustomerIntent: As an administrator, I want to learn about the requirements to create a direct peering in Azure Peering Service, so I can provision and manage direct peerings.
1212
---
1313

14-
# Direct peering walkthrough
14+
# Set up and monitor a direct peering
1515

16-
In this article, you learn how to set up and manage a Direct peering.
16+
In this article, you learn how to set up and manage a direct peering in Azure Peering Service.
1717

18-
## Create a Direct peering
18+
## Create a direct peering
1919

20-
:::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":::
20+
:::image type="content" source="./media/walkthrough-direct-all/direct-peering.png" alt-text="Diagram showing the direct peering workflow and connection states." lightbox="./media/walkthrough-direct-all/direct-peering.png":::
2121

22-
To provision a Direct peering, complete the following steps:
22+
To provision a direct peering:
2323

24-
1. Review Microsoft [peering policy](policy.md) to understand requirements for Direct peering.
25-
1. Follow the instructions in [Create or modify a Direct peering](howto-direct-powershell.md) to submit a peering request.
26-
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***. Then, you need to:
28-
1. complete wiring according to the LOA.
29-
1. (optionally) perform link test using 169.254.0.0/16.
30-
1. configure BGP session and then notify Microsoft.
31-
1. Microsoft provisions BGP session with DENY ALL policy and validate end-to-end.
32-
1. If successful, you receive a notification that peering connection state is ***Active***.
33-
1. Traffic is then allowed through the new peering.
24+
1. Review the Microsoft [peering policy](policy.md) to understand requirements for direct peering.
25+
1. Complete the steps in [Create or modify a direct peering](howto-direct-powershell.md) to submit a peering request.
26+
1. After you submit a peering request, Microsoft contacts you by using your registered email address to provide a Letter of Authorization (LOA) or to provide other information.
27+
1. When your peering request is approved, the connection state changes to **ProvisioningStarted**.
28+
29+
Then, you complete these steps:
30+
31+
1. Complete wiring according to the LOA.
32+
1. (Optional) Complete a link test by using the IP address range 169.254.0.0/16.
33+
1. Configure a Border Gateway Protocol (BGP) session.
34+
1. Notify Microsoft.
35+
36+
1. Microsoft provisions the BGP session with a DENY ALL policy and completes an end-to-end session validation.
37+
1. If the provisioning is successful, you're notified that the peering connection state is **Active**.
38+
39+
Traffic is then allowed through the new peering.
3440

3541
> [!NOTE]
3642
> Connection states are different from standard BGP session states.
3743
38-
## Convert a legacy Direct peering to an Azure resource
44+
## Convert a legacy direct peering to an Azure resource
45+
46+
To convert a legacy direct peering, complete the steps to [convert a legacy direct peering to an Azure resource](howto-legacy-direct-portal.md).
3947

40-
To convert a legacy Direct peering to an Azure resource, complete the following steps:
48+
After you submit the conversion request, Microsoft reviews the request and contacts you if necessary.
4149

42-
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 reviews the request and contacts you if necessary.
44-
1. Once approved, you see your Direct peering with a connection state as ***Active***.
50+
If the request is approved, your direct peering appears with a connection state of **Active**.
4551

46-
## Deprovision Direct peering
52+
## Deprovision a direct peering
4753

48-
Contact [Microsoft peering](mailto:[email protected]) team to deprovision a Direct peering.
54+
To deprovision a direct peering, contact the [Microsoft peering](mailto:[email protected]) team.
4955

50-
When a Direct peering is set for deprovision, the connection state changes to ***PendingRemove***.
56+
When a direct peering is set to deprovision, the connection state changes to **PendingRemove**.
5157

5258
> [!NOTE]
53-
> If you run PowerShell cmdlet to delete the Direct peering when the ConnectionState is ***ProvisioningStarted*** or ***ProvisioningCompleted***, the operation will fail.
59+
> If you run a PowerShell cmdlet to delete a direct peering when the connection state is **ProvisioningStarted** or **ProvisioningCompleted**, the operation fails.
5460
5561
## Related content
5662

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

0 commit comments

Comments
 (0)