Merge pull request #283623 from duongau/erguided

ExpressRoute - Guided create experience GA (add High resiliency)

Author: denrea

articles/expressroute/expressroute-howto-circuit-portal-resource-manager.md

@@ -4,18 +4,15 @@ description: In this quickstart, you learn how to create, provision, verify, upd
 services: expressroute
 author: duongau
 ms.author: duau
-ms.date: 05/14/2024
+ms.date: 08/05/2024
 ms.topic: quickstart
 ms.service: azure-expressroute
 ms.custom: mode-ui
-zone_pivot_groups: expressroute-experience
 ---
 
-# Quickstart: Create and modify ExpressRoute Circuits
+# Quickstart: Create and modify ExpressRoute circuits
 
-This quickstart shows you how to create an ExpressRoute circuit using the Azure portal and the Azure Resource Manager deployment model. You can also check the status, update, delete, or deprovision a circuit.
-
-There are currently two create experience for ExpressRoute circuits in the portal. The new preview create experience is available through this [Preview link](https://aka.ms/expressrouteguidedportal). The current create experience is available through the [Azure portal](https://portal.azure.com). For guidance on how to create an ExpressRoute circuit with the preview create experience select the **Preview** tab at the top of the page. 
+This quickstart shows you how to create an ExpressRoute circuit in three different resiliency types: **Maximum Resiliency**, **High Resiliency**, and **Standard Resiliency**. You'll learn how to check the status, update, delete, or deprovision a circuit using the Azure portal.
 
 :::image type="content" source="media/expressroute-howto-circuit-portal-resource-manager/environment-diagram.png" alt-text="Diagram of ExpressRoute circuit deployment environment using Azure portal." lightbox="media/expressroute-howto-circuit-portal-resource-manager/environment-diagram.png":::
 
@@ -26,34 +23,36 @@ There are currently two create experience for ExpressRoute circuits in the porta
 
 ## <a name="create"></a>Create and provision an ExpressRoute circuit
 
-::: zone pivot="expressroute-preview"
-
 ### Sign in to the Azure portal
 
-Sign in to the Azure portal with this [Preview link](https://aka.ms/expressrouteguidedportal). This link is required to access the new preview create experience for an ExpressRoute circuit.
+From a browser, sign in to the [Azure portal](https://portal.azure.com) and sign in with your Azure account.
 
-### Create a new ExpressRoute circuit (Preview)
+### Create a new ExpressRoute circuit
 
 > [!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.
 
-1. On the Azure portal menu, select **+ Create a resource**. Search for **ExpressRoute (preview)** and then select **Create**.
+1. On the Azure portal menu, select **+ Create a resource**. Search for **ExpressRoute** and then select **Create**.
 
-    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/create-expressroute-circuit-new.png" alt-text="Screenshot of preview create experience of ExpressRoute circuit resource.":::
+    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/create-an-expressroute-circuit.png" alt-text="Screenshot of the create an ExpressRoute circuit resource.":::
 
-1. Select the **Subscription** and **Resource Group** for the circuit. Then select the type of **Resiliency** for your setup.
+1. Select the **Subscription** and **Resource group** for the circuit. Then select the type of **Resiliency** for your setup.
 
-    **Maximum Resiliency (Recommended)** - This option provides the highest level of resiliency for your ExpressRoute connectivity. It provides two ExpressRoute circuits with local redundancy in two different ExpressRoute locations.
+    **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.
 
     > [!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.
 
     :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of maximum resiliency for an ExpressRoute connection.":::
 
+    **High Resiliency** - Provides resiliency against location wide outages through a single ExpressRoute circuit across two locations in a metropolitan area.
+
+    :::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** - This option provides a single ExpressRoute circuit with local redundancy at a single ExpressRoute location.
 
     > [!NOTE]
-    > Standard Resiliency does not provide protection against location wide outages. This option is suitable for non-critical and non-production workloads.
+    > Standard Resiliency doesn't provide protection against location wide outages. This option is suitable for non-critical and non-production workloads.
     
     :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/standard-resiliency.png" alt-text="Diagram of standard resiliency for an ExpressRoute connection.":::
 
@@ -64,24 +63,25 @@ Sign in to the Azure portal with this [Preview link](https://aka.ms/expressroute
     **Maximum Resiliency**
 
     | Setting | Value |
-    | ---     | ---   |
-    | Use existing circuit or create new | You can augment resiliency of an existing standard circuit by selecting **Use existing circuit** and selecting an existing circuit for the first location. If you select **Use existing circuit**, you only need to configure the second circuit. If you select **Create new**, enter following information for both the new ExpressRoute circuit. |
-    | Region   | Select the region closest to the peering location of the circuit. |
-    | Name   | Enter a name for the ExpressRoute circuit. |
-    | Port type | Select if you're connecting to a service provider or directly into Microsoft's global network at a peering location. |
+    | --- | --- |
+    | Use existing circuit or create new | You can augment resiliency of an existing standard circuit by selecting **Use existing circuit** and selecting an existing circuit for the first location. If you select an existing circuit, you only need to configure the second circuit. If you select **Create new**, enter information for both ExpressRoute circuit. |
+    | Region | Select the region closest to the peering location of the circuit. |
+    | Circuit name | Enter the name for the ExpressRoute circuit. |
+    | Port type | Select whether you're connecting with a service provider or directly to Microsoft's global network at a peering location. |
     | Peering Location (Provider port type)  | Select the physical location where you're peering with Microsoft. |
     | Provider (Provider port type)| Select the internet service provider who you are requesting your service from. |
     | ExpressRoute Direct resource (Direct port type) | Select the ExpressRoute Direct resource that you want to use. |
+    | Enable Rate Limiting | Select this option to regulate the distribution of bandwidth across your ExpressRoute circuits. For more information, see [Rate limiting for ExpressRoute Direct circuits](rate-limit.md) |
     | Bandwidth | Select the bandwidth for the ExpressRoute circuit. |
-    | SKU | Select the SKU for the ExpressRoute circuit. You can specify **Local** to get the local SKU, **Standard** to get the standard SKU or **Premium** for the premium add-on. You can change between Local, Standard, and Premium. |
-    | Billing model | Select the billing type for egress data charge. You can specify **Metered** for a metered data plan and **Unlimited** for an unlimited data plan. You can change the billing type from **Metered** to **Unlimited**. |
+    | SKU | Select between **Local**, **Standard, and **Premium** SKU. The SKU determines the connectivity scope of your ExpressRoute circuit. For more information, see [What are the differences between circuit SKU?](expressroute-faqs.md#what-is-the-connectivity-scope-for-different-expressroute-circuit-skus). |
+    | Billing model | Select the billing model for the outbound data charge. You can select between **Metered** for a metered data plan and **Unlimited** for an unlimited data plan. For more information, see [ExpressRoute pricing](https://azure.microsoft.com/pricing/details/expressroute/) details. |
 
     > [!IMPORTANT]
-    > * The Peering Location indicates the [physical location](expressroute-locations.md) where you are peering with Microsoft. This is **not** linked to "Location" property, which refers to the geography where the Azure Network Resource Provider is located. While they're not related, it is a good practice to choose a Network Resource Provider geographically close to the Peering Location of the circuit.
-    > * You can't change the SKU from **Standard/Premium** to **Local** in Azure portal. To downgrade the SKU to **Local**, you can use [Azure PowerShell](expressroute-howto-circuit-arm.md) or [Azure CLI](howto-circuit-cli.md).
-    > * You can't change the type from **Unlimited** to **Metered**.
+    > * The peering location indicates the [physical location](expressroute-locations.md) where you're peering with Microsoft. This field **isn't** linked to **Region** property, which refers to the location of the Azure Network Resource Provider. While they're not related, it's good practice to select a Network Resource Provider closest to the peering location of the ExpressRoute circuit.
+    > * Changing from **Standard/Premium** to **Local** SKU is unavailable in the Azure portal. To downgrade to the **Local** SKU, you can use [Azure PowerShell](expressroute-howto-circuit-arm.md) or [Azure CLI](howto-circuit-cli.md).
+    > * You can't change from the **Unlimited** to **Metered** billing model.
 
-    Complete the same information for the second ExpressRoute circuit. When selecting an ExpressRoute location for the second circuit, you're provided with distances information from the first ExpressRoute location. This information can help you select the second ExpressRoute location.
+    Complete the same information for the second ExpressRoute circuit. When selecting an ExpressRoute location for the second circuit, you're provided with distances information from the first ExpressRoute location. This information can help you decide the second ExpressRoute location. 
 
     :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/peering-location-distance.png" alt-text="Screenshot of distance information from first ExpressRoute circuit.":::
 
@@ -95,56 +95,6 @@ Sign in to the Azure portal with this [Preview link](https://aka.ms/expressroute
 
 1. Select **Review + create** and then select **Create** to deploy the ExpressRoute circuit.
 
-::: zone-end
-
-::: zone pivot="expressroute-current"
-
-### Sign in to the Azure portal
-
-From a browser, sign in to the [Azure portal](https://portal.azure.com) and sign in with your Azure account.
-
-### Create a new ExpressRoute circuit
-
-> [!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.
-
-1. On the Azure portal menu, select **+ Create a resource**. Search for **ExpressRoute** and then select **Create**.
-
-    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/create-an-expressroute-circuit.png" alt-text=" Screenshot of ExpressRoute circuit resource.":::
-
-1. On the **Create ExpressRoute** page. Provide the **Resource Group**, **Region**, and  **Name** for the circuit. Then select **Next: Configuration >**.
-
-    | Setting | Value |
-    | ---     | ---   |
-    | Resource group | Select **Create new**. Enter **ExpressRouteResourceGroup** </br>  Select **OK**. |
-    | Region   |  West US 2 |
-    | Name   |  TestERCircuit |
-
-    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-create-basic.png" alt-text="Screenshot of how to configure the resource group and region.":::
-
-1. When you enter in the values on this page, make sure that you specify the correct SKU tier (Local, Standard, or Premium) and data metering billing model (Unlimited or Metered).
-
-    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-create-configuration.png" alt-text="Screenshot of how to configure the circuit.":::
-    
-    | Setting | Description |
-    | --- | --- |
-    | Port type | Select if you're connecting to a service provider or directly into Microsoft's global network at a peering location. |
-    | Create new or import from classic | Select if you're creating a new circuit or if you're migrating a classic circuit to Azure Resource Manager. |
-    | Provider | Select the internet service provider who you are requesting your service from. |
-    | Peering Location | Select the physical location where you're peering with Microsoft. |
-    | SKU | Select the SKU for the ExpressRoute circuit. You can specify **Local** to get the local SKU, **Standard** to get the standard SKU or **Premium** for the premium add-on. You can change between Local, Standard, and Premium. |
-    | Billing model | Select the billing type for egress data charge. You can specify **Metered** for a metered data plan and **Unlimited** for an unlimited data plan. You can change the billing type from **Metered** to **Unlimited**. |
-    | Allow classic operations | Enable this option to allow classic virtual networks to link to the circuit. |
-
-    > [!IMPORTANT]
-    > * The Peering Location indicates the [physical location](expressroute-locations.md) where you are peering with Microsoft. This is **not** linked to "Location" property, which refers to the geography where the Azure Network Resource Provider is located. While they're not related, it is a good practice to choose a Network Resource Provider geographically close to the Peering Location of the circuit.
-    > * You can't change the SKU from **Standard/Premium** to **Local** in Azure portal. To downgrade the SKU to **Local**, you can use [Azure PowerShell](expressroute-howto-circuit-arm.md) or [Azure CLI](howto-circuit-cli.md).
-    > * You can't change the type from **Unlimited** to **Metered**.
-
-1. Select **Review + create** and then select **Create** to deploy the ExpressRoute circuit.
-
-::: zone-end
-
 ### View the circuits and properties
 
 **View all the circuits**
@@ -159,7 +109,7 @@ All Expressroute circuits created in the subscription appear here.
 
 **View the properties**
 
-You can view the properties of the circuit by selecting it. On the Overview page for your circuit, you find the **Service Key**. Provide the service key to the service provider to complete the provisioning process. The service key is unique to your circuit.
+You can view the properties of the circuit by selecting it. On the Overview page for your circuit, you find the **Service Key**. Provide the service key to your service provider to complete the provisioning process. The service key is unique to your circuit.
 
 :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-overview.png" alt-text="Screenshot of ExpressRoute properties.":::
 
@@ -186,7 +136,7 @@ Circuit status: **Enabled**
 
 ### Periodically check the status and the state of the circuit key
 
-You can view the properties of the circuit that you're interested in by selecting it. Check the **Provider status** and ensure that it has moved to **Provisioned** before you continue.
+You can view the properties of a circuit that you're interested in by selecting it. Check the **Provider status** and ensure that it has moved to **Provisioned** before you continue.
 
 :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/provisioned.png" alt-text="Screenshot of circuit and provider status.":::
 
@@ -228,6 +178,7 @@ You can do the following tasks with no downtime:
   > Changing the metering plan from **Unlimited Data** to **Metered Data** is not supported.
 
 * You can enable and disable *Allow Classic Operations*.
+
   > [!IMPORTANT]
   > You may have to recreate the ExpressRoute circuit if there is inadequate capacity on the existing port. You cannot upgrade the circuit if there is no additional capacity available at that location.
   >
@@ -255,16 +206,14 @@ To modify an ExpressRoute circuit, select **Configuration**.
 
     :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-deprovision-after-deletion.png" alt-text="Screenshot of deprovisioning the ExpressRoute circuit.":::
 
-1. After your circuit service provider has confirmed that they've deprovisioned the circuit, confirm that the *Provider status* changes to **Not provisioned** in the Azure portal. Once the *Provider status* is **Not provisioned**, you'll be able to delete the circuit.
-
-    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-deprovisioned.png" alt-text="Screenshot of deprovisioned circuit.":::
+1. After your circuit service provider has confirmed that they've deprovisioned the circuit, confirm that the *Provider status* changes to **Not provisioned** in the Azure portal. Once the *Provider status* changes to **Not provisioned**, you can delete the circuit.
 
+    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-deprovisioned.png" alt-text="Screenshot of a deprovisioned circuit.":::
 
 > [!NOTE]
 >* You must delete all associated [Virtual Network connections](expressroute-howto-linkvnet-portal-resource-manager.md#clean-up-resources), [Authorizations](expressroute-howto-linkvnet-portal-resource-manager.md#circuit-owner-operations), and [Global Reach](expressroute-howto-set-global-reach-portal.md#disable-connectivity) from the ExpressRoute circuit before deprovisioning. If deprovisioning fails, check whether any associated resources are still linked to the circuit.
 >* If the circuit service provider has deprovisioned the circuit (The *Provider status* has updated to **Not provisioned**), you can delete the circuit. This stops billing for the circuit.
 
-
 ## Next steps
 
 After you create your circuit, continue with the following next step: