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/virtual-wan/third-party-integrations.md
+13-16Lines changed: 13 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,23 +11,23 @@ ms.author: wellee
11
11
---
12
12
# Third-party integrations with Virtual WAN Hub
13
13
14
-
Virtual WAN hubs can be integrated with third-party networking software solutions that enable connectivity (SD-WAN or VPN) and next-generation firewall (Cloud NGFW) functionalities. The three main deployment models of integrated networking software solutions in Virtual WAN are Integrated Network Virtual Appliances (Integrated NVAs), networking and security software-as-a-service (SaaS) solutions and Azure Firewall Manager security providers.
14
+
Virtual WAN hubs offer integrations with third-party networking software solutions, providing connectivity through SD-WAN or VPN and next-generation firewall (NGFW) functionalities. There are three primary deployment models within Virtual WAN for these solutions: **Integrated Network Virtual Appliances (Integrated NVAs)**, **software-as-a-service (SaaS) networking and security solutions** and **Azure Firewall Manager security providers**.
15
15
16
-
This article focuses on third-party integrations with the Virtual Hub. To facilitate connecting from on-premises to Azure Virtual WAN, certain devices that connect to Azure Virtual WAN have built-in automation to program Site-to-site VPN Gateways in both Virtual WAN and on-premises. Connectivity is typically set up in the device-management UI (or equivalent). For more information on IPsec connectivity automation, see [IPsec automation documentation.](virtual-wan-locations-partners.md)
16
+
This article focuses on third-party integrations with the Virtual Hub. To facilitate connecting from on-premises to Azure Virtual WAN, certain devices that connect to Azure Virtual WAN have automated features to program both Site-to-site VPN Gateways in Virtual WAN and on-premises devices. This set-up is usually managed through the device's management UI. For detailed guidance on IPsec connectivity automation, see [IPsec automation documentation.](virtual-wan-locations-partners.md)
17
17
18
18
## Integrated Network Virtual Appliances
19
19
20
-
Integrated Network Virtual Appliances (NVAs) are Microsoft-managed infrastructure-as-a-service solutions that Microsoft and select NVA providers jointly develop and offer. Integrated Network Virtual Appliances are typically deployed through Azure Marketplace Managed Applications or directly from NVA orchestration software. The backing infrastructure of Network Virtual Appliances is deployed into the Virtual WAN Hub as a Microsoft-owned and managed Virtual Machine scale-set with Azure Load Balancers directly into the Virtual WAN hub. A subset of Azure infrastructure configurations are available for you to manage, scale and troubleshoot your NVA deployments in the Virtual WAN hub.
20
+
Integrated Network Virtual Appliances (NVAs) are Microsoft-managed infrastructure-as-a-service solutions that Microsoft and select NVA providers jointly develop and offer. Integrated Network Virtual Appliances are typically deployed through Azure Marketplace Managed Applications or directly from NVA orchestration software. The backing infrastructure of Network Virtual Appliances is deployed into the Virtual WAN Hub as a Microsoft-owned and managed virtual machine scale-set with Azure Load Balancers directly into the Virtual WAN hub. A subset of Azure infrastructure configurations are available for you to manage, scale and troubleshoot your NVA deployments in the Virtual WAN hub.
As an Integrated NVA user, you can select an NVA infrastructure scale unit up-front that determines the aggregate throughput of the NVA (see provider documentation for expected throughput at each scale unit). You also have full control of the software version and configurations in the Integrated NVA operating system and are in full control of software lifecycle management. Depending on the NVA provider, you may use the command-line or NVA-provider orchestration and management software to apply software version and configuration changes.
24
+
As an user of Integrated NVAs, you have the option to choose a scale unit for the NVA infrastructure scale unit up-front that dictates the aggregate throughput of the NVA (see provider documentation for expected throughput at each scale unit). You maintain full control over the software version and settings within the Integrated NVA operating system, as well as full control of software lifecycle management. Depending on the NVA provider, you may use the command-line or NVA-provider orchestration and management software to implement changes to the software version and configuration .
25
25
26
26
Integrated NVAs typically fall into three categories based on their capabilities:
27
27
28
-
***Connectivity**: NVAs in the hub serve as a connectivity gateway in the Virtual WAN hub allowing you to connect on-premises data centers or site to Azure using NVA-specific connectivity protocols like SD-WAN or IPSEC.
29
-
***Next-generation Firewall**: NVAs in the hub serve as a security appliance in the Virtual WAN hub, allowing you to inspect traffic between on-premises, Azure Virtual Networks and the Internet.
30
-
***Dual-role connectivity and Firewall**: NVAs in the hub that provide both connectivity and next-generation firewall security capabiliites on the same device.
28
+
***Connectivity**: These NVAs acts as a gateway in the Virtual WAN hub, enabling connections from on-premises data centers or sites using SD-WAN or IPSEC.
29
+
***Next-generation Firewall**: These NVAs function as a security device within the Virtual WAN hub, allowing you to inspect traffic between on-premises, Azure Virtual Networks and the Internet.
30
+
***Dual-role connectivity and Firewall**: These NVAs provide both connectivity and next-generation firewall security capabiliites on the same device.
31
31
32
32
For more information on Integrated NVAs in the Virtual WAN hub, see [NVA in the hub documentation](about-nva-hub.md).
33
33
@@ -36,28 +36,25 @@ The following solutions are currently available as Integrated NVA partners:
36
36
|Capability Type(s)| Available Partners|
37
37
|--|--|
38
38
|Connectivity|Barracuda, VMware (formerly known as Velocloud), Cisco Viptela, Aruba, Versa |
39
-
|Next-Generation Firewall (NGFW)|Check Point, Fortinet|
39
+
|Next-Generation Firewall (NGFW)|Check Point, Fortinet, Cisco FTDV|
40
40
| Dual-role connectivity and NGFW | Fortinet |
41
41
42
42
For additional documentation and resources on each Integrated NVA solution, see [NVA in the hub partners](about-nva-hub.md#partners).
43
43
44
44
## Software-as-a-service (SaaS) solutions
45
45
46
-
SaaS solutions in Virtual WAN are SaaS provider-managed software offerings that are deployed through Azure Marketplace directly into your Virtual WAN hub. Software-as-a-service solutions are deployed and transacted through Azure Marketplace. SaaS abstracts the underlying infrastructure that's needed to run networking and security software in Virtual WAN and provides customers a cloud-native operational interface to program and customize SaaS configurations.
46
+
Softeware-as-a-service (SaaS) solutions in Virtual WAN are managd by SaaS providers and are deployed directly into your Virtual WAN hub. Software-as-a-service solutions are deployed and transacted through Azure Marketplace. SaaS solutions abstract the underlying infrastructure required to run networking and security software in Virtual WAN, providing customers with a cloud-native operational interface for programming and customizing SaaS configurations.
47
47
48
-
49
-
The SaaS provider is also in charge of the end-to-end lifecycle management of the software, management and configuration of Azure infrastructure, and scalability of the SaaS solution. For more information on the available configurations and architecture of Virtual WAN SaaS solutions, reference your SaaS provider's documentation.
48
+
The SaaS provider handles the complete lifecycle management of the SaaS software, management and configuration of Azure infrastructure, as well as scalability of the SaaS solution. For specifics on configurations and architecture of Virtual WAN SaaS solutions, consult your SaaS provider's documentation.
Palo Alto Networks Cloud NGFW is the only SaaS solution available in Virtual WAN today and enables next-generation firewall inspection use cases. For more information on the SaaS solution provided by Palo Alto Networks, see [Palo Alto Networks Cloud NGFW documentation](how-to-palo-alto-cloud-ngfw.md)
52
+
Currently, Palo Alto Networks Cloud NGFW is the only SaaS solution available in Virtual WAN today, focusing on next-generation firewall inspection use cases. For more details on the SaaS offering provided by Palo Alto Networks, see [Palo Alto Networks Cloud NGFW documentation](how-to-palo-alto-cloud-ngfw.md)
Azure Firewall Manager security partner integrations automates connecting Virtual WAN to a third-party security-as-a-service (SECaaS) offering to protect internet access for your users. SECaaS solutions are hosted by the SECaaS provider and aren't deployed directly into the Virtual WAN hub. When a SECaaS solution is deployed via Azure Firewall Manager, a Site-to-site VPN tunnel between the third-party security infrastructure and your Virtual WAN hub's Site-to-site VPN Gateway is created automatically.
56
+
Azure Firewall Manager's security partner integrations simplify the process of connecting Virtual WAN to a third-party security-as-a-service (SECaaS) offering, ensuring protected Internet access for users. Unlike SaaS solutions, SECaaS infrastructure isn't deployed directly into the Virtual WAN hub but is still hosted by the SECaaS provider. Deploying a SECaaS solution throguh Azure Firewall Manager automatically establishes a Site-to-site VPN tunnel between the third-party security infrastructure and the Virtual WANhub's Site-to-site VPN Gateway.
Configuration and infrastructure management on the SECaaS solution are available via SECaas provided management tools.
62
-
63
-
The following partners are available as SECaaS solutions in Virtual WAN: Check Point, iBoss and zScalar. For more information about Azure Firewall Manager security partner providers, see [Azure Firewall Manager documentation](../firewall-manager/trusted-security-partners.md) and your preferred provider's documentation.
60
+
Management and configuration of the SECaaS solution are accessible through tools provided by the SECaaS provider. Currently, Virtual WAN's SECaaS solutions include the following partners:Check Point, iBoss and zScalar. For more details about Azure Firewall Manager's security partner providers, refer to both [Azure Firewall Manager documentation](../firewall-manager/trusted-security-partners.md) and your preferred provider's documentation.
0 commit comments