Microsoft Azure DevOps Reviews

Our only use case with DevOps was for integration with ReadyAPI.

The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests.

Something that could be improved is the initial setup with the integration of ReadyAPI.

I used this solution for six months.

Stability is fine. I was getting some errors, but that was due to my side of things.

Scalability is fine.

I would rate this solution 6 out of 10.

I did have some issues due to our organization, but it would be different for everyone. My advice is to reach out to support if you have any problems.

We provide this solution to our clients. The company we're currently assisting has had a lot of issues using Jenkins and decided to move the CI/CD pipelines to Azure DevOps. I'm a solution architect and we are partners with Microsoft. 

The solution offers great features including the project management feature and the Git-based repository. There is also the Azure pipelines and release artifact so you have all the functionality in one tool. It's also a relatively cheap solution.  

The only area that requires improvement is the interface. 

Stability is good. 

Scalability is good. 

The technical support is good.

The initial setup is easy. We had a team of three engineers dealing with implementation. 

Licensing costs are very reasonable compared to other solutions. It's a good price.

My only advice would be to go for the cloud version of DevOps, it's a better product. 

I rate the solution eight out of 10. 

We use Azure DevOps for the entire lifecycle of software development, starting with requirements analysis. After that, we use it to continue the process of development and deployment.

Azure DevOps is user-friendly. The UI and the UX are perfect. Their software covers the whole development cycle, from requirements analysis to deployment. In particular, it's helpful in the requirements analysis phase. You can apply your methodology or Agile framework from the beginning. After choosing the framework, like Agile or Scrum, Azure DevOps provides many features, like user stories, tasks, managing boards, and those kinds of things.

Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace. 

This makes up for any possible deficiency in Azure DevOps features. If you want some capability that Azure DevOps doesn't provide, you can develop your plugin or customize any part of it. The options for customization make it worthwhile for any software development.

Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it.

I've been working with DevOps for about five years.

DevOps is totally stable. And if there are any problems, Microsoft patches them as soon as possible.

When you enter into Microsoft ecosystem, you can scale any part of the product in this ecosystem. For example, you can connect Azure DevOps to Microsoft SharePoint for knowledge or document management. You can connect Azure DevOps to OneDrive for storage. You can connect it with Skype for chatting or Outlook. 

We don't use support from Microsoft. We mostly solve problems by searching for solutions on sites like GitHub and that kind of thing. 

I've used Atlassian products like Jira, Confluence, and HipChat, but I prefer Azure DevOps and the Microsoft ecosystem.

It is effortless to set up DevOps. All Microsoft products are user-friendly and easy to install. If you run into any obstacles, you can use Microsoft library or MSDN for any further help that you need. Microsoft provides a lot of wizards that you can use to solve your problem.

We use it for planning, pipeline management and testing, as well as using it as a CI/CD tool.

I like the agile management of projects, running stand-ups and the like. The pipeline management feature is great.  

We'd like to see an improvement in reporting across multiple projects. The same applies to improving program visibility so that project managers can get that pane of glass to assist with their work. It would be a big win for a lot of users as well as a good addition to the tool. 

We've been using this solution for close to four years. 

The solution is stable. There are still the occasional issues but on average it's very stable. 

The solution is easily scalable because it runs on the cloud and everything is managed by Microsoft. We don't do anything in terms of increasing capacity so when more users are added the increased capacity is automatically managed. 

We haven't made a lot of calls to technical support but when we have their response has been good and quick. 

We have a DevOps engineer who carried out the implementation for us and I believe it was relatively easy. 

I rate this solution eight out of 10.

We use Microsoft Azure DevOps for our source control, change request management, and a small amount of Wiki.

Microsoft Azure DevOps has helped our organization from having completely automated builds. The developers can send their own code to QA without needing a release manager or lead or IT person moving the code over.

The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow.

I have used Microsoft Azure DevOps for approximately one year.

Last week the builds did stop working for some unknown reason, and then started again. Most of the time the stability is fine, but there are occasions when there's a problem on Microsoft's side, where it creates problems for us.

The solution is scalable but you have to pay for it.

We have approximately 40 people using this solution consisting of developers, QAs, and product owners. We are extensively using this solution in our organization.

I wish the dashboards and the release process were integrated better. The use of Kanban dashboards could be a lot better. They don't have a Kanban dashboard. They have a dashboard with one sprint but it's not exactly the same as a Kanban dashboard. You are not able to do much with them. 

We have not needed to contact the support.

The installation is straightforward. We can create a whole new organization in less than a day.

We did the implementation ourselves. I do most of the maintenance but it is mostly maintenance-free.

There are additional costs for some functionality, such as increased scalability.

My advice to others is for them to do their research before implementing this solution.

I rate Microsoft Azure DevOps a seven out of ten.

We primarily use the solution for our internal development and we have some clients that require some consulting around some DevOps functionality.

We use the product for the development process for the repository, for the tracking of the tasks in the boards, and for the pipeline for CINCD.

The test plan is one feature that we are exploring more right now. This is a great feature that we want to deeper into.

We have a solid base. We can do everything with DevOps.

It is possible to add third-party extensions to increase the usability of the product.

The initial setup is very simple. 

We have found the solution to be scalable.

The solution, for the most part, is stable. 

Some things, like project management, tasks, progress, and having work progress views, require us to use some external tools or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps. They need to expand the solution's offering.

While I have used the solution for two years, the company has some personnel that have used it for longer. Our development team may have used it for four or five years. 

The product is stable. We had some regional degradations a few months ago, however, it wasn't too much. For the most part, it's reliable and there aren't bugs or glitches. 

The solution is scalable. If we need to expand it we can do so. 

We've never had to contact technical support. I cannot speak to how helpful or responsive they would be, as I've never dealt with them directly. 

The initial setup is very simple and straightforward. It is not difficult or complex. 

We use the online version. We don't have to deploy the tool. We don't have to put in a lot of effort as we already have the pipelines in the TFS. We just move it to Azure DevOps. 

I'm a solution provider. I sell Azure DevOps and I have a client that was looking to analyze some differences between Jira and Azure DevOps. Therefore, I have evaluated Jira a bit for them.

We are both a reseller and a partner of Microsoft.

We always use the latest version of the solution. 

I would recommend this product to other companies and users. If a company or a team doesn't know how to work with Azure DevOps, the advice I would give is to find someone that knows the tool and do a POC first to make sure you understand everything a bit better before diving right in. 

In general, I would rate the solution at an eight out of ten.

We use this solution for project management and delivery.

It is easy to use.

We are able to generate many different types of reports from Azure. It connects well to PowerBI. 

The performance is good.

They could have more reporting features added to the dashboard. There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps. 

We would like to have the same calculated reports that can be accessed in PowerBI, available in Microsoft Azure DevOps. 

We have been using Microsoft Azure DevOps for the last two and a half years.

Microsoft Azure DevOps is a stable product.

It is easy to scale. We have approximately 250 employees in our organization who use this solution.

We have contacted technical support. They provided us with a fast resolution.

We are using Azure, and TFS now. We are also planning to migrate to AWS as well.

The installation was easy.

We have an IT team of four to manage and deploy this solution.

I would definitely recommend this solution to others who are interested in using it.

I would rate Microsoft Azure DevOps an eight out of ten.

I work as a DevOps Engineer. I use this solution as an end-user.

I definitely like the pipelines and the ease of management once you're in an enterprise. 

The controlling security, the ease of access, the free plans, and the developer plans.

I also like the licensing structure in general.

I would like there to be more seamless integration with GitHub. 

Azure DevOps seems to be targeted towards enterprises and GitHub is the ugly sister, so to speak, that you come about in the enterprise. 

There is no real interaction between the products, which is a real shame since they are both developed by Microsoft. 

Definitely, there should be more integration between GitHub and Azure DevOps.

I have been working with Microsoft Azure DevOps for a couple of years, ever since they changed their name from Visual Studio Team Services.

Microsoft Azure DevOps is definitely stable.

I have experience with Azure Bicep and Paraform.

The initial setup is quite easy.

The licensing structure is good.

Definitely, I would recommend this solution. I would still look into your team goals and what tools you already know. 

GitHub is more community-driven, with more modules that are easy to access. 

Azure DevOps is more integrated with Azure as a platform, and that is important to consider when you consider DevOps in general or Azure DevOps.

I would rate this solution a seven out of ten.