Merge pull request #286915 from halkazwini/er-qs-ps2

ER PowerShell quickstart update 2

Author: prmerger-automator[bot]

articles/expressroute/expressroute-howto-circuit-arm.md

@@ -4,15 +4,15 @@ description: This quickstart shows you how to create, provision, verify, update,
 services: expressroute
 author: duongau
 ms.author: duau
-ms.date: 12/28/2023
+ms.date: 09/25/2024
 ms.topic: quickstart
 ms.service: azure-expressroute
 ms.custom: devx-track-azurepowershell, mode-api
 ---
 
 # Quickstart: Create and modify an ExpressRoute circuit using Azure PowerShell
 
-This quickstart shows you how to create an ExpressRoute circuit using PowerShell cmdlets and the Azure Resource Manager deployment model. You can also check the status, update, delete, or deprovision a circuit.
+This quickstart shows you how to create an ExpressRoute circuit in three different resiliency types: **Maximum Resiliency**, **High Resiliency**, and **Standard Resiliency** using Azure PowerShell. You'll learn how to check the status, update, delete, or deprovision a circuit using PowerShell cmdlets.
 
 :::image type="content" source="media/expressroute-howto-circuit-portal-resource-manager/environment-diagram.png" alt-text="Diagram of ExpressRoute circuit deployment environment using Azure PowerShell." lightbox="media/expressroute-howto-circuit-portal-resource-manager/environment-diagram.png":::
 
@@ -48,19 +48,85 @@ Check to see if your connectivity provider is listed there. Make a note of the f
 
 You're now ready to create an ExpressRoute circuit.
 
+### Get the list of resilient locations
+
+If you're creating an ExpressRoute circuit with a resiliency type of  **Maximum Resiliency**, you need to know the list of resilient locations. Here are the steps to retrieve this information:
+
+#### Clone the script
+
+```azurepowershell-interactive
+# Clone the setup script from GitHub.
+git clone https://github.com/Azure-Samples/azure-docs-powershell-samples/ 
+# Change to the directory where the script is located.
+CD azure-docs-powershell-samples/expressroute/
+```
+
+#### Run resilient locations script
+
+Run the **Get-AzExpressRouteResilientLocations.ps1** script to get the list of resilient locations. The following example shows how to get the resilient locations for a specific subscription sorted by distance from Silicon Valley:
+
+```azurepowershell-interactive
+$SubscriptionId = Get-AzureSubscription -SubscriptionName "<SubscriptionName>"
+highAvailabilitySetup/Get-AzExpressRouteResilientLocations.ps1 -SubscriptionId $SubscriptionId -RelativeLocation "silicon valley"
+```
+If you don't specify the location, you get a list of all resilient locations.
+
 ### Create an ExpressRoute circuit
 
-If you don't already have a resource group, you must create one before you create your ExpressRoute circuit. You can do so by running the following command:
+If you don't already have a resource group, you must create one before you create your ExpressRoute circuit. You can do so by running the **New-AzResourceGroup** cmdlet:
 
 ```azurepowershell-interactive
-New-AzResourceGroup -Name "ExpressRouteResourceGroup" -Location "West US"
+$resourceGroupName = (New-AzResourceGroup -Name "ExpressRouteResourceGroup" -Location "West US").ResourceGroupName
 ```
 
-The following example shows how to create a 200-Mbps ExpressRoute circuit through Equinix in Silicon Valley. If you're using a different provider and different settings, replace that information when you make your request. Use the following example to request a new service key:
+If you already have a resource group, you can use **Get-AzResourceGroup** to get the resource group name into a variable:
+
+```azurepowershell-interactive
+$resourceGroupName = (Get-AzResourceGroup -Name "<ResourceGroupName>").ResourceGroupName
+```
+
+# [**Maximum Resiliency**](#tab/maximum)
+
+**Maximum Resiliency** (Recommended) provides the highest level of resiliency for your ExpressRoute connection. It provides two ExpressRoute circuits with local redundancy in two different ExpressRoute edge locations.
+
+The following example shows how to create two ExpressRoute circuits through Equinix with local redundancy in Silicon Valley and Washington DC. If you're using a different provider and different settings, replace that information when you make your request.
+
+> [!NOTE]
+> This example uses the **New-AzHighAvailabilityExpressRouteCircuits.ps1** script. You must clone the script from GitHub to create the circuits. For more information, see [Clone the script](#clone-the-script).
+
+```azurepowershell-interactive
+$SubscriptionId = Get-AzureSubscription -SubscriptionName "<SubscriptionName>"
+highAvailabilitySetup/New-AzHighAvailabilityExpressRouteCircuits.ps1 -SubscriptionId $SubscriptionId -ResourceGroupName $resourceGroupName -Location "westus" -Name1 $circuit1Name -Name2 $circuit2Name -SkuFamily1 "MeteredData" -SkuFamily2 "MeteredData" -SkuTier1 "Standard" -SkuTier2 "Standard" -ServiceProviderName1 "Equinix" -ServiceProviderName2 "Equinix" -PeeringLocation1 "Silicon Valley" -PeeringLocation2 "Washington DC" -BandwidthInMbps 1000
+```
+
+:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of maximum resiliency for an ExpressRoute connection.":::
+
+> [!NOTE]
+> Maximum Resiliency provides maximum protection against location wide outages and connectivity failures in an ExpressRoute location. This option is strongly recommended for all critical and production workloads.
+
+# [**High Resiliency**](#tab/high)
+
+**High Resiliency** provides resiliency against location wide outages through a single ExpressRoute circuit across two locations in a metropolitan area.
+
+The following example shows how to create an ExpressRoute circuit through Equinix in Amsterdam Metro. If you're using a different provider and different settings, replace that information when you make your request. Use the following example to request a new service key.
+
+```azurepowershell-interactive
+New-AzExpressRouteCircuit -Name "ExpressRouteARMCircuit" -ResourceGroupName "ExpressRouteResourceGroup" -Location "West EU" -SkuTier Standard -SkuFamily MeteredData -ServiceProviderName "Equinix" -PeeringLocation "Amsterdam Metro" -BandwidthInMbps 200
+```
+:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/high-resiliency.png" alt-text="Diagram of high resiliency for an ExpressRoute connection.":::
+
+# [**Standard Resiliency**](#tab/standard)
+
+**Standard Resiliency** provides a single ExpressRoute circuit with local redundancy at a single ExpressRoute location.
+
+The following example shows how to create an ExpressRoute circuit through Equinix in Silicon Valley. If you're using a different provider and different settings, replace that information when you make your request. Use the following example to request a new service key.
 
 ```azurepowershell-interactive
 New-AzExpressRouteCircuit -Name "ExpressRouteARMCircuit" -ResourceGroupName "ExpressRouteResourceGroup" -Location "West US" -SkuTier Standard -SkuFamily MeteredData -ServiceProviderName "Equinix" -PeeringLocation "Silicon Valley" -BandwidthInMbps 200
 ```
+:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/standard-resiliency.png" alt-text="Diagram of standard resiliency for an ExpressRoute connection.":::
+
+---
 
 Make sure that you specify the correct SKU tier and SKU family:
 
@@ -69,7 +135,6 @@ Make sure that you specify the correct SKU tier and SKU family:
 
 > [!IMPORTANT]
 > Your ExpressRoute circuit is billed from the moment a service key is issued. Ensure that you perform this operation when the connectivity provider is ready to provision the circuit.
->
 
 The response contains the service key. You can get detailed descriptions of all the parameters by running the following command: