added photos for upgrade

Author: MekaylaMoore

articles/expressroute/expressroute-howto-add-gateway-portal-resource-manager.md

@@ -19,7 +19,7 @@ ms.custom:
 > * [Classic - PowerShell](expressroute-howto-add-gateway-classic.md)
 > 
 
-This article walks you through the steps to add and remove a virtual network gateway for a pre-existing virtual network (virtual network). The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
+This article walks you through the steps to add and remove a virtual network gateway for a preexisting virtual network (virtual network). The steps for this configuration apply to VNets that were created using the Resource Manager deployment model for an ExpressRoute configuration. For more information about virtual network gateways and gateway configuration settings for ExpressRoute, see [About virtual network gateways for ExpressRoute](expressroute-about-virtual-network-gateways.md).
 
 :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/gateway-circuit.png" alt-text="Diagram showing an ExpressRoute gateway connected to the ExpressRoute circuit." lightbox="./media/expressroute-howto-add-gateway-portal-resource-manager/gateway-circuit.png":::
 
@@ -55,7 +55,7 @@ The steps for this tutorial use the values in the following configuration refere
 
 1. Select **+ Gateway subnet** to add a gateway subnet. 
 
-1. The **Name** for your subnet is automatically filled in with the value 'GatewaySubnet'. This value is required in order for Azure to recognize the subnet as the gateway subnet. Adjust the autofilled **Address range** values to match your configuration requirements. **You need to create the GatewaySubnet with a /27 or larger** (/26, /25, and so on.). /28 or smaller subnets are not supported for new deployments. If you plan on connecting 16 ExpressRoute circuits to your gateway, you **must** create a gateway subnet of /26 or larger.
+1. The **Name** for your subnet is automatically filled in with the value 'GatewaySubnet'. This value is required in order for Azure to recognize the subnet as the gateway subnet. Adjust the autofilled **Address range** values to match your configuration requirements. **You need to create the GatewaySubnet with a /27 or larger** (/26, /25, and so on.). /28 or smaller subnets aren't supported for new deployments. If you plan on connecting 16 ExpressRoute circuits to your gateway, you **must** create a gateway subnet of /26 or larger.
 
     If you're using a dual stack virtual network and plan to use IPv6-based private peering over ExpressRoute, select **Add IPv6 address space** and enter **IPv6 address range** values.
 
@@ -115,6 +115,25 @@ You can enable or disable VNet to VNet or VNet to WAN connectivity through Expre
 
 These steps will need to be completed on all virtual networks that need to communicate with each other through ExpressRoute.
 
+## Upgrade the gateway SKU
+
+1. In the Azure portal, navigate to the ExpressRoute virtual network gateway.
+
+1. In the **Settings** section, select **Configuration**.
+
+1. In the **Configuration** section, select the **SKU** dropdown and choose your desired SKU.
+
+    You can upgrade:
+    * From one Non-Az-enabled SKU to another Non-Az-enabled SKU
+
+     :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/standard-sku-upgrade.png" alt-text="Screenshot that shows where to upgrade Gateway SKU for Non-Az Gateways.":::
+
+    * From one Az-enabled SKU to another Az-enabled SKU
+
+      :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/az-sku-upgrade.png" alt-text="Screenshot that shows where to upgrade Gateway SKU for Non-Az Gateways.":::
+
+    
+For all other downgrade scenarios, you need to delete and re-create the gateway, which incurs downtime.
 ## Clean up resources
 
 If you no longer need the ExpressRoute gateway, locate the gateway in the virtual network resource group and select **Delete**. Ensure the gateway doesn't have any connections to a circuit.

articles/expressroute/gateway-migration.md

@@ -30,6 +30,7 @@ By comparison, the **Standard**, **HighPerformance**, and **UltraPerformance** S
 The gateway migration experience allows you to deploy a second virtual network gateway in the same GatewaySubnet. Azure migrates your configurations from the old gateway to the new one. Both gateways run simultaneously during migration, minimizing disruption – though brief connectivity interruptions may still occur.
 
 After migration, the old gateway and its connections are deleted, and the new gateway is tagged with **CreatedBy: GatewaySKUMigration** to identify it as a migrated resource and shouldn’t be deleted.
+
 ## Supported Migration Scenarios
 
 The guided gateway migration experience supports the following scenarios:
@@ -46,7 +47,10 @@ For enhanced reliability and high availability, we recommend migrating to an Az-
 
 1. **Validate**: Check that all resources are in a succeeded state. If any prerequisites aren't met, validation fails and migration can't proceed.
 2. **Prepare**: Azure creates a new virtual network gateway, public IP, and connections. This step can take up to 45 minutes. You can specify a name for the new gateway, or Azure will add **_migrated** to the original name by default. During preparation, the existing gateway is locked to prevent changes. If you need to stop the migration, you can **abort** at this stage, which deletes the new gateway and connections.
-    - **Note**: The new gateway is created in the same region as the existing one. To change regions, you must delete the current gateway and create a new one in the desired region.
+
+> [!NOTE] 
+>The new gateway is created in the same region as the existing one. To change regions, you must delete the current gateway and create a new one in the desired region.
+
 3. **Migrate**: Switch traffic from the old gateway to the new one. This step can take up to 15 minutes and may cause brief connectivity interruptions.
 4. **Commit**: Complete the migration by deleting the old gateway and its connections. If necessary, you can abort and revert to the old gateway before committing.