Merge pull request #262043 from duongau/erfreshness2

ExpressRoute - Freshness review 2 - Dec 2023

Author: v-regandowner

articles/expressroute/expressroute-config-samples-nat.md

@@ -3,25 +3,24 @@ title: 'Azure ExpressRoute: Router configuration samples - NAT'
 description: This page provides router configuration samples for Cisco and Juniper routers.
 services: expressroute
 author: duongau
-
 ms.service: expressroute
 ms.topic: article
-ms.date: 01/07/2021
+ms.date: 12/28/2023
 ms.author: duau
-
 ---
+
 # Router configuration samples to set up and manage NAT
 
-This article provides NAT configuration samples for Cisco ASA and Juniper SRX series routers when working with ExpressRoute. These router configurations are intended to be samples for guidance only and must not be used as is. You'll need to work with your vendor to come up with appropriate configurations for your network.
+This article provides NAT configuration samples for Cisco ASA and Juniper SRX series routers when working with ExpressRoute. These router configurations are intended to be samples for guidance only and must not be used as is. You need to work with your vendor to come up with appropriate configurations for your network.
 
 > [!IMPORTANT]
 > Samples in this page are intended to be purely for guidance. You must work with your vendor's sales / technical team and your networking team to come up with appropriate configurations to meet your needs. Microsoft will not support issues related to configurations listed in this page. You must contact your device vendor for support issues.
 > 
 > 
 
-* Router configuration samples below apply to Azure Public and Microsoft peerings. You don't configure NAT for Azure private peering. Review [ExpressRoute peerings](expressroute-circuit-peerings.md) and [ExpressRoute NAT requirements](expressroute-nat.md) for more details.
+* The following router configuration samples apply to Azure Public and Microsoft peerings. You don't configure NAT for Azure private peering. Review [ExpressRoute peerings](expressroute-circuit-peerings.md) and [ExpressRoute NAT requirements](expressroute-nat.md) for more details.
 
-* You MUST use separate NAT IP pools for connectivity to the internet and ExpressRoute. Using the same NAT IP pool across the internet and ExpressRoute will result in asymmetric routing and loss of connectivity.
+* You MUST use separate NAT IP pools for connectivity to the internet and ExpressRoute. Using the same NAT IP pool across the internet and ExpressRoute results in asymmetric routing and loss of connectivity.
 
 
 ## Cisco ASA firewalls
@@ -196,7 +195,7 @@ nat (inside,outside) source dynamic MSFT-PAT-Networks pat-pool outbound-PAT dest
 ```
 
 ### 4. Configure NAT policies
-* Create two NAT pools. One will be used to NAT traffic outbound to Microsoft and other from Microsoft to the customer.
+* Create two NAT pools. One is used to NAT traffic outbound to Microsoft and other from Microsoft to the customer.
 * Create rules to NAT the respective traffic
 
 ```console

articles/expressroute/expressroute-howto-reset-peering.md

@@ -2,22 +2,20 @@
 title: 'Azure ExpressRoute: Reset circuit peering using Azure PowerShell'
 description: Learn how to enable and disable peerings for an Azure ExpressRoute circuit using Azure PowerShell.
 services: expressroute
-author:  charwen
-
+author:  duongau
 ms.service: expressroute
-ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 12/15/2020
+ms.date: 12/28/2023
 ms.author: duau
 ---
 
 # Reset ExpressRoute circuit peerings using Azure PowerShell
 
-This article describes how to enable and disable peerings of an ExpressRoute circuit using PowerShell. Peerings are enabled by default when you create them. When you disable a peering, the BGP session on both the primary and the secondary connection of your ExpressRoute circuit will be shut down. You'll lose connectivity for this peering to Microsoft. When you enable a peering, the BGP session on both the primary and the secondary connection of your ExpressRoute circuit will be established. The connectivity to Microsoft will be restored for this peering. You can enable and disable peering for Microsoft Peering and Azure Private Peering independently on the ExpressRoute circuit.
+This article describes how to enable and disable peerings of an ExpressRoute circuit using PowerShell. Peerings are enabled by default when you create them. When you disable a peering, the BGP session on both the primary and the secondary connection of your ExpressRoute circuit disconnects. You lose connectivity for this peering to Microsoft. When you enable a peering, the BGP session on both the primary and the secondary connection of your ExpressRoute circuit establishes. The connectivity to Microsoft reconnects for this peering. You can enable and disable peering for Microsoft Peering and Azure Private Peering independently on the ExpressRoute circuit.
 
-There are a two scenarios where you may find it helpful to reset your ExpressRoute peerings.
+There are a two scenarios where you can find it helpful to reset your ExpressRoute peerings.
 * If you want to test your disaster recovery design and implementation. For example, you have two ExpressRoute circuits. You can disable the peerings on one circuit and force your network traffic to fail over to the other circuit.
-* Enable Bidirectional Forwarding Detection (BFD) on either Azure Private Peering or Microsoft Peering of your ExpressRoute circuit. BFD gets enabled by default on Azure Private Peering if you created your ExpressRoute circuit after August 1, 2018 and for Microsoft Peering after January 10, 2020. If your circuit was created before the date listed, you'll need reset the peering to enable BFD. 
+* Enable Bidirectional Forwarding Detection (BFD) on either Azure Private Peering or Microsoft Peering of your ExpressRoute circuit. BFD gets enabled by default on Azure Private Peering if you created your ExpressRoute circuit after August 1, 2018 and for Microsoft Peering after January 10, 2020. If your circuit was created before the date listed, you need reset the peering to enable BFD. 
 
 ### Working with Azure PowerShell
 
@@ -144,7 +142,7 @@ There are a two scenarios where you may find it helpful to reset your ExpressRou
    $ckt.Peerings[0].State = "Enabled"
    Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
    ```
-   The peering should be in a enabled state you set.
+   The peering should be in an enabled state you set.
 
 ## Next steps
 If you need help with troubleshooting an ExpressRoute problem, see the following articles: