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 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 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)
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.
I believe it is well suited for "pop-up" offices of a small number of people. 5 to 10 is ideal. It can be setup with a minimum of involvement from the IT infrastructure group. It is a very simple way to connect a remote site securely and quickly with the confidence that the connection will be stable. I believe it is less suited for a large organization requiring complex routing and routing protocols. It only works with Meraki endpoints and so there must be Meraki firewalls at both ends. It cannot be used with IPSEC tunnels
I really like the firewalls and the access points, like the wireless ones. From a wireless access point perspective, we recently moved to the new MR57s, multi-gig bandwidth as well as Wi-Fi 6, which helps users connect wirelessly regardless of where they sit in the office. The experience they get doesn’t matter wherever they move—it’s fantastic. So we’ve moved from the previous iteration of Meraki Access Points to the new iteration, like two weeks ago, and we’ve seen a major shift in the user experience.
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 personally think that this particular place is on the logging side. I have seen where the event log is that what they call in terms of capturing all the log events is the area which I personally feel can actually be improved. Even this could be similar, like how I said about packet capture where you could have a flexibility of having a high level information or deep level regardless you should have that kind of option where you could also see the logging site as granular as per the requirement. So that's the area which I think is a bit little behind compared to other vendors.
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.
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.).
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.
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 did a very stringent valuation a few years ago. And we evaluated probably about a dozen suppliers on paper that we evaluate just by capabilities. And, we of some other business criteria, and we whittled that down to a list of five. And out of those five, we brought four of those into our lab environment where we ran approximately 350 different test cases on, we really beat on it pretty heavily. And some of those other suppliers would've been companies like Fortinet Versa Networks Silver Peak, which is now owned by Hewlett Packard.
With the implementation of Cisco Meraki SD-WAN on our new site, this has enabled us to optimize the bandwidth of our 3 links. Thanks to this, updates pushed by Microsoft Intune, such as Microsoft CRM operations, are running smoothly. The same applies to SAP and our Teams meetings. And I almost forgot our Cisco telephone system.
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.
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
