|
| 1 | +--- |
| 2 | +title: 'About Third Party Integrations - Virtual WAN hub' |
| 3 | +titleSuffix: Azure Virtual WAN |
| 4 | +description: Learn about third-party integrations available in a Virtual WAN hub. |
| 5 | +author: wtnlee |
| 6 | +ms.service: virtual-wan |
| 7 | +ms.topic: conceptual |
| 8 | +ms.date: 04/26/2024 |
| 9 | +ms.author: wellee |
| 10 | +# Customer intent: As someone with a networking background, I want to learn about third-party integrations in a Virtual WAN hub. |
| 11 | +--- |
| 12 | +# Third-party integrations with Virtual WAN Hub |
| 13 | + |
| 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 | + |
| 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 | + |
| 18 | +## Integrated Network Virtual Appliances |
| 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. |
| 21 | + |
| 22 | +:::image type="content" source="./media/third-party-solutions/integrated-network-virtual-appliances.png" alt-text="Integrated NVA architecture diagram." lightbox="./media/third-party-solutions/integrated-network-virtual-appliances.png"::: |
| 23 | + |
| 24 | +As a 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 | + |
| 26 | +Integrated NVAs typically fall into three categories based on their capabilities: |
| 27 | + |
| 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 capabilities on the same device. |
| 31 | + |
| 32 | +For more information on Integrated NVAs in the Virtual WAN hub, see [NVA in the hub documentation](about-nva-hub.md). |
| 33 | + |
| 34 | +The following solutions are currently available as Integrated NVA partners: |
| 35 | + |
| 36 | +|Capability Type(s)| Available Partners| |
| 37 | +|--|--| |
| 38 | +|Connectivity|Barracuda, VMware (formerly known as Velocloud), Cisco Viptela, Aruba, Versa | |
| 39 | +|Next-Generation Firewall (NGFW)|Check Point, Fortinet, Cisco FTDV| |
| 40 | +| Dual-role connectivity and NGFW | Fortinet | |
| 41 | + |
| 42 | +For more information and resources on each Integrated NVA solution, see [NVA in the hub partners](about-nva-hub.md#partners). |
| 43 | + |
| 44 | +## Software-as-a-service (SaaS) solutions |
| 45 | + |
| 46 | +Softeware-as-a-service (SaaS) solutions in Virtual WAN are managed 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 | + |
| 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. |
| 49 | + |
| 50 | +:::image type="content" source="./media/third-party-solutions/software-as-a-service.png" alt-text="SaaS architecture diagram." lightbox="./media/third-party-solutions/software-as-a-service.png"::: |
| 51 | + |
| 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 information on the SaaS offering provided by Palo Alto Networks, see [Palo Alto Networks Cloud NGFW documentation](how-to-palo-alto-cloud-ngfw.md) |
| 53 | + |
| 54 | +## Azure Firewall Manager security partners providers |
| 55 | + |
| 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 through Azure Firewall Manager automatically establishes a Site-to-site VPN tunnel between the third-party security infrastructure and the Virtual WAN hub's Site-to-site VPN Gateway. |
| 57 | + |
| 58 | +:::image type="content" source="./media/third-party-solutions/security-as-a-service.png" alt-text="SECaaS architecture diagram." lightbox="./media/third-party-solutions/security-as-a-service.png"::: |
| 59 | + |
| 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 information 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