Merge pull request #257681 from AbdullahBell/ddos-freshness-update

DDoS Protection: Freshness update: Freshness for DDoS articles

Author: ttorble

articles/ddos-protection/ddos-disaster-recovery-guidance.md

@@ -6,7 +6,7 @@ author: AbdullahBell
 ms.service: ddos-protection
 ms.custom: ignite-2022
 ms.workload: infrastructure-services
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.author: abell
 ms.topic: conceptual
 ---

articles/ddos-protection/ddos-protection-features.md

@@ -7,7 +7,7 @@ ms.service: ddos-protection
 ms.topic: conceptual
 ms.custom: ignite-2022
 ms.workload: infrastructure-services
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.author: abell
 ---
 # Azure DDoS Protection features
@@ -52,6 +52,8 @@ DDoS Protection applies three auto-tuned mitigation policies (TCP SYN, TCP, and
 
 The policy thresholds are auto-configured via machine learning-based network traffic profiling. DDoS mitigation occurs for an IP address under attack only when the policy threshold is exceeded.
 
+For more information, see [View and configure DDoS Protection telemetry](telemetry.md).
+
 ### Metric for an IP address under DDoS attack
 
 If the public IP address is under attack, the value for the metric **Under DDoS attack or not** changes to 1 as DDoS Protection performs mitigation on the attack traffic.
@@ -76,7 +78,7 @@ If you have DDoS Protection, make sure that it's enabled on the virtual network
 
 Monitor your applications independently. Understand the normal behavior of an application. Prepare to act if the application is not behaving as expected during a DDoS attack.
 
-Learn how your services will respond to an attack by [testing through simulations](test-through-simulations.md).
+Learn how your services will respond to an attack by [testing through DDoS simulations](test-through-simulations.md).
 
 ## Next steps
 

articles/ddos-protection/ddos-protection-partner-onboarding.md

@@ -5,7 +5,7 @@ ms.service: ddos-protection
 ms.custom: ignite-2022
 author: AbdullahBell
 ms.topic: how-to
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.author: abell
 ---
 # Partnering with Azure DDoS Protection

articles/ddos-protection/ddos-rapid-response.md

@@ -7,7 +7,7 @@ ms.service: ddos-protection
 ms.topic: how-to
 ms.custom: ignite-2022
 ms.workload: infrastructure-services
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.author: abell
 ---
 # Azure DDoS Rapid Response
@@ -16,7 +16,8 @@ During an active attack, Azure DDoS Network Protection customers have access to
 
 ## Prerequisites
 
-- Before you can complete the steps in this tutorial, you must first create a [Azure DDoS Protection plan](manage-ddos-protection.md).
+- If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+- Before you can complete the steps in this guide, you must first create a [Azure DDoS Protection plan](manage-ddos-protection.md).
 
 ## When to engage DRR
 
@@ -33,11 +34,11 @@ You should only engage DRR if:
 2. Choose **Service** as **DDOS Protection**.
 3. Choose a resource in the resource drop-down menu. _You must select a DDoS Plan that’s linked to the virtual network being protected by DDoS Protection to engage DRR._
 
-    ![Choose Resource](./media/ddos-rapid-response/choose-resource.png)
+    :::image type="content" source="./media/ddos-rapid-response/choose-resource.png" alt-text="Screenshot of creating a DDoS Support Ticket in Azure.":::
 
 4. On the next **Problem** page, select the **severity** as A -Critical Impact and **Problem Type** as ‘Under attack.’
 
-    ![PSeverity and Problem Type](./media/ddos-rapid-response/severity-and-problem-type.png)
+    :::image type="content" source="./media/ddos-rapid-response/severity-and-problem-type.png" alt-text="Screenshot of choosing Severity and Problem Type.":::
 
 5. Complete additional details and submit the support request.
 

articles/ddos-protection/inline-protection-glb.md

@@ -7,7 +7,7 @@ ms.service: ddos-protection
 ms.topic: how-to
 ms.workload: infrastructure-services
 ms.author: abell
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.custom: ignite-fall-2021, ignite-2022
 ---
 

articles/ddos-protection/manage-ddos-protection-template.md

@@ -8,7 +8,7 @@ ms.topic: quickstart
 ms.workload: infrastructure-services
 ms.custom: subject-armqs, mode-arm, ignite-2022, devx-track-arm-template
 ms.author: abell
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ---
 
 # Quickstart: Create and configure Azure DDoS Network Protection using ARM template

articles/ddos-protection/manage-permissions.md

@@ -7,13 +7,13 @@ ms.service: ddos-protection
 ms.topic: how-to
 ms.custom: ignite-2022
 ms.workload: infrastructure-services
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.author: abell
 ---
 
 # Manage DDoS Protection Plans: permissions and restrictions
 
-A DDoS protection plan works across regions and subscriptions. The same plan can be linked to virtual networks from other subscriptions in different regions, across your tenant. The subscription the plan is associated to incurs the monthly recurring bill for the plan, as well as overage charges, in case the number of protected public IP addresses exceed 100. For more information on DDoS pricing, see [pricing details](https://azure.microsoft.com/pricing/details/ddos-protection/).
+A DDoS protection plan works across regions and subscriptions. The same plan can be linked to virtual networks from other subscriptions in different regions, across your tenant. The associated subscription incurs the plan's monthly bill and overage charges if the protected public IP addresses exceed 100. For more information on DDoS pricing, see [pricing details](https://azure.microsoft.com/pricing/details/ddos-protection/).
 
 ## Prerequisites
 
@@ -37,9 +37,9 @@ To enable DDoS protection for a virtual network, your account must also be assig
 
 ## Azure Policy
 
-Creation of more than one plan is not required for most organizations. A plan cannot be moved between subscriptions. If you want to change the subscription a plan is in, you have to delete the existing plan and create a new one.
+Creation of more than one plan isn't required for most organizations. A plan can't be moved between subscriptions. If you want to change the subscription a plan is in, you have to delete the existing plan and create a new one.
 
-For customers who have various subscriptions, and who want to ensure a single plan is deployed across their tenant for cost control, you can use Azure Policy to restrict creation of Azure DDoS Protection plans. This policy will block the creation of any DDoS plans, unless the subscription has been previously marked as an exception. This policy will also show a list of all subscriptions that have a DDoS plan deployed but should not, marking them as out of compliance.
+For customers who have various subscriptions, and who want to ensure a single plan is deployed across their tenant for cost control, you can use Azure Policy to restrict creation of Azure DDoS Protection plans. This policy blocks the creation of any DDoS plans, unless the subscription has been previously marked as an exception. This policy will also show a list of all subscriptions that have a DDoS plan deployed but shouldn't, marking them as out of compliance.
 
 
 ## Next steps

articles/ddos-protection/media/ddos-rapid-response/choose-resource.png

@@ -7,7 +7,7 @@ ms.service: ddos-protection
 ms.topic: tutorial
 ms.custom: ignite-2022
 ms.workload: infrastructure-services
-ms.date: 10/12/2022
+ms.date: 11/06/2023
 ms.author: abell
 ---
 # Tutorial: View and configure Azure DDoS protection telemetry
@@ -24,8 +24,9 @@ In this tutorial, you'll learn how to:
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
 ## Prerequisites
-* Before you can complete the steps in this tutorial, you must first create an [Azure DDoS Protection plan](manage-ddos-protection.md). DDoS Network Protection must be enabled on a virtual network or DDoS IP Protection must be enabled on a public IP address.  
-* DDoS monitors public IP addresses assigned to resources within a virtual network. If you don't have any resources with public IP addresses in the virtual network, you must first create a resource with a public IP address. You can monitor the public IP address of all resources deployed through Resource Manager (not classic) listed in [Virtual network for Azure services](../virtual-network/virtual-network-for-azure-services.md#services-that-can-be-deployed-into-a-virtual-network) (including Azure Load Balancers where the backend virtual machines are in the virtual network), except for Azure App Service Environments. To continue with this tutorial, you can quickly create a [Windows](../virtual-machines/windows/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) or [Linux](../virtual-machines/linux/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) virtual machine.  
+
+* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+* Before you can complete the steps in this tutorial, you must first create a DDoS simulation attack to generate the telemetry. Telemetry data is recorded during an attack. For more information, see [Test DDoS Protection through simulation](test-through-simulations.md).
 
 ## View Azure DDoS Protection telemetry