Merge pull request #294462 from AbdullahBell/expressroute-image-deletion

Networking: ExpressRoute: Reducing screenshot usage: 21 articles

Author: v-shils

articles/expressroute/evaluate-circuit-resiliency.md

@@ -45,8 +45,6 @@ To manually failover an ExpressRoute circuit that is configured with maximum res
 
 1. Navigate to the **Overview** page and select the private peering that is to be disabled.
 
-    :::image type="content" source="./media/evaluate-circuit-resiliency/primary-circuit.png" alt-text="Screenshot of the peering section of an ExpressRoute circuit on the overview page.":::
-
 1.  Deselect the checkbox next to **Enable IPv4 Peering** or **Enable IPv6 Peering** to disconnect the Border Gateway Protocol (BGP) peering and then select **Save**. When you disable the peering, Azure disconnects the private peering connection on the first circuit, and the secondary circuit assumes the role of the active connection."
 
     :::image type="content" source="./media/evaluate-circuit-resiliency/disable-private-peering-primary.png" alt-text="Screenshot of the private peering settings page for an ExpressRoute circuit.":::

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

@@ -54,25 +54,19 @@ The steps for this tutorial use the values in the following configuration refere
 1. In the **Settings** section of your virtual network, select **Subnets** to expand the Subnet settings.
 
 1. Select **+ Gateway subnet** to add a gateway subnet. 
-   
-    :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/add-gateway-subnet.png" alt-text="Screenshot that shows the button to add the 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.
 
     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.
 
     Then, select **OK** to save the values and create the gateway subnet.
 
-    :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/add-subnet-gateway.png" alt-text="Screenshot of the create an ExpressRoute gateway page with ErGwScale SKU selected.":::
-
 ## Create the virtual network gateway
 
 1. In the portal, on the left side, select **Create a resource**, and type 'Virtual Network Gateway' in search. Locate **Virtual network gateway** in the search return and select the entry. On the **Virtual network gateway** page, select **Create**.
 
 1. On the **Create virtual network gateway** page, enter or select these settings:
 
-    :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/create-gateway.png" alt-text="Screenshot that shows the Add subnet page for adding  the gateway subnet.":::
-
     | Setting | Value |
     | --------| ----- |
     | **Project details** |  |
@@ -125,8 +119,6 @@ These steps will need to be completed on all virtual networks that need to commu
 
 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.
 
-:::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/delete-gateway.png" alt-text="Screenshot that shows how to delete the virtual network gateway.":::
-
 ## Next steps
 
 In this tutorial, you learned how to create a virtual network gateway. For more information about virtual network gateways, see: [ExpressRoute virtual network gateways](expressroute-about-virtual-network-gateways.md).

articles/expressroute/expressroute-howto-add-ipv6-portal.md

@@ -24,12 +24,8 @@ From a web browser, sign in to the [Azure portal](https://portal.azure.com).
 
 1. [Create an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md) or navigate to the existing circuit you want to change.
 
-    :::image type="content" source="./media/expressroute-howto-add-ipv6-portal/navigate-to-circuit.png" alt-text="Screenshot of ExpressRoute circuit list.":::
-
 1. Select the **Azure private** peering configuration.
 
-    :::image type="content" source="./media/expressroute-howto-add-ipv6-portal/navigate-to-peering.png" alt-text="Screenshot of ExpressRoute overview page.":::
-
 1. Add an IPv6 Private Peering to your existing IPv4 Private Peering configuration by selecting "Both" for **Subnets**, or only enable IPv6 Private Peering on your new circuit by selecting "IPv6". Provide a pair of /126 IPv6 subnets that you own for your primary link and secondary links. From each of these subnets, you assign the first usable IP address to your router as Microsoft uses the second usable IP for its router. **Save** your peering configuration once you defined all parameters.
 
     :::image type="content" source="./media/expressroute-howto-add-ipv6-portal/add-ipv6-peering.png" alt-text="Screenshot of adding Ipv6 on private peering page.":::
@@ -44,8 +40,6 @@ Follow these steps if you have an existing environment of Azure resources that y
 
 1. Navigate to the virtual network that your ExpressRoute circuit is connected to.
 
-    :::image type="content" source="./media/expressroute-howto-add-ipv6-portal/navigate-to-vnet.png" alt-text="Screenshot of virtual network list.":::
-
 1. Navigate to the **Address space** tab and add an IPv6 address space to your virtual network. **Save** your address space.
 
     :::image type="content" source="./media/expressroute-howto-add-ipv6-portal/add-ipv6-space.png" alt-text="Screenshot of add Ipv6 address space to virtual network.":::

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

@@ -34,8 +34,6 @@ From a browser, sign in to the [Azure portal](https://portal.azure.com) and sign
 
 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 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.
 
     **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.
@@ -105,8 +103,6 @@ You can view all the circuits that you created by searching for **ExpressRoute c
 
 All Expressroute circuits created in the subscription appear here.
 
-:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-list.png" alt-text="Screenshot of ExpressRoute circuit list.":::
-
 **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 your service provider to complete the provisioning process. The service key is unique to your circuit.
@@ -122,8 +118,6 @@ When you create a new ExpressRoute circuit, the circuit is in the following stat
 Provider status: **Not provisioned**<BR>
 Circuit status: **Enabled**
 
-:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-overview-provisioning-state.png" alt-text="Screenshot of provisioning process.":::
-
 The circuit changes to the following state when the connectivity provider is currently enabling it for you:
 
 Provider status: **Provisioning**<BR>
@@ -138,8 +132,6 @@ Circuit status: **Enabled**
 
 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.":::
-
 ### Create your routing configuration
 
 For step-by-step instructions, refer to the [ExpressRoute circuit routing configuration](expressroute-howto-routing-portal-resource-manager.md) article to create and modify circuit peerings.
@@ -197,8 +189,6 @@ To modify an ExpressRoute circuit, select **Configuration**.
 
 1. In the **Overview** page, select **Delete**. If there are any associated resources attached to the circuit, you're asked to view the resources. Select **Yes** to see the associations that need to be removed before starting the deprovisioning process. If there are no associated resources, you can proceed with step 4.
 
-    :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-circuit-deprovision.png" alt-text="Screenshot of deprovisioning circuit for ExpressRoute.":::
-
 1. In the **View Associated Resources of Circuit** pane, you can see the resources associated with the circuit. Ensure you delete the resources before proceeding with the deprovisioning of the circuit. 
 
     :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-deprovision-associated-resources.png" alt-text="Screenshot of deleting associated resources to ExpressRoute circuit.":::
@@ -209,8 +199,6 @@ To modify an ExpressRoute circuit, select **Configuration**.
 
 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), [Route Filter](how-to-routefilter-portal.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.

articles/expressroute/expressroute-howto-erdirect.md

@@ -200,8 +200,6 @@ Reference the recently created ExpressRoute Direct resource, input a customer na
 
 1. Select the **Upload/Download** button and then select **Download**. Select the `loa.pdf` file and select Download.
 
-    :::image type="content" source="./media/expressroute-howto-erdirect/download.png" alt-text="Screenshot of download button from Azure Cloud Shell.":::
-
 ## <a name="state"></a>Change Admin State of links
    
 This process should be used to conduct a Layer 1 test, ensuring that each cross-connection is properly patched into each router for primary and secondary.

articles/expressroute/expressroute-howto-gateway-migration-portal.md

@@ -39,8 +39,6 @@ Here are the steps to migrate to a new gateway in Azure portal.
 
 1. the left-hand menu under *Settings*, select **Gateway SKU Migration**.
 
-    :::image type="content" source="media/gateway-migration/gateway-sku-migration-location.png" alt-text="Screenshot of Gateway migration location."lightbox="media/gateway-migration/gateway-sku-migration-location.png":::
-
 1. Select **Validate** to check if the gateway is ready for migration. You'll first see a list of prerequisites that must be met before migration can begin. If these prerequisites aren't met, validation fails and you can't proceed. 
 
     :::image type="content" source="media/gateway-migration/validate-step.png" alt-text="Screenshot of the validate step for migrating a virtual network gateway."lightbox="media/gateway-migration/validate-step.png":::

articles/expressroute/expressroute-howto-ipsec-transport-private-windows.md

@@ -97,10 +97,8 @@ Ensure that you meet the following prerequisites:
 
 1. Create a new GPO linked to an OU by opening the Group Policy Management snap-in. Then locate the OU to which the GPO gets linked. In the example, the OU is named **IPSecOU**. 
 
-   [![9]][9]
 2. In the Group Policy Management snap-in, select the OU, and right-click. In the dropdown, select "**Create a GPO in this domain, and Link it here…**".
 
-   [![10]][10]
 3. Name the GPO an intuitive name so that you can easily locate it later. Select **OK** to create and link the GPO.
 
    [![11]][11]
@@ -169,7 +167,6 @@ Create a filter list that specifies encrypted HTTP traffic with destination port
    [![29]][29]
 7. On the **IP Protocol Type** page, select **TCP**. Then, select **Next**.
 
-   [![30]][30]
 8. On the **IP Protocol Port** page, select **From any port** and **To this port:**. Type **8080** in the text box. These settings specify only the HTTP traffic on destination port 8080 gets encrypted. Then, select **Next**.
 
    [![31]][31]
@@ -315,8 +312,6 @@ For more information about ExpressRoute, see the [ExpressRoute FAQ](expressroute
 [1]: ./media/expressroute-howto-ipsec-transport-private-windows/network-diagram.png "network Diagram IPsec transport mode through ExpressRoute"
 [4]: ./media/expressroute-howto-ipsec-transport-private-windows/ipsec-interesting-traffic.png "IPsec interesting traffic"
 [5]: ./media/expressroute-howto-ipsec-transport-private-windows/windows-ipsec.png "Windows IPsec policy"
-[9]: ./media/expressroute-howto-ipsec-transport-private-windows/ou.png "Organization Unit in the Group Policy"
-[10]: ./media/expressroute-howto-ipsec-transport-private-windows/create-gpo-ou.png "create a GPO associated with the OU"
 [11]: ./media/expressroute-howto-ipsec-transport-private-windows/gpo-name.png "assign a name to the GPO associated with the OU"
 [12]: ./media/expressroute-howto-ipsec-transport-private-windows/edit-gpo.png "edit the GPO"
 [15]: ./media/expressroute-howto-ipsec-transport-private-windows/manage-ip-filter-list-filter-actions.png "Manage IP Filter Lists and Filter Actions"
@@ -334,7 +329,6 @@ For more information about ExpressRoute, see the [ExpressRoute FAQ](expressroute
 [27]: ./media/expressroute-howto-ipsec-transport-private-windows/source-address.png "selection of the Source subnet"
 [28]: ./media/expressroute-howto-ipsec-transport-private-windows/source-network.png "Source Network"
 [29]: ./media/expressroute-howto-ipsec-transport-private-windows/destination-network.png "Destination Network"
-[30]: ./media/expressroute-howto-ipsec-transport-private-windows/protocol.png "Protocol"
 [31]: ./media/expressroute-howto-ipsec-transport-private-windows/source-port-and-destination-port.png "source port and destination port"
 [32]: ./media/expressroute-howto-ipsec-transport-private-windows/ip-filter-list.png "filter list"
 [33]: ./media/expressroute-howto-ipsec-transport-private-windows/ip-filter-for-http.png "IP filter list with HTTP traffic"