Merge pull request #214371 from halkazwini/fd-headers

Front Door: Freshness: Tutorial: Add Security headers with Rules Engine

Author: jborsecnik

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

@@ -2,14 +2,12 @@
 title: 'Tutorial: Add security headers with Rules Engine - Azure Front Door'
 description: This tutorial teaches you how to configure a security header via Rules Engine on Azure Front Door 
 services: frontdoor
-documentationcenter: ''
 author: duongau
-editor: ''
 ms.service: frontdoor
 ms.topic: tutorial
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 09/14/2020
+ms.date: 10/12/2022
 ms.author: duau
 # Customer intent: As an IT admin, I want to learn about Front Door and how to configure a security header via Rules Engine. 
 ---
@@ -26,32 +24,38 @@ In this tutorial, you learn how to:
 
 ## Prerequisites
 
-* Before you can complete the steps in this tutorial, you must first create a Front Door. For more information, see [Quickstart: Create a Front Door](quickstart-create-front-door.md).
-* If this is your first time using the Rules Engine feature, see how to [Set up a Rules Engine](front-door-tutorial-rules-engine.md).
+* An Azure subscription.
+* An Azure Front Door. To complete the steps in this tutorial, you must have a Front Door configured with rules engine. For more information, see [Quickstart: Create a Front Door](quickstart-create-front-door.md) and [Configure your Rules Engine](front-door-tutorial-rules-engine.md).
 
 ## Add a Content-Security-Policy header in Azure portal
 
-1. Click **Add** to add a new rule. Provide the rule a name and then click **Add an Action** > **Response Header**.
+1. Within your Front door resource, select **Rules engine configuration** under **Settings**, and then select the rules engine that you want to add the security header to.
 
-1. Set the Operator to be **Append** to add this header as a response to all of the incoming requests to this route.
+:::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.":::
 
-1. Add the header name: **Content-Security-Policy** and define the values this header should accept. In this scenario, we choose *"script-src 'self' https://apiphany.portal.azure-api.net."*
+2. Select **Add rule** to add a new rule. Provide the rule a name and then select **Add an Action** > **Response Header**.
+
+3. Set the Operator to **Append** to add this header as a response to all of the incoming requests to this route.
+
+4. Add the header name: *Content-Security-Policy* and define the values this header should accept, then select **Save**. In this scenario, we choose *`script-src 'self' https://apiphany.portal.azure-api.net`*.
+
+:::image type="content" source="./media/front-door-security-headers/front-door-security-header.png" alt-text="Screenshot showing the added security header under.":::
 
    > [!NOTE]
    > Header values are limited to 640 characters.
 
-1. Once you've added all of the rules you'd like to your configuration, don't forget to go to your preferred route and associate your Rules Engine configuration to your Route Rule. This step is required to enable the rule to work. 
+5. Once you've added all of the rules you'd like to your configuration, don't forget to go to your preferred route and associate your Rules engine configuration to the Route Rule. This step is required to enable the rule to work.
 
-![portal sample](./media/front-door-rules-engine/rules-engine-security-header-example.png)
+:::image type="content" source="./media/front-door-security-headers/front-door-associate-routing-rule.png" alt-text="Screenshot showing how to associate a routing rule.":::
 
 > [!NOTE]
 > In this scenario, we did not add [match conditions](front-door-rules-engine-match-conditions.md) to the rule. All incoming requests that match the path defined in the Route Rule will have this rule applied. If you would like it to only apply to a subset of those requests, be sure to add your specific **match conditions** to this rule.
 
 ## Clean up resources
 
-In the preceding steps, you configured Security headers with Rules Engine. If you no longer want the rule, you can remove it by clicking Delete rule.
+In the previous steps, you configured security headers with rules engine of your Front Door. If you no longer want the rule, you can remove it by selecting **Delete rule** within the rules engine.
 
-:::image type="content" source="./media/front-door-rules-engine/rules-engine-delete-rule.png" alt-text="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