Skip to content

Commit 98ea1c1

Browse files
committed
corrected acrolinx and updated items on review.
1 parent b6830c2 commit 98ea1c1

File tree

2 files changed

+13
-13
lines changed

2 files changed

+13
-13
lines changed

articles/firewall-manager/configure-ddos.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ ms.custom: template-how-to
1414
Azure Firewall Manager is a platform to manage and protect your network resources at scale. You can associate your virtual networks with a DDoS protection plan within Azure Firewall Manager.
1515

1616
> [!TIP]
17-
> DDoS Protection currently does not support virtual WANs. However, you can workaround this limitation by force tunneling Internet traffic to an Azure Firewall in a virtual network that has a DDoS Protection Plan associated with it.
17+
> DDoS Protection currently doesn't support virtual WANs. However, you can work around this limitation by force tunneling Internet traffic to an Azure Firewall in a virtual network that has a DDoS Protection Plan associated with it.
1818
1919
Under a single tenant, DDoS protection plans can be applied to virtual networks across multiple subscriptions. For more information about DDoS protection plans, see [Azure DDoS Protection overview](../ddos-protection/ddos-protection-overview.md).
2020

21-
To see how this works, you'll create a firewall policy and then a virtual network secured with an Azure Firewall. Then you'll create a DDoS Protection Plan and then associate it with the virtual network.
21+
To see how this works, you create a firewall policy and then a virtual network secured with an Azure Firewall. Then you create a DDoS Protection Plan and then associate it with the virtual network.
2222

2323
## Create a firewall policy
2424

articles/firewall-manager/secure-cloud-network.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ In this tutorial, you learn how to:
2929
> [!IMPORTANT]
3030
> The procedure in this tutorial uses Azure Firewall Manager to create a new Azure Virtual WAN secured hub.
3131
> You can use Firewall Manager to upgrade an existing hub, but you can't configure Azure **Availability Zones** for Azure Firewall.
32-
> It is also possible to convert an existing hub to a secured hub using the Azure portal, as described in [Configure Azure Firewall in a Virtual WAN hub](../virtual-wan/howto-firewall.md). But like Azure Firewall Manager, you can't configure **Availability Zones**.
33-
> To upgrade an existing hub and specify **Availability Zones** for Azure Firewall (recommended) you must follow the upgrade procedure in [Tutorial: Secure your virtual hub using Azure PowerShell](secure-cloud-network-powershell.md).
32+
> It's also possible to convert an existing hub to a secured hub using the Azure portal, as described in [Configure Azure Firewall in a Virtual WAN hub](../virtual-wan/howto-firewall.md). But like Azure Firewall Manager, you can't configure **Availability Zones**.
33+
> To upgrade an existing hub and specify Availability Zones for Azure Firewall (recommended), you must follow the upgrade procedure in [Tutorial: Secure your virtual hub using Azure PowerShell](secure-cloud-network-powershell.md).
3434
3535
:::image type="content" source="media/secure-cloud-network/secure-cloud-network.png" alt-text="Diagram showing the secure cloud network." lightbox="media/secure-cloud-network/secure-cloud-network.png":::
3636

@@ -59,7 +59,7 @@ The two virtual networks each have a workload server in them and are protected b
5959

6060

6161
1. Select **Next**, then select **Next**.
62-
1. In the ****Networking** tab, create a subnet with the following settings:
62+
1. In the **Networking** tab, create a subnet with the following settings:
6363

6464
| Setting | Value |
6565
|--------------------------|----------------------|
@@ -113,10 +113,10 @@ Create your secured virtual hub using Firewall Manager.
113113
1. Select the desired combination of **Availability Zones**.
114114

115115
> [!IMPORTANT]
116-
> A Virtual WAN is a collection of hubs and services made available inside the hub. You can deploy as many Virtual WANs that you need. In a Virtual WAN hub, there are multiple services like VPN, ExpressRoute, and so on. Each of these services is automatically deployed across Availability Zones except Azure Firewall, if the region supports Availability Zones. To align with Azure Virtual WAN resiliency, you should select all available Availability Zones.
116+
> A Virtual WAN is a collection of hubs and services made available inside the hub. You can deploy as many Virtual WANs as you need. In a Virtual WAN hub, there are multiple services like VPN, ExpressRoute, and so on. Each of these services is automatically deployed across Availability Zones except Azure Firewall, if the region supports Availability Zones. To align with Azure Virtual WAN resiliency, you should select all available Availability Zones.
117117
118118

119-
1. Type **1** in the **Specify number of Public IP addressees** text box or associate an existing public IP address (preview) with this firewall.
119+
1. Type **1** in the **Specify number of Public IP addresses** text box or associate an existing public IP address (preview) with this firewall.
120120
1. Under **Firewall Policy** ensure the **Default Deny Policy** is selected. You refine your settings later in this article.
121121
1. Select **Next: Security Partner Provider**.
122122
1. Accept the default **Trusted Security Partner** **Disabled** setting, and select **Next: Review + create**.
@@ -140,12 +140,12 @@ Now you can peer the hub and spoke virtual networks.
140140
1. Select the **fw-manager-rg** resource group, then select the **Vwan-01** virtual WAN.
141141
1. Under **Connectivity**, select **Virtual network connections**.
142142

143-
| Setting | Value |
144-
|-------------------|----------------------|
145-
| Connection name | **hub-spoke-01** |
146-
| Hubs | **Hub-01** |
147-
| Resource group | **fw-manager-rg** |
148-
| Virtual network | **Spoke-01** |
143+
| Setting | Value |
144+
|-------------------|----------------------|
145+
| Connection name | **hub-spoke-01** |
146+
| Hubs | **Hub-01** |
147+
| Resource group | **fw-manager-rg** |
148+
| Virtual network | **Spoke-01** |
149149

150150
1. Select **Create**.
151151
1. Repeat the previous steps to connect the **Spoke-02** virtual network with the following settings:

0 commit comments

Comments
 (0)