Skip to content

Commit 78d97cb

Browse files
committed
acrolinx update.
1 parent 9e95383 commit 78d97cb

9 files changed

+30
-31
lines changed

articles/ddos-protection/alerts.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,12 @@ You can select any of the available Azure DDoS Protection metrics to alert you w
4848
|Resource | Select the specific **Public IP address** you want to log metrics for. |
4949

5050
1. Select **Done**, then select **Next: Condition**.
51-
1. On the **Condition** page, select **+ Add Condition**, then in the *Search by signal name* search box, search and select **Under DDoS attack or not**.
51+
1. On the **Condition** page, select **+ Add Condition**, then in the *Search by signal name* search box, search, and select **Under DDoS attack or not**.
5252

5353
:::image type="content" source="./media/ddos-alerts/ddos-protection-alert-add-condition.png" alt-text="Screenshot of adding DDoS Protection attack alert condition." lightbox="./media/ddos-alerts/ddos-protection-alert-add-condition.png":::
5454

55-
1. In the **Create an alert rule** page, enter or select the following information.
55+
1. In the **Create an alert rule** page, select the following information.
56+
5657
:::image type="content" source="./media/ddos-alerts/ddos-protection-alert-signal.png" alt-text="Screenshot of adding DDoS Protection attack alert signal." lightbox="./media/ddos-alerts/ddos-protection-alert-signal.png":::
5758

5859
| Setting | Value |
@@ -83,7 +84,7 @@ You can select any of the available Azure DDoS Protection metrics to alert you w
8384
| Display name | This display name will be shown as the action group name in email and SMS notifications. For this example, enter **myDDoSAlerts**. |
8485

8586

86-
1. On the *Notifications* tab, under *Notification type*, select the notification type you wish to use. For this example we will select **Email/SMS message/Push/Voice**. In the *Name* tab, enter **myUnderAttackEmailAlert**.
87+
1. On the *Notifications* tab, under *Notification type*, select the notification type you wish to use. For this example, we select **Email/SMS message/Push/Voice**. In the *Name* tab, enter **myUnderAttackEmailAlert**.
8788

8889
:::image type="content" source="./media/ddos-alerts/ddos-protection-alert-action-group-notification.png" alt-text="Screenshot of adding DDoS Protection attack alert notification type." lightbox="./media/ddos-alerts/ddos-protection-alert-action-group-notification.png":::
8990

articles/ddos-protection/ddos-diagnostic-alert-templates.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,11 @@ DDoS Protection diagnostic logging alerts provide visibility into DDoS attacks a
2727

2828
## Configure diagnostic logging alerts through Azure Monitor
2929

30-
With these templates, you'll be able to configure alerts for all public IP addresses that you have enabled diagnostic logging on.
30+
With these templates, you are able to configure alerts for all public IP addresses that you have enabled diagnostic logging on.
3131

3232
### Create Azure Monitor alert rule
3333

34-
The Azure Monitor alert rule template will run a query against the diagnostic logs to detect when an active DDoS mitigation is occurring. The alert indicates a potential attack. Action groups can be used to invoke actions as a result of the alert.
34+
The Azure Monitor alert rule template runs a query against the diagnostic logs to detect when an active DDoS mitigation is occurring. The alert indicates a potential attack. Action groups can be used to invoke actions as a result of the alert.
3535

3636

3737
#### Deploy the template
@@ -49,7 +49,7 @@ The Azure Monitor alert rule template will run a query against the diagnostic lo
4949
| Subscription | Select your Azure subscription. |
5050
| Resource Group | Select your Resource group. |
5151
| Region | Select your Region. |
52-
| Workspace Name | Enter your workspace name. In this example the *Workspace name* is **myLogAnalyticsWorkspace**. |
52+
| Workspace Name | Enter your workspace name. In this example, the *Workspace name* is **myLogAnalyticsWorkspace**. |
5353
| Location | Enter **East US**. |
5454

5555
> [!NOTE]
@@ -79,7 +79,7 @@ This DDoS Mitigation Alert Enrichment template deploys the necessary components
7979
| Alert Name | Leave as default. |
8080
| Security Team Email | Enter the required email address. |
8181
| Company Domain | Enter the required domain. |
82-
| Workspace Name | Enter your workspace name. In this example the *Workspace name* is **myLogAnalyticsWorkspace**. |
82+
| Workspace Name | Enter your workspace name. In this example, the *Workspace name* is **myLogAnalyticsWorkspace**. |
8383

8484
1. Select **Review + create** and then select **Create** after validation passes.
8585

articles/ddos-protection/ddos-pricing-guide.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,13 @@ ms.author: abell
1414

1515
Azure DDoS Protection has two tiers: Network Protection and IP Protection. The Network Protection tier is available for resources deployed in virtual networks that are enabled for DDoS Protection. The IP Protection tier is available for public IP addresses that are enabled for DDoS Protection. We recommend a cost analysis to understand the pricing differences between the tiers. In this article, we show you how to evaluate cost for your environment.
1616

17-
18-
1917
## Cost assessment
2018

2119
Network Protection cost begins once the DDoS protection plan is created. IP Protection cost begins once the Public IP address is configured with IP Protection, and its associated virtual network isn't protected by a DDoS protection plan.
2220
For more information, see [Azure DDoS Protection Pricing](https://azure.microsoft.com/pricing/details/ddos-protection/).
2321

2422
When IP Protection is enabled for a public IP resource and a DDoS protection plan is created and enabled on its virtual network, customers are billed for the lower *per Public IP resource* rate. In this case, we'll automatically start billing for Network Protection.
23+
2524
## Example scenarios
2625

2726
For this section we use the following pricing information:
@@ -39,13 +38,13 @@ In this example, we compare the cost of Network Protection and IP Protection for
3938

4039
#### Network Protection
4140

42-
Let's assume you have only one subscription in your tenant. If you create a Network Protection plan, the plan includes protection for 100 IP address. That subscription is billed for $2944 USD per month (29.5 USD x 100 resources). To learn more about different scenarios within DDoS Network Protection, see [Pricing examples](https://azure.microsoft.com/pricing/details/ddos-protection/#pricing).
41+
Let's assume you have only one subscription in your tenant. If you create a Network Protection plan, the plan includes protection for 100 IP address. That subscription is billed for $2,944 USD per month (29.5 USD x 100 resources). To learn more about different scenarios within DDoS Network Protection, see [Pricing examples](https://azure.microsoft.com/pricing/details/ddos-protection/#pricing).
4342

4443
#### IP Protection
4544

46-
Let's take this same scenario and assume you have 10 Public IP addresses. If you enable IP Protection for each Public IP address, you're billed for $1990 USD per month (199 USD x 10 resources).
45+
Let's take this same scenario and assume you have 10 Public IP addresses. If you enable IP Protection for each Public IP address, you're billed for $1,990 USD per month (199 USD x 10 resources).
4746

48-
Under this scenario, it's more cost effective to enable IP Protection for each Public IP address. For environments with more than 15 Public IP addresses, it's more cost effective to create a Network Protection plan. To calculate your unique pricing scenarios, see the [pricing calculator](https://azure.microsoft.com/pricing/calculator/?service=ddos-protection).
47+
Under this scenario, its more cost effective to enable IP Protection for each Public IP address. For environments with more than 15 Public IP addresses, it's more cost effective to create a Network Protection plan. To calculate your unique pricing scenarios, see the [pricing calculator](https://azure.microsoft.com/pricing/calculator/?service=ddos-protection).
4948

5049
> [!NOTE]
5150
> Network Protection includes valued-added benefits such as DDoS Rapid Protection, WAF Discount, and Cost Protection. For more information, see [Azure DDoS Protection SKU Comparison](ddos-protection-sku-comparison.md).

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ Azure DDoS Protection monitors actual traffic utilization and constantly compare
2020

2121
During mitigation, traffic sent to the protected resource is redirected by the DDoS protection service and several checks are performed, such as:
2222

23-
- Ensure packets conform to internet specifications and are not malformed.
23+
- Ensure packets conform to internet specifications and aren't malformed.
2424
- Interact with the client to determine if the traffic is potentially a spoofed packet (e.g: SYN Auth or SYN Cookie or by dropping a packet for the source to retransmit it).
2525
- Rate-limit packets, if no other enforcement method can be performed.
2626

27-
Azure DDoS Protection drops attack traffic and forwards the remaining traffic to its intended destination. Within a few minutes of attack detection, you are notified using Azure Monitor metrics. By configuring logging on DDoS Protection telemetry, you can write the logs to available options for future analysis. Metric data in Azure Monitor for DDoS Protection is retained for 30 days.
27+
Azure DDoS Protection drops attack traffic and forwards the remaining traffic to its intended destination. Within a few minutes of attack detection, you're notified using Azure Monitor metrics. By configuring logging on DDoS Protection telemetry, you can write the logs to available options for future analysis. Metric data in Azure Monitor for DDoS Protection is retained for 30 days.
2828

2929
## Adaptive real time tuning
3030

articles/ddos-protection/ddos-protection-sku-comparison.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -41,14 +41,14 @@ The following table shows features and corresponding tiers.
4141
| WAF discount | Not available | Yes |
4242
| Price | Per protected IP | Per 100 protected IP addresses |
4343

44-
>[!Note]
45-
>At no additional cost, Azure DDoS infrastructure protection protects every Azure service that uses public IPv4 and IPv6 addresses. This DDoS protection service helps to protect all Azure services, including platform as a service (PaaS) services such as Azure DNS. For more information on supported PaaS services, see [DDoS Protection reference architectures](ddos-protection-reference-architectures.md). Azure DDoS infrastructure protection requires no user configuration or application changes. Azure provides continuous protection against DDoS attacks. DDoS protection does not store customer data.
44+
> [!NOTE]
45+
> At no additional cost, Azure DDoS infrastructure protection protects every Azure service that uses public IPv4 and IPv6 addresses. This DDoS protection service helps to protect all Azure services, including platform as a service (PaaS) services such as Azure DNS. For more information on supported PaaS services, see [DDoS Protection reference architectures](ddos-protection-reference-architectures.md). Azure DDoS infrastructure protection requires no user configuration or application changes. Azure provides continuous protection against DDoS attacks. DDoS protection does not store customer data.
4646
4747
## Limitations
4848

4949
DDoS Network Protection and DDoS IP Protection have the following limitations:
5050

51-
- PaaS services (multi-tenant), which includes Azure App Service Environment for Power Apps, Azure API Management in deployment modes other than APIM with virtual network integration (For more information see https://techcommunity.microsoft.com/t5/azure-network-security-blog/azure-ddos-standard-protection-now-supports-apim-in-vnet/ba-p/3641671), and Azure Virtual WAN aren't currently supported.
51+
- PaaS services (multi-tenant), which includes Azure App Service Environment for Power Apps, Azure API Management in deployment modes other than APIM with virtual network integration (For more information, see https://techcommunity.microsoft.com/t5/azure-network-security-blog/azure-ddos-standard-protection-now-supports-apim-in-vnet/ba-p/3641671), and Azure Virtual WAN aren't currently supported.
5252
- Protecting a public IP resource attached to a NAT Gateway isn't supported.
5353
- Virtual machines in Classic/RDFE deployments aren't supported.
5454
- VPN gateway or Virtual network gateway is protected by a DDoS policy. Adaptive tuning isn't supported at this stage.
@@ -59,8 +59,8 @@ DDoS IP Protection is similar to Network Protection, but has the following addit
5959

6060
- Public IP Basic tier protection isn't supported.
6161

62-
>[!Note]
63-
>Scenarios in which a single VM is running behind a public IP is supported, but not recommended. For more information, see [Fundamental best practices](./fundamental-best-practices.md#design-for-scalability).
62+
> [!NOTE]
63+
> Scenarios in which a single VM is running behind a public IP is supported, but not recommended. For more information, see [Fundamental best practices](./fundamental-best-practices.md#design-for-scalability).
6464
6565
For more information, see [Azure DDoS Protection reference architectures](./ddos-protection-reference-architectures.md).
6666

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Azure DDoS Protection identifies and mitigates DDoS attacks without any user int
5151

5252
### When to contact Microsoft support
5353

54-
Azure DDoS Network Protection customers have access to the DDoS Rapid Response (DRR) team, who can help with attack investigation during an attack as well as post-attack analysis. For more details, including when you should engage the DRR team, see [DDoS Rapid Response](ddos-rapid-response.md). Azure DDoS IP Protection customers should create a request to connect with Microsoft support. To learn more, see [Create a support request](../azure-portal/supportability/how-to-create-azure-support-request.md).
54+
Azure DDoS Network Protection customers have access to the DDoS Rapid Response (DRR) team, who can help with attack investigation during an attack and post-attack analysis. For more information, including when you should engage the DRR team, see [DDoS Rapid Response](ddos-rapid-response.md). Azure DDoS IP Protection customers should create a request to connect with Microsoft support. To learn more, see [Create a support request](../azure-portal/supportability/how-to-create-azure-support-request.md).
5555

5656
## Post-attack steps
5757

articles/ddos-protection/ddos-switch-ddos-protection-tier.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ ms.custom: template-how-to-pattern
1313

1414
In this guide, we walk through the steps to switch between Network Protection and IP Protection tiers using Azure portal. This guide follows the *Application running on load-balanced virtual machines* architecture. To learn more about the different architectures, see [Azure DDoS Protection reference architectures](./ddos-protection-reference-architectures.md#application-running-on-load-balanced-virtual-machines).
1515

16-
1716
## Prerequisites
1817

1918
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -64,7 +63,7 @@ The DDoS protection plan must be disassociated from the protected resources befo
6463
>To maintain DDoS Protection during migration, ensure IP protection is enabled on all public IPs protected by Network Protection.
6564
6665
1. In the search box at the top of the portal, enter **DDoS protection plans**. Select your DDoS protection plan.
67-
1. In the **Settings** page, select the **Protected Resources** tab, then select the **Dissociate** icon next to the virtual network that contains the resources you are protecting. When prompted, select **Yes** to confirm.
66+
1. In the **Settings** page, select the **Protected Resources** tab, then select the **Dissociate** icon next to the virtual network that contains the resources you're protecting. When prompted, select **Yes** to confirm.
6867

6968
:::image type="content" source="./media/ddos-switch-ddos-protection/ddos-remove-protected-resources.png" alt-text="Screenshot of removing protected resources to DDoS protection plan.":::
7069

0 commit comments

Comments
 (0)