Microsoft Azure DevOps Reviews

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.

I primarily use the solution for more of an end-to-end pipeline. 

The integration with the full end-to-end suite is great. The integration between the Kanban all the way through, including the traceability all the way through to the other end is very useful. You're able to test and you have your repositories and the ability to integrate with pipelines. 

There are great automation tools. 

The solution is very stable.

The scalability is quite good.

Individually, the components and not quite as good as others in the market. For example, the DevOps test plan isn't quite as good as a Micro Focus ALM QC. That said, when you integrate it into that entire pipeline, it's better.

Microsoft initiates changes so quickly, it's hard to keep up. It would be helpful if there was more documentation and more training to go with all of the changes. Chris:

With Microsoft, I would prefer to have more test plans. It's very difficult to find individual test plan module training.

The solution is quite stable. It's pretty reliable. there aren't bugs or glitches. It doesn't crash or freeze. 

The solution is very scalable. It's easy to expand.

I've had no problems with technical support, however, I'll get put in the fast-track programs. I always get very fast responses. 

I also use Micro Focus. For older style waterfall projects, it's best to go with Micro Focus probably, barring pricing and other consideration. However, in an agile environment, a Microsoft Azure-based product such as DevOps is great due to the pipeline and the whole integration end-to-end is just better.

I'm also familiar with Jira, which has better features in various areas. The problem is it moves so fast and new versions are always coming out and it can be hard to keep up.

I'm an implementor. I work with a variety of clients. 

I'd rate the solution at a nine out of ten. It's great for agile and we've been pretty happy with it as an end-to-end solution. 

If you're moving into an agile CI/CD, DevOps is the way to go. If you're still thinking about old manual start testing, Micro Focus is probably the way to go. That said, more standalone manual testing is better supported by Micro Focus.

Currently, we are using it for the continuous integration and continuous deployment of the CI/CD pipeline available for our projects.

The solution is very useful.

It's very easy to use and easy to navigate. It's a simple product to navigate.

The product is very stable; it's being used by quite a few organizations. We find it quite reliable.

The scalability, for now, is good for what we need. 

The installation is very straightforward.

We haven't had too much time to really play with the solution and therefore it's difficult to really know if there's anything missing in terms of features. We need more time with it.

The price could be lowered. It would be nice if it was cheaper.

I started using the solution a few months ago. It's been about a year or so. We have not used the product for that long just yet.

The product is quite stable. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable in terms of performance. 

The solution is scalable, at least for our purposes. We haven't run into any issues.

We have about 1,000 users on the solution currently.

The forums that are available to users are quite helpful and have a lot of information. It helps us troubleshoot very well. We don't usually call anyone directly.

We did not use a different solution before using this product.

The product is very straightforward to set up. 

The deployment is fast as well. It only took us about 10 to 15 minutes to have everything up and running. 

I handled the installation myself. I did not need the assistance of a consultant or integrator. It was handled in-house.

It would be nice if the licensing was a bit cheaper.

Our IT team looks after that aspect. I don't deal with tasks such as licensing and payments directly.

We did not evaluate other solutions before deciding on this product.

I'd rate the solution at an eight out of ten. So far, we've been very pleased with its capabilities.

The solution can be used for immutable infrastructure or for microservices.

The most valuable feature is the ease of use and performance.

There could more integration with other platforms.

I have been using this solution for approximately two years.

I have found the stability good.

We have approximately 20 people using the solution in my organization.

The technical support from Microsoft is really good.

We purchase the solution on an annual basis.

I have evaluated AWS.

I would recommend this solution.

I rate Microsoft Azure DevOps an eight out of ten.

We are using it for managing the teams and planning the screens and scope of work. We are also using it for building pipelines for automation of builds.

Monitoring is most valuable.

Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials.

It is stable.

Their technical support is pretty good.

Our IT department installs this solution.

Before using this solution, I would advise getting somebody who really knows how to use this solution and learning about how to do customizations based on your organization's needs.

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

I am using the solution to create continuous integration and deployment agents on the server environments. We are also involved in some projects where we create user stories and features created on the solution.

The most valuable features are continuous integration and deployment, and simplicity.

The active directory password system needs some improvement because many times the password for the active directory expires before the set time. Additionally, in the beginning, when I get the repository and check in my code on the dashboard to see who made changes, it shows that another user made the change that did not. This could be fixed in a future release.

 have been using the solution for three years.

The solution is stable.

I have found the scalability of the solution to be good.

I did not contact support but I was able to find all the information I needed on the internet.

The installation is straightforward.

There is a license for this solution.

I have experience with other solutions and with this one, you can add many addons without any difficult configuration. It has all the code and related items together, it is a total package.

I highly recommend this solution to others.

I rate Microsoft Azure DevOps a nine out of ten.

Broadly speaking, we use the product for .net websites, APIs, data integration, migration, data analysis, job orders, and workflows.

The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved. 

We have been using Microsoft Azure DevOps for more than seven years.

The product is easy to use and very stable.

The product is scalable.

We feel our experience with technical support to be straightforward. They have responded to our requests for help or support in good time and make themselves available for questions.

The installation of Microsoft Azure DevOps is straightforward. The steps are already in place and one only need follow them. We were able to handle this by ourselves.

The product is deployed to the cloud and we have five developers responsible for this. 

We are using the latest version of the product.

Our organization has five people who are using it. 

We plan to continue to use Microsoft Azure DevOps because our development or our environment is one of Microsoft's.

My advice to someone considering implementing the product is that it is good. I work in a Microsoft school so this is the environment with which everyone is acquainted.

I would rate this solution a nine out of ten.