Likelihood to Recommend Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Read full review They're great to embed logic and code in a medium-small, cloud-native application, but they can become quite limiting for complex, enterprise applications.
Read full review Pros Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project. Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts. Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing. Read full review They natively integrate with many triggers from other Azure services, like Blob Storage or Event Grid, which is super handy when creating cloud-native applications on Azure (data wrangling pipelines, business process automation, data ingestion for IoT, ...) They natively support many common languages and frameworks, which makes them easily approachable by teams with a diverse background They are cheap solutions for low-usage or "seasonal" applications that exhibits a recurring usage/non-usage pattern (batch processing, montly reports, ...) Read full review Cons Can add more build templates for specific technology requirements Can have more features in dashboards which can help dev teams stream line their tasks and priorities Can have raise alarm feature in case of any sort of failure in devops pipeline execution Read full review My biggest complaint is that they promote a development model that tightly couples the infrastructure with the app logic. This can be fine in many scenarios, but it can take some time to build the right abstractions if you want to decouple you application from this deployment model. This is true at least using .NET functions. In some points, they "leak" their abstraction and - from what I understood - they're actually based on the App Service/Web App "WebJob SDK" infrastructure. This makes sense, since they also share some legacy behavior from their ancestor. For larger projects, their mixing of logic, code and infrastructure can become difficult to manage. In these situations, good App Services or brand new Container Apps could be a better fit. Read full review Likelihood to Renew Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Read full review Usability Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
Read full review Support Rating I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
Read full review Implementation Rating Do research beforehand and, if possible, do a trial run before implementing into production environment.
Read full review Alternatives Considered In my opinion, DevOps covers the development process end to end way better than
Jira or
GitHub . Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
Read full review This is the most straightforward and easy-to-implement server less solution. App Service is great, but it's designed for websites, and it cannot scale automatically as easily as Azure Functions. Container Apps is a robust and scalable choice, but they need much more planning, development and general work to implement. Container Instances are the same as Container Apps, but they are extremely more limited in termos of capacity.
Kubernetes Service si the classic pod container on Azure, but it requires highly skilled professional, and there are not many scenario where it should be used, especially in smaller teams.
Read full review Return on Investment It has streamlined the pipeline and project management for our agile effort. It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise. The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization. Read full review They allowed me to create solutions with low TCO for the customer, which loves the result and the low price, that helped me create solutions for more clients in less time. You can save up to 100% of your compute bill, if you stay under a certain tenant conditions. Read full review ScreenShots