Microsoft Azure DevOps Reviews

We are a reseller of solutions and provide maintenance to our customers. Azure DevOps is one of the products that we have experience with.

Our customers use this product when they want to enter the DevOps space and integrate or consolidate all of their existing tools. It allows them to communicate seamlessly between development, their operations, and other team members.

This platform provides a large span of tools and technologies.

I would like to see better integration and collaboration between tools. There are different companies offering different tools, and how well something is integrated contributes to the completeness of the solution. 

The platform needs to be updated because things are still in the process of change.

I have been working with Microsoft Azure DevOps for almost three years.

We have had no complaints about stability.

Scalability has not been a problem.

We have not been in contact with technical support.

The initial setup is complex. It really depends on those who are using it in the company and exactly what they're utilizing with respect to tools. It also depends on whether they want to integrate it.

We have an in-house team for deployment.

The price of this solution is fair.

There are a lot of different tools on the market such as Jira, so I would look at DevOps as one option and how it is going to handle things in your environment.

I would rate this solution a six out of ten.

We are a small product team and we do software development. I'm part of the testing team and I use Azure DevOps to manage all of my test activities. This includes my test plan, where I create my test cases, write test scripts, execute them, and publish the results using the dashboards.

I like a lot of the features in Azure DevOps.

The creation of test plans is valuable and I like the reporting features that it offers. For example, I like the charts, as well as reporting progress.

The interface is user-friendly.

I have not been able to use the integration with automation features, such as test management automation, with a framework that is written in Java. Currently, Azure offers frameworks that are written in C#. I have not found anything in the Microsoft documentation to say that it supports other languages.

I have been using Microsoft Azure DevOps for approximately two years.

Being a SaaS product, sometimes we experience hangs. However, that is okay because in general, it is very much stable. If there are any outages then I get prior notification of such events.

I have not tried scaling it. In my team, we have approximately 30 people who are using it.

For me, the first point of contact is my internal organization and not Microsoft directly. However, if there are any changes that require Microsoft's intervention then there is an intermediate team who coordinates it. The response has been pretty good and I am happy with the support.

I have used several tools in the past including Zephyr and the Rational Quality Manager.

The initial setup is pretty straightforward. We needed to set up a Microsoft account, and that gives access to the projects. Basically, the IT department or IT administrators take care of the access.

As a member of the team, once access is provided, I can just start using it. It is plug-and-play, as far as I'm concerned.

It is a subscription model and I only pay for what I use.

Very recently, I was doing comparative studies of available test management solutions on the market and I find Azure DevOps to be pretty good.

Overall, this is a good product and I recommend it.

I would rate this solution an eight out of ten.

The company that we were working with was in development using a Microsoft platform. We used Azure to integrate the complete project management and DevOps work.

This solution works with other Microsoft solutions pretty easily. It was easy to integrate everything into all the other tools that we were using. It integrates very seamlessly.

I have not come across information for integrating this solution with others, such as ServiceNow. I am not sure if the integration would be straightforward to implement. There should be readily available information to accomplish these integrations.

I have been using the solution for approximately two years.

The project that we were using the solution for was a small implementation, I cannot fully comment on how scalable it is. I did not have enough data to comment if it was good. However, we did not have any issues.

The customer support is good.

The installation time of this solution depends on the environment it is being implemented in. We had a couple of projects that took around two weeks of implementation. This included the whole integration of the DevOps and everything together.

We had an expert that did the implementation of the solution for us. He did not face any problems.

There is a license for this solution.

We plan to continue offering this product to our customers and I would recommend it.

I rate Microsoft Azure DevOps a seven out of ten.

We are using this solution for workflow management, especially when using a Kanban board to monitor the small assignments. Also, some programming for some of the disciplines. It's still in its infant stages.

It's a complete solution that has everything you need. 

It covers all of the development workflows to the initial planning, testing, coding, and even to launch the subsequent feedbacks.

Also, it has marketing reports.

It's very promising. They are very well positioned to take over some pretty heavy contestants in that area.

I think that they have some menus there that are not very well placed. For example, I was searching for some extensions in the marketplace and I couldn't find my way back to the console. It's not very well designed.

The general user interface is nice. It's intuitive, but I had the luck to discover something that is not very well designed. The fact that I can't return back to the console is very strange. I couldn't find my way back. I had to log off and log on again and get back to the console in a very awkward way.

I have been using this solution for a few weeks.

We are using the latest version.

It's a stable solution.

As per the documentation that I have read, it's pretty scalable. My brother, who works with this solution practically every day, says it's scalable.

We plan to continue using this solution.

I have not yet had any experience with technical support.

Previously, I just used GitHub, so just Version Control for code and not much more. 

I used also their integrated development environments including Visual Studio Code and Visual Studio. These solutions are built by Microsoft.

It's straightforward. With the cloud solution, there is no installation.

I could create the main console for the project very quickly, with just a name and description and the rest is the default.

This is a product that I can recommend to other users.

I would rate this solution an eight out of ten.

All of the features related to release management are very good. We use release management and dev management, and the dashboard is good. The ability to specify multiple platforms in release management, by using Docker, is valuable.

Better integration with the Linux operating system would be an improvement for this solution.

I would like to see more third-party plugins; by comparison, the open source solution, Jenkins, has thousands of plugins available.

The Wiki for this solution is not very good.

There is a problem when you want to run a release pipeline for an organization that needs enhanced security. There is no option to configure a dynamic login for a station that is running the tests. The only solution in the platform is to configure an agent that uses a fixed username and password login. There is no option to change the username or password for the login dynamically. If I want to run multiple tests, with different users, then I cannot do it. When it comes to running tests, it needs an option to use different users or authentications. This is a very important feature that is missing.

This solution is very stable.

Scalability is not particularly relevant. It depends on what kind of scaling you want to do. Generally, it has very good support for scaling.

There are hundreds of developers using this solution.

We only had one issue, and I would rate their technical support at medium, based on that experience. The issue was related to shrinking a database, where it was not working well. It took a long time for Microsoft support to fix the problem.

We did not use another solution prior to this one. However, I use other tools in conjunction with Azure DevOps. One of these is Jenkins, for CICD, and I also use the Atlassian Suite.

The initial setup for the latest version was very straightforward. The upgrade was quick and lightweight.

I handled the implementation on my own.

This is a solution that I would recommend.

Azure DevOps is a leading platform, but some things can be better. 

I would rate this solution a seven out of ten.

As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there.

Apart from that, the reporting structure could be provided as well. Depending on how the company is using the technology, there may be other Microsoft tools that are better so that the integration and reporting will be easier.

I've been using Microsoft Azure DevOps for almost five or six years.

It is stable, and we have had no issues with it.

It is scalable.

I would rate this solution at eight on a scale from one to ten.

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.

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.