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
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,48 +6,48 @@ author: wtnlee
6
6
ms.service: virtual-wan
7
7
ms.topic: conceptual
8
8
ms.date: 04/26/2024
9
-
.author: wellee
9
+
ma.author: wellee
10
10
# Customer intent: As someone with a networking background, I want to learn about third-party integrations in a Virtual WAN hub.
11
11
---
12
12
# Third-party integrations with Virtual WAN Hub
13
13
14
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.
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. This 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 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)
17
17
18
18
## Integrated Network Virtual Appliances
19
19
20
20
21
-
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 are deployed as Microsoft-owned and managed Virtual Machine scale-sets 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
+
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.
26
26
27
-
Integrated NVAs typically fall into 3 categories based on their capabilities:
27
+
Integrated NVAs typically fall into three categories based on their capabilities:
28
28
29
29
***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.
30
30
***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.
31
-
***Dual-role connectivty and Firewall**: NVAs in the hub that provide both connectivity and next-generation firewall security capabiliites on the same device.
31
+
***Dual-role connectivity and Firewall**: NVAs in the hub that provide both connectivity and next-generation firewall security capabiliites on the same device.
32
32
33
33
For more information on Integrated NVAs in the Virtual WAN hub, see [NVA in the hub documentation](about-nva-hub.md). For the list of NVAs that can be deployed in Virtual WAN see [NVA in the hub partners](about-nva-hub.md#partners).
34
34
35
35
36
36
37
37
## Software-as-a-service (SaaS) solutions
38
38
39
-
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 needed to run networking and security software in Virtual WAN and provides customers a cloud-native operational interface to program and customize SaaS configurations.
39
+
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.
40
40
41
41
42
42
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.
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-networks-cloud-ngfw.md)
46
+
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)
Azure Firewall Manager security partner integrations automates connecting Virtual WAN to a third-party security-as-a-service (SECaS) offering to protect internet access for your users. SECaaS solutions are hosted by the SECaaS provider and are not deployed directing in 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.
50
+
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.
0 commit comments