edits

Author: ktoliver

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

@@ -1,58 +1,64 @@
 ---
-title: Direct peering walkthrough
-titleSuffix: Internet Peering
-description: Get started with Direct peering. Learn about the steps that you need to follow to provision and manage a Direct peering.
+title: Set up and monitor a direct peering
+titleSuffix: Internet peering
+description: Learn how to provision and manage a direct peering in Azure Peering Service.
 ms.author: halkazwini
 author: halkazwini
 ms.service: internet-peering
 ms.topic: how-to
 ms.date: 02/09/2024
 
-#CustomerIntent: As an administrator, I want to learn about the requirements to create a Direct peering so I can provision and manage Direct peerings.
+#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.
 ---
 
-# Direct peering walkthrough
+# Set up and monitor a direct peering
 
-In this article, you learn how to set up and manage a Direct peering.
+In this article, you learn how to set up and manage a direct peering in Azure Peering Service.
 
-## Create a Direct peering
+## Create a direct peering
 
-:::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":::
+:::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":::
 
-To provision a Direct peering, complete the following steps:
+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***. Then, 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 Microsoft.
-1. Microsoft provisions BGP session with DENY ALL policy and validate end-to-end.
-1. If successful, you receive a notification that peering connection state is ***Active***.
-1. Traffic is then allowed through the new peering.
+1. Review the Microsoft [peering policy](policy.md) to understand requirements for direct peering.
+1. Complete the steps in [Create or modify a direct peering](howto-direct-powershell.md) to submit a peering request.
+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.
+1. When your peering request is approved, the connection state changes to **ProvisioningStarted**.
+
+   Then, you complete these steps:
+
+    1. Complete wiring according to the LOA.
+    1. (Optionally) Complete a link test by using the IP address range 169.254.0.0/16.
+    1. Configure a Border Gateway Protocol (BGP) session.
+    1. Notify Microsoft.
+
+1. Microsoft provisions the BGP session with a DENY ALL policy and completes an end-to-end session validation.
+1. If the provisioning is successful, you're notified that the peering connection state is **Active**.
+
+Traffic is then allowed through the new peering.
 
 > [!NOTE]
 > Connection states are different from standard BGP session states.
 
-## Convert a legacy Direct peering to an Azure resource
+## Convert a legacy direct peering to an Azure resource
+
+To convert a legacy direct peering, complete the steps to [convert a legacy direct peering to an Azure resource](howto-legacy-direct-portal.md).
 
-To convert a legacy Direct peering to an Azure resource, complete the following steps:
+After you submit the conversion request, Microsoft reviews the request and contacts you if necessary.
 
-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 reviews the request and contacts you if necessary.
-1. Once approved, you see your Direct peering with a connection state as ***Active***.
+If the request is approved, your direct peering appears with a connection state of **Active**.
 
-## Deprovision Direct peering
+## Deprovision a direct peering
 
-Contact [Microsoft peering](mailto:[email protected]) team to deprovision a Direct peering.
+To deprovision a direct peering, contact the [Microsoft peering](mailto:[email protected]) team.
 
-When a Direct peering is set for deprovision, the connection state changes to ***PendingRemove***.
+When a direct peering is set to deprovision, the connection state changes to **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 a PowerShell cmdlet to delete a direct peering when the connection state is **ProvisioningStarted** or **ProvisioningCompleted**, the operation fails.
 
 ## Related content
 
-- Learn about the [Prerequisites to set up peering with Microsoft](prerequisites.md).
-- Learn about the [Peering policy](policy.md).
+- Learn about the [prerequisites to set up peering with Microsoft](prerequisites.md).
+- Learn about [peering policy](policy.md).

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

@@ -1,54 +1,56 @@
 ---
-title: Direct peering type conversion request walkthrough
+title: Request a direct peering type conversion
 titleSuffix: Internet peering
-description: Learn how to request a type conversion for a Direct Peering.
+description: Learn how to request a type conversion for a direct peering in Azure Peering Service.
 author: halkazwini
 ms.author: halkazwini 
 ms.service: internet-peering
 ms.topic: how-to
 ms.date: 10/23/2024
 ---
 
-# Direct peering type conversion request walkthrough
+# Create a direct peering type conversion request
 
-In this article, you learn how to use the Azure portal to request a type conversion on a direct peering.
+In this article, you learn how to use the Azure portal to request a type conversion for a direct peering in Azure Peering Service.
 
 ## Prerequisites
 
 A direct peering type conversion for a peering connection can only be requested if the following prerequisites apply:
--  The peering must have at least two connections.
--  The redundant connections must be of equal bandwidth 
--  All connections in the peering must be fully provisioned (with the property 'ConnectionState' = 'Active') that is, none of the connections must be undergoing provisioning, decommission, or an internal device migration.
--  The peering must be represented as an Azure resource with a valid subscription. To onboard your peering as a resource, see [Convert a legacy Direct peering to an Azure resource using the Azure portal](howto-legacy-direct-portal.md).
--  Bandwidth updates can't be requested to other connections in the peering during the conversion.
--  No adding or removing of connections can occur during the conversion.
--  Type conversions run during the business hours of the Pacific Time zone.
--  For Voice conversions, the connection session addresses are provided by Microsoft and enabled with BFD (Bidirectional Forwarding Detection). It's expected that the partners set up their configurations accordingly.
+
+- The peering must have at least two connections.
+- The redundant connections must be of equal bandwidth
+- All connections in the peering must be fully provisioned (with the property 'ConnectionState' = 'Active') that is, none of the connections must be undergoing provisioning, decommission, or an internal device migration.
+- The peering must be represented as an Azure resource with a valid subscription. To onboard your peering as a resource, see [Convert a legacy Direct peering to an Azure resource using the Azure portal](howto-legacy-direct-portal.md).
+- Bandwidth updates can't be requested to other connections in the peering during the conversion.
+- No adding or removing of connections can occur during the conversion.
+- Type conversions run during the business hours of the Pacific Time zone.
+- For Voice conversions, the connection session addresses are provided by Microsoft and enabled with BFD (Bidirectional Forwarding Detection). It's expected that the partners set up their configurations accordingly.
 
 ## Configure the new type on a Direct Peering
 
 ### Convert from PNI to Voice
+
 A peering with standard PNI or PNI enabled for Azure Peering Service can be converted to Voice PNI. This conversion must be made at the peering level, which means all the connections within the peering are converted.
 
-1. Go to the **Configuration** page of your peering.
+1. Go to the **Configuration** pane of your peering.
 
 1. Select the **AS8075 (with Voice)** option and then select **Save**.
 
-    :::image type="content" source="./media/walkthrough-direct-peering-type-conversions/conversion-selection.png" alt-text="Screenshot shows how to change Microsoft network in the Conversions page of the peering in the Azure portal." lightbox="./media/walkthrough-direct-peering-type-conversions/conversion-selection.png":::
+    :::image type="content" source="./media/walkthrough-direct-peering-type-conversions/conversion-selection.png" alt-text="Screenshot shows how to change Microsoft network in the Conversions pane of the peering in the Azure portal." lightbox="./media/walkthrough-direct-peering-type-conversions/conversion-selection.png":::
 
 ### Enable Peering Service on a connection
 
 A standard PNI within a peering can be enabled for Peering Service and can be requested per connection.
 
-You need to be a Peering Service partner to enable Peering Service on a connection. See the [partner requirements page](prerequisites.md) and make sure you sign the agreement with Microsoft. For questions, reach out to [Azure Peering group](mailto:[email protected]).
+You need to be a Peering Service partner to enable Peering Service on a connection. See the [partner requirements pane](prerequisites.md) and make sure you sign the agreement with Microsoft. For questions, reach out to [Azure Peering group](mailto:[email protected]).
 
-1. Go to the **Connection** page of your peering.
+1. Go to the **Connection** pane of your peering.
 
 1. Select the ellipsis (...) next to the connection that you want to edit and select **Edit connection**.
 
-    :::image type="content" source="./media/walkthrough-direct-peering-type-conversions/view-connection.png" alt-text="Screenshot shows how to select a connection to edit in the Connections page of a peering in the Azure portal." lightbox="./media/walkthrough-direct-peering-type-conversions/view-connection.png":::
+    :::image type="content" source="./media/walkthrough-direct-peering-type-conversions/view-connection.png" alt-text="Screenshot shows how to select a connection to edit in the Connections pane of a peering in the Azure portal." lightbox="./media/walkthrough-direct-peering-type-conversions/view-connection.png":::
 
-1. In the **Direct Peering Connection** page, select **Enabled** for **Use for Peering Service**, and then select **Save**.
+1. In the **Direct Peering Connection** pane, select **Enabled** for **Use for Peering Service**, and then select **Save**.
 
     :::image type="content" source="./media/walkthrough-direct-peering-type-conversions/edit-connection.png" alt-text="Screenshot shows how to edit a connection." lightbox="./media/walkthrough-direct-peering-type-conversions/edit-connection.png":::
 
@@ -59,21 +61,21 @@ Once the request is received, the **Connection State** on each of the connection
 Your request is reviewed and approved by someone from the internal team.
 
 Connections remain in the **TypeChangeRequested** state until they're approved. After approval, the connections converted one at a time to ensure that the redundant connections are always up and carrying traffic. The **Connection State** changes to **TypeChangeInProgress**.
-You can see this state in the Connection page.
+You can see this state in the Connection pane.
 
 ## Monitor the conversion
 
 When your connection enters the conversion process, its state is labeled as **TypeChangeInProgress**.
 
 You're kept up to date through emails at the following steps:
 
--  Request Received
--  Request Approved
--  Session Address Changes (if any)
--  Conversion complete
--  Peering Azure Resource removal (if any)
--  Request rejected
--  Action required from peering partner
+- Request Received
+- Request Approved
+- Session Address Changes (if any)
+- Conversion complete
+- Peering Azure Resource removal (if any)
+- Request rejected
+- Action required from peering partner
 
 The email notifications are sent to the peer email contact provided during the *Peer Asn* resource creation. You can either reply back to the emails or contact [Azure Peering group](mailto:[email protected]) if you have questions.
 
@@ -88,18 +90,19 @@ Once the conversion is completed its state returns to **Active**.
 **Q.** Will there be an interruption to my connection?
 
 **A.** We do our absolute best and take various steps to prevent any interruption to service. These steps include:
--  Guaranteeing that a redundant connection with equivalent bandwidth is up at the time of conversion.
--  Performing any conversions one connection at a time.
--  Only bringing down old connections if it's necessary (in the case of a type conversion while the IP address stays the same).
--  Only performing conversions at times where engineers are online and capable of helping remedy any unlikely issues.  
 
-**Q.** Why has my request to convert the type of direct peering been rejected?
+- Guaranteeing that a redundant connection with equivalent bandwidth is up at the time of conversion.
+- Performing any conversions one connection at a time.
+- Only bringing down old connections if it's necessary (in the case of a type conversion while the IP address stays the same).
+- Only performing conversions at times where engineers are online and capable of helping remedy any unlikely issues.  
+
+**Q.** Why was my request to convert the type of direct peering rejected?
 
 **A.** Verify if the peering satisfies all the requirements from the [Prerequisites](#prerequisites) section.
 
-**Q.** Why has my request to enable Peering Service on a connection been rejected? 
+**Q.** Why has my request to enable Peering Service on a connection been rejected?
 
-**A.** To enable Peering Service on a connection, see [partner requirements page](prerequisites.md) and make sure you have signed the agreement with Microsoft. For questions, reach out to the [Azure Peering group](mailto:[email protected]). Verify if the peering satisfies all the requirements from the [Prerequisites](#prerequisites) section.
+**A.** To enable Peering Service on a connection, see [partner requirements pane](prerequisites.md) and make sure you have signed the agreement with Microsoft. For questions, reach out to the [Azure Peering group](mailto:[email protected]). Verify if the peering satisfies all the requirements from the [Prerequisites](#prerequisites) section.
 
 **Q.** How long does it take for the conversion to complete?
 
@@ -109,7 +112,7 @@ Once the conversion is completed its state returns to **Active**.
 
 **A.** Conversion process involves several stages and not all stages have traffic impact. Draining the traffic, configuring new policies pertaining to the type of peering, and allowing the traffic back once BGP and BFD come up are done serially. Combined these steps usually take ~2 hrs given the peering partner complete their end of the configurations. For Voice conversions, ensure that the BFD setup is done on time to ensure minimal downtime. For conversions that involve a change in IP addresses, there's almost zero downtime, since the traffic is seamlessly shifted to the session with the new addresses from the old session after which the old session is shut down.
 
-**Q.** How do I know which connection to configure the new Microsoft provided IP addresses?
+**Q.** How do I know which connection to configure the new Microsoft-provided IP addresses?
 
 **A.** The email notification lists the connection details with both the old peer provided IP addresses and the corresponding new Microsoft provided IP addresses.
 
@@ -121,6 +124,6 @@ Once the conversion is completed its state returns to **Active**.
 
 **A.** Once Peering A is converted from PNIs to Voice, the connections from Peering A are moved to Peering B, and Peering A is deleted. For example: If Peering A with two PNI connections are converted to Voice, and Peering B already has two connections, the process results in Peering B (the Voice peering) having four connections now and the Peering A resource will be removed. This is by design so that we maintain only one peering for a given peering provider and type of direct peering at a given location.
 
-**Q.** I have more questions, what is the best way to contact you?
+**Q.** I have more questions. What is the best way to contact you?
 
-**A.** Contact the [Azure Peering group](mailto:[email protected]).
+**A.** Contact the [Azure Peering Service group](mailto:[email protected]).