Skip to content

Commit 4e246ab

Browse files
Merge pull request #278954 from vhorne/fwm-deploy
freshness review
2 parents 7c551e3 + 6251ec2 commit 4e246ab

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/firewall-manager/deployment-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: vhorne
55
ms.service: firewall-manager
66
services: firewall-manager
77
ms.topic: conceptual
8-
ms.date: 05/02/2023
8+
ms.date: 06/21/2024
99
ms.author: victorh
1010
---
1111

@@ -35,7 +35,7 @@ To review network architecture options, see [What are the Azure Firewall Manager
3535

3636
- This is done while you create a Hub Virtual Network
3737
<br>*or*<br>
38-
- Convert an existing virtual network to a Hub Virtual Network. It is also possible to convert multiple virtual networks.
38+
- Convert an existing virtual network to a Hub Virtual Network. It's also possible to convert multiple virtual networks.
3939

4040
4. Configure User Define Routes to route traffic to your Hub Virtual Network firewall.
4141

@@ -53,7 +53,7 @@ To review network architecture options, see [What are the Azure Firewall Manager
5353
3. Create a firewall policy and associate it with your hub
5454

5555
- Applicable only if using Azure Firewall.
56-
- Third-party security as a service (SECaaS) policies are configured via partners management experience.
56+
- Partner security as a service (SECaaS) policies are configured via partners management experience.
5757
4. Configure route settings to route traffic to your secured hub
5858

5959
- Easily route traffic to your secured hub for filtering and logging without User Defined Routes (UDR) on spoke Virtual Networks using the Secured Virtual Hub Route Setting page.
@@ -66,7 +66,7 @@ To review network architecture options, see [What are the Azure Firewall Manager
6666

6767
The following information applies if you convert an existing virtual network to a hub virtual network:
6868

69-
- If the virtual network has an existing Azure Firewall, you select a Firewall Policy to associate with the existing firewall. The firewall provisioning status will be updating while the firewall policy replaces firewall rules. During the provisioning state, the firewall continues processing traffic and has no downtime. You can import existing rules to a Firewall Policy using Firewall Manager or Azure PowerShell.
69+
- If the virtual network has an existing Azure Firewall, you select a Firewall Policy to associate with the existing firewall. The firewall provisioning status is updated while the firewall policy replaces firewall rules. During the provisioning state, the firewall continues processing traffic and has no downtime. You can import existing rules to a Firewall Policy using Firewall Manager or Azure PowerShell.
7070
- If the virtual network doesn't have an associated Azure Firewall, a firewall is deployed and the Firewall Policy is associated with the new firewall.
7171

7272
## Next steps

0 commit comments

Comments
 (0)