Microsoft's Azure Virtual WAN connects global branch offices, point-of-sale locations, and sites using Azure and the Microsoft global network. With it the user can plan, configure, and seamlessly deploy new connections.
N/A
VMware SD-WAN
Score 7.3 out of 10
N/A
VMware SD-WAN (formerly VeloCloud) aims to deliver high-performance, reliable branch access to cloud services, private data centers, and SaaS-based enterprise applications. VeloCloud was acquired by VMware in 2018.
Azure Virtual WAN provides single functional interphase for routing, monitoring, connectivity and security operations. The connection of hubs in Azure virtual WAN makes it simple for us to use Microsoft as the pillar of our spoke connectivity. The platform provides us with robust connectivity features that allow for transitive connectivity across different spokes. However, you should always ensure you have understood your total cost of ownership to avoid potential price bombshells.
VeloCloud was the #1 choice out of various POCs performed when migrating off of MPLS into an ADI/public internet circuit environment. Their ability to also be top of rack with certain software vendors played a major role in improving user experience. Their dynamic DMPO and circuit load balancing can cause some challenges when working with other entities that use a static whitelisting service for access to resources.
VMware SD-WAN has great usability. We have had a positive experience with the solution. It has helped solved a number of issues with our network such as visibility in user usage, application usage, and prioritizing critical application network traffic. VMware SD-WAN user interface is also very easy to understand and configure.
There are still some glitches that need to be worked out. As an example, I rebooted a device at one of our branch locations and it just died. That should never have happened, and I've only seen this happen when a company needs to improve hardware on some of their lower-end models.
As we were already using Azure as a cloud platform, it was easy setting up a Virtual WAN inside Azure as users/developers and DevOps engineers were familiar with the user interface and functioning as compared to going to some other portal for just the VWAN solution. The umbrella of features provided by Azure Virtual WAN made it the right choice for our infrastructure.
We preferred the features and UI of the Velocloud compared to FortiGate SDWAN. They seemed to offer the same sets of information in different layouts. Our company decided on Velocloud for personal/aesthetic reasons. They offered a more concise set of graphs and tables out of the box for us. SD WAN provided us a with a broader look into our connections with a more robust view, which Velocloud backed by Vmware, gave us.
