Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Cisco Catalyst SD-WAN
Score 8.8 out of 10
N/A
Cisco Catalyst SD-WAN is a software-defined wide area network solution designed to simplify and optimize enterprise network connectivity in complex digital landscapes. It enables organizations to connect any user to any application, whether on-premises, in data centers, or across multiple clouds, with integrated capabilities for multicloud support, security, predictive automation, and enhanced network visibility—all built on a Secure Access Service Edge (SASE)-enabled…
N/A
Cisco Meraki SD-WAN
Score 8.7 out of 10
N/A
Cisco Meraki SD-WAN is a cloud-managed solution that simplifies and secures wide area networking across branch, campus, and remote locations. Built on Meraki’s dashboard, it delivers centralized visibility, automation, and traffic optimization without the complexity of traditional WAN deployments. The solution improves application performance by dynamically routing traffic based on real-time conditions, integrating advanced security, and providing seamless multicloud connectivity. With support…
N/A
Pricing
Azure DevOps
Cisco Catalyst SD-WAN
Cisco Meraki SD-WAN
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Cisco Catalyst SD-WAN is more sophisticated and has a wider range of functionalities than the Meraki SD-WAN solution. For Meraki SD-WAN you cannot configure all policies that it is possible for Cisco Catalyst SD-WAN. Meraki SD-WAN is more as plug and play solution. For Cisco …
Silver Peak is a pretty solid product as well. It does not offer as many customizations, but that also makes onboarding significantly easier. It's a tradeoff between the amount of supported features and the complexity of the dashboard. Similarly if you are willing to …
Actually quite well, I will say. Like I said, I think the one thing that is probably holding us back is what do we need to do to clean up our environment now if we're able to do that right now, I think we wouldn't even be in this RFP process.
When we analyzed Meraki it was clear for us, that our company complexity and need required another level of maturity that was not present for there but it was for Viptela SDWAN now Cisco SDWAN.
Efficient enterprise solution for multi-cloud environments with optimum support and a company which has been leader in the market and keep up to date with latest tendencies, appropriate solution providers in network world
We compared Cisco WD-WAN with several other vendors, including service providers. We are already a Cisco shop, so that gave Cisco and Meraki a leg up. With our hope to expand this beyond Telecommuters to actual sites, we wanted to maintain an in-house solution rather than a …
Cisco Meraki auto-VPN works great and easily in SMBs. Meraki has few limitations that won’t make it as number 1 choice for big customers. Cisco vip tela solution is more inclusive. It has all the integration's capability
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
The best case, what I recommend to others and to clients to use is Cisco Catalyst SD-WAN one for is the case when you have a huge number of branches or small offices or remote offices, you name it. Even home offices, you have a large number and you want this whole infrastructure to be extremely easy to set up and also to have everything almost the same, not to have deviations from the standard configuration. This is the sweet spot for introducing Cisco Catalyst SD-WAN.
At our level, we had to optimize our 3 internet links (MPLS and LTE) with applications like O365, SAP, Microsoft CRM Dynamics and our collaborative work tools like Teams. We also had to ensure that both client workstations and servers could communicate with minimal latency with our Microsoft Intune infrastructure.
We are able to use a multiple different circuits to go into the cloud, so we are not relying on just one particular private wireless. We're relying on wine circuits, ethernet, ethernet out. So it provides us that flexibility where we didn't have that before. Provides security that is very robust and flexible and scalable and it provides us with, the biggest thing is redundancy, where we have backup. For example, we have a Starlink for nuclear power plants. If our main circuits go down, we have that. And without Cisco Catalyst SD-WAN it would be very hard to actually achieve, to accomplish true redundancy. So we're happy with Cisco Catalyst SD-WAN in that regard.
Meraki has been beautifully done for people who are actually very lean on the IT infrastructure as in resources wise. So Meraki is a very good solution to give them the simplicity on a single glass plan where they can actually have visibility over all their networks on a single glass plane by a click of button, they could actually see what's happening. They could actually do troubleshooting on the fly, including packet capture, which is such a smooth feature. Usually myself including I've been have an engineering background, all my ears packet capture, I've never seen that smooth and easy to operate that you can actually have a high level understanding or deep level depending on how much you want to go in with the click of a button. That's so beautiful. I mean everything for me Meraki is point of kind of a go ahead for everyone.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I will say the way we use it now, and I think what happened was the way it was deployed, it was fine, but unfortunately over the course of the years we've gotten a little out of hand with our device templates and feature templates. I think if there's any form of feedback that I would give to Cisco is how do we find ways to improve the environment as it stands so we get to a certain point with the environment and then we don't know how to undo it or fix it or optimize the environment. Because right now we're in a position where we're playing a lot of catch up and clean up and if there was a way or some tool or feature that we can take advantage of that would allow us to optimize that environment where we will kind of corner ourselves into a lot of problems in the future. There's some feature or something that we could take advantage of that will allow us to optimize that environment and not let it get out of control pretty easily. That would be my suggestion.
The platform itself is very feature-rich. One of the difficulties we find is that to do things, for example, in terms of monitoring and obtaining data, it's not consistent. There are multiple interfaces to get them, but you can't get the same data through all interfaces. So you end up having to try to find either the least common denominator or we have to build our own code that then mines through all the interfaces and that becomes very problematic.
The other problem we've found is that there are issues where the same amount of expected software quality isn't really there in all releases. Cisco breaks things out by like shorter or long-lived release trains. And the long-lived release trains tend to have good quality by the time you get to the second or third release within it. But then those are skips. There are like 12, 18 months skips in between those. So if you start releasing features on versions in between there practically to be safe, you have to wait until you know much later. So to be able to see new future capabilities as they come out and deploy those readily needs to improve, it needs to be much faster.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
I would rate SD-WAN highly because it has significantly improved network performance, reliability, and cost-efficiency for my organization. Its ability to optimize traffic dynamically, enhance security, and simplify management across multiple locations has been invaluable. With SD-WAN, we’ve reduced dependency on costly MPLS, improved cloud application performance, and gained greater control over our network infrastructure.
Because so far the solution showed great stability during the time, easy to use and deploy. There is still room for improvements like adding a smarter way to manage the policies to apply to the tunneled traffic, today the way to configure and manage them is quite old style, It would be better an "object" oriented way to create them.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
The niche configurations are given equal focus as the standard use cases, which can make onboarding difficult in the beginning (ie why am I not using an entire tab of the portal), but aside from that part, the dashboard is relatively easy to navigate and apply the configuration. The metrics and analytics available are also nice to have in a single pane.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Al ser soluciones integradas del portafolio de soluciones de Cisco, el soporte es transversal a cada uno de los componentes implementados, teniendo el cliente la capacidad de resolver sus inconvenientes bajo una misma infraestructura que está totalmente homologada, satisfacciendo de esta manera, las necesidades del cliente asi como permitiendo, que este se concentre en su negocio. Since the Cisco SD-WAN tools are a part of Cisco’s broader portfolio of solutions, support cross-cuts to each of our deployed components, with our company as the customer having the ability to solve our problems through the same, approved infrastructure. Their support team easily satisfies the customer’s needs so that they continue to focus on business functions.
Fast and efficient. The only issue currently is that the support is only overseas support and not in South Africa, which causes delays in resolution for some cases. Escalating issues is quite simple and the opening of new cases from the dashboard is easy. I have never had a support issue that could not be resolved.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
We've used the old Cisco SD-WAN, which no longer exists. It was a lot more complex to configure what is now called Cisco Catalyst SD-WAN. So they've definitely come a long way in that it is a lot less complicated to set up and template based.
Cisco Meraki SD-WAN is way more easy to configure as they do not use a command line interface, but a graphical user interface. Cisco Meraki SD-WAN also has configuration templates, which allows for multiple devices configuration with much less effort than conventional command line interface devices. Monitoring is also a benefit over regular devices.
Being a cloud-first solution, Meraki Dashboard will scale as needed without any effort for the client. The Meraki cloud will provision (upscale and downscale) the resources as you grow or shrink in size. You only have to physically install the MX on your site, all the management is one through the Internet via Meraki Dashboard. Worth noting that you can fully-configure the MX prior to the physical installation on site.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
Our branch offices can connect to our enterprise network and the internet quickly and securely, which has helped to increase productivity and reduce downtime.
We have been able to reduce our dependence on expensive MPLS connections, and instead utilize a combination of broadband and LTE connections, which are more cost-effective
The centralized location improves network visibility and troubleshooting process
Cisco Meraki SD-WAN gave us a new perspective on SDN, ZTP and other automation tools we didn't have before
The sizing of Meraki MX series cannot compete very large and robust networks, only if we use virtual appliances. In this case, I would recommend on other vendors like Fortinet
