Virtual WAN partners, regions, and virtual hub locations
This article provides information on Virtual WAN supported regions and partners for connectivity into a Virtual WAN hub.
There are two types of offerings that make connecting to Azure easier:
- Network Virtual Appliances (NVAs) deployed in a Virtual WAN hub: Customers can deploy Network Virtual Appliances directly into a Virtual WAN hub. This solution is jointly managed by Microsoft Azure and third-party Network Virtual Appliance solution providers. To learn more about NVAs deployed in a Virtual WAN hub, see About NVAs in a Virtual WAN hub.
- Branch IPsec connectivity automation: Customers can automatically configure and connect their branch devices to the Azure Virtual WAN Site-to-site VPN gateway using IPsec tunnels. These configurations are typically set up in the device-management UI (or equivalent).
Partners with integrated virtual hub offerings
Some partners offer Network Virtual Appliances (NVAs) that can be deployed directly into the Azure Virtual WAN hub through a solution that is jointly managed by Microsoft Azure and third-party Network Virtual Appliance solution providers.
When a Network Virtual Appliance is deployed into a Virtual WAN hub, it can serve as a third-party gateway with various functionalities. It could serve as an SD-WAN gateway, Firewall or a combination of both. For more information about the benefits of deploying an NVA into a Virtual WAN hub, see About NVAs in a Virtual WAN hub.
The following SD-WAN connectivity Network Virtual Appliances can be deployed in the Virtual WAN hub.
Partners | Virtual WAN NVA Vendor Identifier | Configuration/How-to/Deployment guide | Dedicated support model |
---|---|---|---|
Barracuda Networks | barracudasdwanrelease | Barracuda SecureEdge for Virtual WAN Deployment Guide | Yes |
Cisco SD-WAN | ciscosdwan | The integration of the Cisco SD-WAN solution with Azure virtual WAN enhances Cloud OnRamp for Multi-Cloud deployments and enables configuring Cisco Catalyst 8000V Edge Software (Cisco Catalyst 8000V) as a network virtual appliance (NVA) in Azure Virtual WAN hubs. View Cisco SD-WAN Cloud OnRamp, Cisco IOS XE Release 17.x configuration guide | Yes |
VMware SD-WAN | vmwaresdwaninvwan | VMware SD-WAN in Virtual WAN hub deployment guide. The managed application for deployment can be found at this Azure Marketplace link. | Yes |
Versa Networks | versanetworks | If you're an existing Versa Networks customer, log on to your Versa account and access the deployment guide using the following link Versa Deployment Guide. If you're a new Versa customer, sign-up using the Versa preview sign-up link. | Yes |
Aruba EdgeConnect | arubaedgeconnectenterprise | Aruba EdgeConnect SD-WAN deployment guide. Currently in Preview: Azure Marketplace link | No |
The following security Network Virtual Appliance can be deployed in the Virtual WAN hub. This Virtual Appliance can be used to inspect all North-South, East-West, and Internet-bound traffic.
Partners | Virtual WAN NVA Vendor | Configuration/How-to/Deployment guide | Dedicated support model |
---|---|---|---|
Check Point CloudGuard Network Security for Azure Virtual WAN | checkpoint | Check Point Network Security for Virtual WAN deployment guide | No |
Fortinet Next-Generation Firewall (NGFW) | fortinet-ngfw | Fortinet NGFW deployment guide. Fortinet NGFW supports up to 80 scale units and isn't recommended to be used for SD-WAN tunnel termination. For Fortigate SD-WAN tunnel termination, see Fortinet SD-WAN and NGFW documentation. | No |
The following dual-role SD-WAN connectivity and security (Next-Generation Firewall) Network Virtual Appliances can be deployed in the Virtual WAN hub. These Virtual Appliances can be used to inspect all North-South, East-West, and Internet-bound traffic.
Partners | Virtual WAN NVA Vendor | Configuration/How-to/Deployment guide | Dedicated support model |
---|---|---|---|
Fortinet Next-Generation Firewall (NGFW) | fortinet-sdwan-and-ngfw | Fortinet SD-WAN and NGFW NVA deployment guide. Fortinet SD-WAN and NGFW NVA supports up to 20 scale units and supports both SD-WAN tunnel termination and Next-Generation Firewall capabilities. | No |
Branch IPsec connectivity automation from partners
Devices that connect to Azure Virtual WAN have built-in automation to connect. This is typically set up in the device-management UI (or equivalent), which sets up the connectivity and configuration management between the VPN branch device to an Azure Virtual hub VPN endpoint (VPN gateway).
The following high-level automation is set up in the device console/management center:
- Appropriate permissions for the device to access Azure Virtual WAN Resource Group.
- Uploading of Branch Device into Azure Virtual WAN.
- Automatic download of Azure connectivity information.
- Configuration of on-premises branch device.
Some connectivity partners may extend the automation to include creating the Azure Virtual hub VNet and VPN gateway. If you want to know more about automation, see Automation guidelines for Virtual WAN partners.
Branch IPsec connectivity partners
You can check the links in this section for more information about services offered by partners. If your branch device partner is not listed in the section below, have your branch device provider contact us. They can contact us by sending an email to azurevirtualwan@microsoft.com.
* Direct link unavailable. Please contact partner company for support.
The following partners are slated on our roadmap based on a terms sheet signed between the companies indicating the scope of work to automate IPsec connectivity between the partner device and Azure Virtual WAN VPN gateways: 128 Technologies, Arista, F5 Networks, Oracle SD-WAN (Talari), and SharpLink.
Available regions
To view the available regions for Virtual WAN, see Products available by region. Specify Virtual WAN as the product name.
Next steps
For more information about Virtual WAN, see the Virtual WAN FAQ.
For more information about how to automate connectivity to Azure Virtual WAN, see Automation guidelines for Virtual WAN partners.
Povratne informacije
https://aka.ms/ContentUserFeedback.
Stiže uskoro: Tokom 2024. godine postepeno ćemo ukidati probleme sa uslugom GitHub kao mehanizam povratnih informacija za sadržaj i zameniti ga novim sistemom povratnih informacija. Dodatne informacije potražite u članku:Prosledite i prikažite povratne informacije za