Merge pull request #228429 from halkazwini/ip-direct

Internet Peering: Freshness: Direct peering walkthrough

Author: Stacyrch140

articles/internet-peering/media/walkthrough-direct-all/direct-peering.png

@@ -1,52 +1,57 @@
 ---
 title: Direct peering walkthrough
-description: Direct peering walkthrough.
+titleSuffix: Internet Peering
+description: Get started with Direct peering.
 services: internet-peering
 author: halkazwini
 ms.service: internet-peering
 ms.topic: how-to
-ms.date: 12/15/2020
+ms.date: 02/23/2023
 ms.author: halkazwini
-ms.custom: template-how-to
+ms.custom: template-how-to, engagement-fy23
 ---
 
 # Direct peering walkthrough
 
-This section explains the steps you need to follow to set up and manage a Direct peering.
+In this article, you learn how to set up and manage a Direct peering.
 
 ## Create a Direct peering
-> [!div class="mx-imgBorder"]
-> ![Direct peering workflow and connection states](./media/direct-peering.png)
 
-The following steps must be followed in order to provision a Direct peering:
-1. Review Microsoft [peering policy](https://peering.azurewebsites.net/peering) to understand requirements for Direct peering.
+:::image type="content" source="./media/walkthrough-direct-all/direct-peering.png" alt-text="Diagram showing Direct peering workflow and connection states.":::
+
+The following steps must be followed to provision a Direct peering:
+
+1. Review Microsoft [peering policy](policy.md) to understand requirements for Direct peering.
 1. Follow the instructions in [Create or modify a Direct peering](howto-direct-powershell.md) to submit a peering request.
 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.
-1. Once peering request is approved, connection state changes to ProvisioningStarted.
+1. Once peering request is approved, connection state changes to *ProvisioningStarted*.
 1. You need to:
     1. complete wiring according to the LOA
     1. (optionally) perform link test using 169.254.0.0/16
-    1. configure BGP session and then notify us.
+    1. configure BGP session and then notify Microsoft.
 1. Microsoft provisions BGP session with DENY ALL policy and validate end-to-end.
-1. If successful, you will receive a notification that peering connection state is Active.
+1. If successful, you receive a notification that peering connection state is *Active*.
 1. Traffic will then be allowed through the new peering.
 
-Note that connection states are not to be confused with standard [BGP](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) session states.
+> [!NOTE]
+> Connection states aren't to be confused with standard BGP session states.
 
 ## Convert a legacy Direct peering to Azure resource
-The following steps must be followed in order to convert a legacy Direct peering to Azure resource:
-1. Follow the instructions in [Convert a legacy Direct peering to Azure resource](howto-legacy-direct-powershell.md)
-1. After you submit the conversion request, Microsoft will review the request and contact you if required.
-1. Once approved, you will see your Direct peering with a connection state as Active.
+
+The following steps must be followed to convert a legacy Direct peering to Azure resource:
+1. Follow the instructions in [Convert a legacy Direct peering to Azure resource](howto-legacy-direct-portal.md)
+1. After you submit the conversion request, Microsoft will review the request and contact you if necessary.
+1. Once approved, you see your Direct peering with a connection state as *Active*.
 
 ## Deprovision Direct peering
-Contact [Microsoft peering](mailto:[email protected]) team to deprovision Direct peering.
 
-When a Direct peering is set for deprovision, you will see the connection state as **PendingRemove**
+Contact [Microsoft peering](mailto:[email protected]) team to deprovision a Direct peering.
+
+When a Direct peering is set for deprovision, you see the connection state as *PendingRemove*.
 
 > [!NOTE]
-> If you run PowerShell cmdlet to delete the Direct peering when the ConnectionState is ProvisioningStarted or ProvisioningCompleted the operation will fail.
+> If you run PowerShell cmdlet to delete the Direct peering when the ConnectionState is *ProvisioningStarted* or *ProvisioningCompleted*, the operation will fail.
 
 ## Next steps
 
-* Learn about [Prerequisites to set up peering with Microsoft](prerequisites.md).
+* Learn about the [Prerequisites to set up peering with Microsoft](prerequisites.md).