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/deploy-trusted-security-partner.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: firewall-manager
5
5
author: vhorne
6
6
ms.service: azure-firewall-manager
7
7
ms.topic: how-to
8
-
ms.date: 09/28/2023
8
+
ms.date: 11/19/2024
9
9
ms.author: victorh
10
10
---
11
11
@@ -19,8 +19,6 @@ To learn more about supported scenarios and best practice guidelines, see [What
19
19
Integrated third-party Security as a service (SECaaS) partners are now available:
20
20
21
21
-**Zscaler**
22
-
-**[Check Point](check-point-overview.md)**
23
-
-**iboss**
24
22
25
23
## Deploy a third-party security provider in a new hub
26
24
@@ -83,10 +81,10 @@ To set up tunnels to your virtual hub’s VPN Gateway, third-party providers nee
83
81
1. Follow your partner provided instructions to complete the setup. This includes submitting Microsoft Entra information to detect and connect to the hub, update the egress policies, and check connectivity status and logs.
84
82
85
83
-[Zscaler: Configure Microsoft Azure Virtual WAN integration](https://help.zscaler.com/zia/configuring-microsoft-azure-virtual-wan-integration).
86
-
-[Check Point: Configure Microsoft Azure Virtual WAN integration](https://www.checkpoint.com/cloudguard/microsoft-azure-security/wan).
87
-
-[iboss: Configure Microsoft Azure Virtual WAN integration](https://www.iboss.com/business/microsoft-365-features-integration/).
88
-
89
-
2.You can look at the tunnel creation status on the Azure Virtual WAN portal in Azure. Once the tunnels show **connected** on both Azure and the partner portal, continue with the next steps to set up routes to select which branches and VNets should send Internet traffic to the partner.
84
+
85
+
2. You can look at the tunnel creation status on the Azure Virtual WAN portal in Azure. Once the tunnels show **connected** on both Azure and the partner portal, continue with the next steps to set up routes to select which branches and VNets should send Internet traffic to the partner.
86
+
87
+
You can add other network virtual appliances to your virtual WAN hub. For more information, see [About NVAs in a Virtual WAN hub](../virtual-wan/about-nva-hub.md).
90
88
91
89
## Configure security with Firewall Manager
92
90
@@ -118,7 +116,7 @@ After you finish the route setting steps, the virtual network virtual machines a
118
116
119
117
Use the partner portal to configure firewall rules. Azure Firewall passes the traffic through.
120
118
121
-
For example, you may observe allowed traffic through the Azure Firewall, even though there's no explicit rule to allow the traffic. This is because Azure Firewall passes the traffic to the next hop security partner provider (ZScalar, CheckPoint, or iBoss). Azure Firewall still has rules to allow outbound traffic, but the rule name isn't logged.
119
+
For example, you may observe allowed traffic through the Azure Firewall, even though there's no explicit rule to allow the traffic. This is because Azure Firewall passes the traffic to the next hop security partner provider (ZScalar). Azure Firewall still has rules to allow outbound traffic, but the rule name isn't logged.
122
120
123
121
For more information, see the partner documentation.
0 commit comments