Skip to content

Commit 12236c2

Browse files
author
Jill Grant
authored
Merge pull request #290736 from vhorne/fwm-partner
freshness
2 parents 257fa59 + bc9517d commit 12236c2

File tree

4 files changed

+12
-46
lines changed

4 files changed

+12
-46
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1970,6 +1970,11 @@
19701970
"redirect_url": "/azure/firewall/tutorial-protect-firewall-ddos",
19711971
"redirect_document_id": false
19721972
},
1973+
{
1974+
"source_path_from_root": "/articles/firewall-manager/check-point-overview.md",
1975+
"redirect_url": "/azure/firewall-manager/deploy-trusted-security-partner",
1976+
"redirect_document_id": false
1977+
},
19731978
{
19741979
"source_path_from_root": "/articles/flexible-server/concepts-high-availability.md",
19751980
"redirect_url": "/azure/reliability/reliability-postgre-flexible",

articles/firewall-manager/check-point-overview.md

Lines changed: 0 additions & 35 deletions
This file was deleted.

articles/firewall-manager/deploy-trusted-security-partner.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: firewall-manager
55
author: vhorne
66
ms.service: azure-firewall-manager
77
ms.topic: how-to
8-
ms.date: 09/28/2023
8+
ms.date: 11/19/2024
99
ms.author: victorh
1010
---
1111

@@ -19,8 +19,6 @@ To learn more about supported scenarios and best practice guidelines, see [What
1919
Integrated third-party Security as a service (SECaaS) partners are now available:
2020

2121
- **Zscaler**
22-
- **[Check Point](check-point-overview.md)**
23-
- **iboss**
2422

2523
## Deploy a third-party security provider in a new hub
2624

@@ -83,10 +81,10 @@ To set up tunnels to your virtual hub’s VPN Gateway, third-party providers nee
8381
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.
8482

8583
- [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).
9088

9189
## Configure security with Firewall Manager
9290

@@ -118,7 +116,7 @@ After you finish the route setting steps, the virtual network virtual machines a
118116

119117
Use the partner portal to configure firewall rules. Azure Firewall passes the traffic through.
120118

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.
122120

123121
For more information, see the partner documentation.
124122

articles/firewall-manager/toc.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
- name: Quickstarts
88
items:
99
- name: Secure virtual hub - Bicep
10-
displayName: Resource Manager, ARM, Template
10+
displayName: Resource Manager, ARM, Templatehttps://github.com/MicrosoftDocs/azure-docs-pr/pull/290736/
1111
href: quick-secure-virtual-hub-bicep.md
1212
- name: Secure virtual hub - Terraform
1313
displayName: Terraform
@@ -46,8 +46,6 @@
4646
href: deployment-overview.md
4747
- name: Security partner providers
4848
href: trusted-security-partners.md
49-
- name: Secure hubs using Check Point Cloudguard Connect
50-
href: check-point-overview.md
5149
- name: IP Groups
5250
href: ip-groups.md
5351
- name: Rule processing logic

0 commit comments

Comments
 (0)