Merge pull request #294849 from AbdullahBell/frontdoor-image-removal

Networking: FrontDoor: Reducing screenshot usage:

Author: JillGrant615

articles/frontdoor/blue-green-deployment.md

@@ -42,8 +42,6 @@ Azure Front Door is Microsoft's modern cloud Content Delivery Network (CDN) that
 
 1. Select **+ Add a route** to configure routing to your Web App origin.
 
-    :::image type="content" source="./media/blue-green-deployment/endpoint.png" alt-text="Screenshot of adding a new endpoint for a new Azure Front Door profile.":::
-
 1. Provide a name for the route and configure the route settings based on the needs of your application. For more information, see [Create a Front Door for your application](create-front-door-portal.md#create-a-front-door-for-your-application).
 
     :::image type="content" source="./media/blue-green-deployment/add-a-route.png" alt-text="Screenshot of the added route page for a new Azure Front Door profile.":::
@@ -65,8 +63,6 @@ Azure Front Door is Microsoft's modern cloud Content Delivery Network (CDN) that
 
 1. Select **+ Add** to add another origin to the origin group. Enter the following information for the new version of the application:
 
-    :::image type="content" source="./media/blue-green-deployment/add-new-origin.png" alt-text="Screenshot of adding the second origin in an origin group for a new Azure Front Door profile.":::
-
     | Settings | Values |
     |--|--|
     | Name | Enter `NewWebApp`. |
@@ -88,8 +84,6 @@ Azure Front Door is Microsoft's modern cloud Content Delivery Network (CDN) that
 
 1. Under **Load balancing settings**, enter the following information:
 
-     :::image type="content" source="./media/blue-green-deployment/configure-origin-group-settings.png" alt-text="Screenshot of configuring the origin group settings.":::
-
     | Settings | Values |
     |--|--|
     | Sample size | Enter `4`. |

articles/frontdoor/classic-retirement-faq.md

@@ -96,8 +96,6 @@ If you have a support plan and you need technical assistance, you can create a [
 * *Summary*, describe the problem you’re experiencing with the migration.
 * *Problem type*, select **Migrating Front Door Classic to Front Door Standard or Premium**
 
-:::image type="content" source="./media/classic-retirement-faq/support-request.png" alt-text="Screenshot of a new support request for Azure Front Door (classic) migration issue.":::
-
 ## Next steps
 
 - Migrate from Azure Front Door (classic) to Standard or Premium tier using the [Azure portal](migrate-tier.md) or [Azure PowerShell](migrate-tier-powershell.md) 

articles/frontdoor/create-front-door-portal.md

@@ -115,16 +115,10 @@ In this step, you configure Azure Front Door to route user traffic to the neares
 
 1. From the home page or the Azure menu, select **+ Create a resource**, search for *Front Door and CDN profiles*, and select **Create**.
 
-    :::image type="content" source="./media/create-front-door-portal/front-door-custom-create-secret.png" alt-text="Screenshot of add a secret in custom create.":::
-
 1. In the *Endpoint* tab, select **Add an endpoint**, enter a globally unique name (for example, contoso-frontend), and select **Add**. You can create more endpoints after the initial deployment.
 
-    :::image type="content" source="./media/create-front-door-portal/front-door-custom-create-add-endpoint.png" alt-text="Screenshot of add an endpoint.":::
-
 1. To configure routing to your Web App origin, select **+ Add a route**.
 
-    :::image type="content" source="./media/create-front-door-portal/add-route.png" alt-text="Screenshot of add a route from the endpoint page." lightbox="./media/create-front-door-portal/add-route-expanded.png":::
-
 1. On the **Add a route** page, enter or select the following information and then select **Add** to add the route to the endpoint configuration.
 
     :::image type="content" source="./media/create-front-door-portal/add-route-page.png" alt-text="Screenshot of add a route configuration page." lightbox="./media/create-front-door-portal/add-route-page-expanded.png":::
@@ -144,12 +138,8 @@ In this step, you configure Azure Front Door to route user traffic to the neares
 
 1. Select **+ Add a policy** to apply a Web Application Firewall (WAF) policy to one or more domains in the Azure Front Door profile.
 
-    :::image type="content" source="./media/create-front-door-portal/add-policy.png" alt-text="Screenshot of add a policy from endpoint page." lightbox="./media/create-front-door-portal/add-policy-expanded.png":::
-
 1. To create a security policy, provide a name that uniquely identifies it. Next, choose the domains that you want to apply the policy to. You can also select an existing WAF policy or create a new one. To finish, select **Save** to add the security policy to the endpoint configuration.
 
-    :::image type="content" source="./media/create-front-door-portal/add-security-policy.png" alt-text="Screenshot of add security policy page.":::
-
 1. To deploy the Azure Front Door profile, select **Review + Create** and then **Create**. The configuration propagates to all edge locations within a few minutes.
 
 ---

articles/frontdoor/front-door-how-to-onboard-apex-domain.md

@@ -57,12 +57,8 @@ You can use the Azure portal to onboard an apex domain on your Azure Front Door
 
 1. Select the **Pending** validation state. A new pane appears with the DNS TXT record information needed to validate the custom domain. The TXT record is in the form of `_dnsauth.<your_subdomain>`.
 
-   :::image type="content" source="./media/front-door-apex-domain/pending-validation.png" alt-text="Screenshot that shows the custom domain Pending validation.":::
-
    - **Azure DNS-based zone**: Select **Add** to create a new TXT record with the value that appears in the Azure DNS zone.
 
-      :::image type="content" source="./media/front-door-apex-domain/validate-custom-domain.png" alt-text="Screenshot that shows validating a new custom domain.":::
-
     - If you're using another DNS provider, manually create a new TXT record with the name `_dnsauth.<your_subdomain>` with the record value as shown on the pane.
 
 1. Close the **Validate the custom domain** pane and return to the **Domains** pane for the Azure Front Door profile. You should see **Validation state** change from **Pending** to **Approved**. If not, wait up to 10 minutes for changes to appear. If your validation doesn't get approved, make sure your TXT record is correct and that name servers are configured correctly if you're using Azure DNS.
@@ -75,14 +71,10 @@ You can use the Azure portal to onboard an apex domain on your Azure Front Door
 
 1. On the **Associate endpoint and route** pane, select the endpoint and route to which you want to associate the domain. Then select **Associate**.
 
-    :::image type="content" source="./media/front-door-apex-domain/associate-endpoint.png" alt-text="Screenshot that shows the associated endpoint and route pane for a domain.":::
-
 1.	Under the **DNS state** column, select **CNAME record is currently not detected** to add the alias record to the DNS provider.
 
     - **Azure DNS**: Select **Add**.
 
-       :::image type="content" source="./media/front-door-apex-domain/cname-record.png" alt-text="Screenshot that shows the Add or update the CNAME record pane.":::
-
     - **A DNS provider that supports CNAME flattening**: You must manually enter the alias record name.
 
 1. After the alias record gets created and the custom domain is associated with the Azure Front Door endpoint, traffic starts flowing.
@@ -115,8 +107,6 @@ Follow the guidance for [configuring HTTPS for your custom domain](standard-prem
 
 1. Select **OK** to submit your changes.
 
-    :::image type="content" source="./media/front-door-apex-domain/front-door-apex-alias-record.png" alt-text="Screenshot that shows an alias record for zone apex.":::
-
 1. The preceding step creates a zone apex record that points to your Azure Front Door resource. It also creates a CNAME record mapping **afdverify** (for example, `afdverify.contosonews.com`) that's used for onboarding the domain on your Azure Front Door profile.
 
 ## Onboard the custom domain on your Azure Front Door
@@ -129,8 +119,6 @@ Follow the guidance for [configuring HTTPS for your custom domain](standard-prem
 
 1. Select **Save** to submit the changes.
 
-   :::image type="content" source="./media/front-door-apex-domain/front-door-onboard-apex-domain.png" alt-text="Screenshot that shows the Add a custom domain pane.":::
-
 ## Enable HTTPS on your custom domain
 
 1. Select the custom domain that was added. Under the section **Custom domain HTTPS**, change the status to **Enabled**.

articles/frontdoor/front-door-how-to-redirect-https.md

@@ -28,8 +28,6 @@ This guide explains how to redirect traffic from HTTP to HTTPS for an Azure Fron
 
 3. Select the **+** icon under *Routing rules* to create a new route. Name the route, for example, **HttpToHttpsRedirect**, and set the *Accepted Protocol* to **HTTP only**. Choose the *Frontend/domains* you want to redirect from HTTP to HTTPS.
 
-    :::image type="content" source="./media/front-door-url-redirect/front-door-designer-routing-rule.png" alt-text="Screenshot of adding a route in Front Door designer.":::
-
 4. In the *Route Details* section, set the *Route Type* to **Redirect**. Choose **Moved (301)** for *Redirect type* and **HTTPS only** for *Redirect protocol*.
 
     :::image type="content" source="./media/front-door-url-redirect/front-door-redirect-config-example.png" alt-text="Screenshot of adding an HTTP to HTTPS redirect route.":::

articles/frontdoor/front-door-security-headers.md

@@ -32,8 +32,6 @@ In this tutorial, you will learn how to:
 
 1. In your Azure Front Door resource, go to **Settings** and select **Rules engine configuration**. Choose the rules engine where you want to add the security header.
 
-    :::image type="content" source="media/front-door-security-headers/front-door-rules-engine-configuration.png" alt-text="Screenshot showing rules engine configuration page of Azure Front Door.":::
-
 2. Click **Add rule** to create a new rule. Name the rule and then select **Add an Action** > **Response Header**.
 
 3. Set the Operator to **Append** to add this header to all incoming requests for this route.
@@ -56,8 +54,6 @@ In this tutorial, you will learn how to:
 
 If you no longer need the security header rule configured in the previous steps, you can remove it. To do this, go to the rules engine in your Azure Front Door resource and select **Delete rule**.
 
-:::image type="content" source="./media/front-door-security-headers/front-door-delete-security-header.png" alt-text="Screenshot showing how to delete the security rule.":::
-
 ## Next steps
 
 To learn how to configure a Web Application Firewall for your Azure Front Door, proceed to the next tutorial.

articles/frontdoor/front-door-tutorial-rules-engine.md

@@ -29,8 +29,6 @@ In this tutorial, you learn how to:
 
 1. Within your Azure Front Door (classic) resource, select **Rule Engine configuration** from under *Settings* on the left side menu pane. Select **+ Add**, give your configuration a name, and start creating your first Rules Engine configuration.
 
-    :::image type="content" source="./media/front-door-rules-engine/rules-engine-tutorial-1.png" alt-text="Screenshot of the rules engine configuration from the Azure Front Door overview page.":::
-
 1. Enter a name for your first rule. Then select **+ Add condition** or **+ Add action** to define your rule.
 
     > [!NOTE]
@@ -40,8 +38,6 @@ In this tutorial, you learn how to:
     > - All paths in the rules engine configuration are case sensitive.
     > - Header names should adhere to [RFC 7230](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6).
 
-    :::image type="content" source="./media/front-door-rules-engine/rules-engine-tutorial-4.png" alt-text="Screenshot of the rules engine configuration page with a single rule.":::
-
 1. Determine the priority of the rules within your configuration by using the Move up, Move down, and Move to top buttons. The priority is in ascending order, meaning the rule first listed is the most important rule.
 
     > [!TIP]
@@ -106,12 +102,8 @@ To remove the Rules Engine configuration from your Front Door (classic):
 
 1. Disassociate any routing rules from the rule engine configuration by selecting the three dots next to the rule engine name and selecting **Associate routing rule**:
 
-    :::image type="content" source="./media/front-door-rules-engine/front-door-rule-engine-routing-association.png" alt-text="Screenshot of the associate routing rules from the menu.":::
-
 1. Uncheck all routing rules associated with this Rule Engine configuration and select **Save**:
 
-    :::image type="content" source="./media/front-door-rules-engine/front-door-routing-rule-association.png" alt-text="Routing rule association":::
-
 1. Delete the Rule Engine configuration from your Front Door:
 
     :::image type="content" source="./media/front-door-rules-engine/front-door-delete-rule-engine-configuration.png" alt-text="Delete Rule Engine configuration":::

articles/frontdoor/how-to-configure-caching.md

@@ -30,8 +30,6 @@ Caching can significantly decrease latency and reduce the load on origin servers
 1. Sign in to the [Azure portal](https://portal.azure.com?azure-portal=true) and navigate to your Azure Front Door profile.
 
 1. Select **Front Door manager** and then select your route.
-   
-    :::image type="content" source="./media/how-to-configure-caching/select-route.png" alt-text="Screenshot of endpoint landing page.":::
 
 1. Select **Enable caching**.