You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/firewall-manager/vhubs-and-vnets.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: vhorne
5
5
ms.service: firewall-manager
6
6
services: firewall-manager
7
7
ms.topic: article
8
-
ms.date: 01/11/2023
8
+
ms.date: 03/08/2024
9
9
ms.author: victorh
10
10
---
11
11
@@ -15,10 +15,10 @@ Azure Firewall Manager can provide security management for two network architect
15
15
16
16
-**secured virtual hub**
17
17
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)*.
19
19
-**hub virtual network**
20
20
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.
22
22
23
23
## Comparison
24
24
@@ -36,7 +36,7 @@ The following table compares these two architecture options and can help you dec
|**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|
38
38
|**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 thirdparty 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|
40
40
|**Web Application Firewall on Application Gateway**|Supported in Virtual Network|Currently supported in spoke network|
41
41
|**Network Virtual Appliance**|Supported in Virtual Network|Currently supported in spoke network|
0 commit comments