Skip to content

Commit 30ccb1a

Browse files
Merge pull request #268492 from vhorne/fwm-architecture
freshness review
2 parents f9b59ed + b8f19df commit 30ccb1a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/firewall-manager/vhubs-and-vnets.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: article
8-
ms.date: 01/11/2023
8+
ms.date: 03/08/2024
99
ms.author: victorh
1010
---
1111

@@ -15,10 +15,10 @@ Azure Firewall Manager can provide security management for two network architect
1515

1616
- **secured virtual hub**
1717

18-
An [Azure Virtual WAN Hub](../virtual-wan/virtual-wan-about.md#resources) is a Microsoft-managed resource that lets you easily create hub and spoke architectures. When security and routing policies are associated with such a hub, it's referred to as a *[secured virtual hub](secured-virtual-hub.md)*.
18+
An [Azure Virtual WAN Hub](../virtual-wan/virtual-wan-about.md#resources) is a Microsoft-managed resource that lets you easily create hub and spoke architectures. When security and routing policies associate with such a hub, it's known as a *[secured virtual hub](secured-virtual-hub.md)*.
1919
- **hub virtual network**
2020

21-
This is a standard Azure virtual network that you create and manage yourself. When security policies are associated with such a hub, it is referred to as a *hub virtual network*. At this time, only Azure Firewall Policy is supported. You can peer spoke virtual networks that contain your workload servers and services. You can also manage firewalls in standalone virtual networks that are not peered to any spoke.
21+
This is a standard Azure virtual network that you create and manage yourself. When security policies are associated with such a hub, it's known as a *hub virtual network*. At this time, only Azure Firewall Policy is supported. You can peer spoke virtual networks that contain your workload servers and services. You can also manage firewalls in standalone virtual networks that aren't peered to any spoke.
2222

2323
## Comparison
2424

@@ -36,7 +36,7 @@ The following table compares these two architecture options and can help you dec
3636
|**Azure Firewall Availability Zones** |Supported|Supported|
3737
|**Advanced Internet security with third-party Security as a Service partners** |Customer established and managed VPN connectivity to partner service of choice|Automated via security partner provider flow and partner management experience|
3838
|**Centralized route management to route traffic to the hub** |Customer-managed User Defined Route|Supported using BGP|
39-
|**Multiple security provider support**|Supported with manually configured forced tunneling to third-party firewalls|Automated support for two security providers: Azure Firewall for private traffic filtering and third party for Internet filtering|
39+
|**Multiple security provider support**|Supported with manually configured forced tunneling to third-party firewalls|Automated support for two security providers: Azure Firewall for private traffic filtering and third-party for Internet filtering|
4040
|**Web Application Firewall on Application Gateway** |Supported in Virtual Network|Currently supported in spoke network|
4141
|**Network Virtual Appliance**|Supported in Virtual Network|Currently supported in spoke network|
4242
|**Azure DDoS Protection support**|Yes|No|

0 commit comments

Comments
 (0)