Microsoft Azure DevOps Reviews

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.

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.

We primarily use Azure DevOps for the early phase of software development projects. We don't use it for building the software. Rather, it is for development support. It handles management of the features, the composition, the definition of requirements, and checking our requirements against the use cases. 

Since it is a cloud product, it is constantly updated and not the responsibility of the user.

The quality of the user interface is very good.

It is a well-integrated product in terms of the development lifecycle. There are different functional areas from the requirements to finish including test management, product development, and deployment. I do not personally make use of all of these components together, but I understand from my colleagues that make wider use of it that everything integrates nicely.

It lacks integration with Office 365. It would be very useful if it had better integration with Microsoft Word because we would like to be able to define the priority requirement document and add it to different stages of the backlog. Currently, it is difficult to do this. There are some third-party products for this but they are either quite expensive or do not function properly.

I would like to see the requirement management links between work items improved.

An API to develop custom functions would be useful because we work with a large integrator that uses TFS, the on-premises version, and have seen what they do. One of the advantages of it is that you can develop using the XML approach to customization. Essentially, the customizability is more in-depth. This could be done, even without going to the code level, if they provided an API or and SDK. Although the interface currently used for customization is good, we sometimes find it limited. It would be more complex to use but also allow for greater potential.

I have been using Azure DevOps services for two years.

This is a stable service.

I would say that it is scalable. On a recent project, we had a lot of users and did not experience any issues in terms of performance.

I have only been in contact with technical support on one occasion and they gave me a good and prompt answer. From my experience, I can say that I am satisfied.

I do not personally have experience with other products, although the company has some experience with Jira.

In summary, this is a good product but I would like to see better Office integration and API support.

I would rate this solution an eight out of ten.

I am a consultant and this is one of the tools that I use to help develop solutions for my clients.

The most valuable feature is the complete integration between test cases, pipelines, and issue management.

The test management section needs to be improved. It is easy to use but they can make changes such that it is more comfortable for the users.

I would like to see a full-quality dashboard added. For example, if I am not using their pipeline then I would still like to see the dashboard available.

I have been using Azure DevOps for more than two years.

I have found it stable, so far.

This product is very scalable. I am currently using it for about 10 users and if I want to add more then I have to pay more money.

I have not yet been in a position where I needed technical support for this product. In the past, I have dealt with Microsoft's technical support for other products and I have found them to be fine.

I have also worked with similar tools such as GitLab, GitHub, Bitbucket, and then Jira.

Because I am a consultant, I work with multiple tools and the choice is that of my client.

I find that the pricing is good, and it is competitive with the other vendors in the market.

My advice to anybody who is considering Azure DevOps is that it is quite easy to onboard. It is a good product if you really want to work in a close-knit environment.

I would rate this solution an eight out of ten.

We are a software development company and we use DevOps practices to manage our application development lifecycle. This is our primary use case. We don't have a production environment for the applications that we develop. Rather, they are given to our customers when they are production-ready.

The management includes service requests, incidents, issues, etc.

The most valuable feature is that it brings order to our projects, and we know the status of each one at every moment.

This product would be improved if the helpdesk were included.

We are a small company and have not had any problems with scalability.

Technical support is good and we haven't had any problems with them.

We don't have any complaints about the pricing.

I would rate this solution a nine out of ten.

We normally use DevOps. On the application, everything has gone DevOps, however, we don't use the functions. All applications developed there have gone under Azure or AWS. We normally develop them to be able to not be dependent on anything, so if we want to deploy them in another environment, we can deploy them easily. If we want to use it in Azure, we use it in Azure. If we want AWS, we use it in AWS.

I like the CD pipeline. It's the most valuable feature for us. It's so easy to integrate into the CD/CI environment. I mostly love that one.

The initial setup is quick and easy.

The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code. 

If you want to use the DPR it's a bit harder due to the fact that it's only 30 days.

We've been using the solution for a year and a half at this point.

The stability of the product has been good so far. I can't say that I've witnessed glitches. There aren't bugs. It doesn't crash or freeze. It's reliable, as far as I can tell.

We don't have any issues with the scalability of the solution. If we need to, we're able to scale.

We've never contacted Microsoft for technical assistance. 

We are Microsoft partners. We have several Azure experts on our development team, and we have a tech that came from the US and did the training for us. We have a very strong understanding of the product and therefore we don't need help with troubleshooting or anything of that nature.

We also currently use AWS, however, I prefer Microsoft's solution as it's a bit easier to use overall.

We did not find the initial setup to be complex. The implementation is straight forward. 

Deployment is quick and typically only takes a few days or so.

We have ten people that handle maintenance. They are in different parts of the world. We have two in Australia, for example, and two in the USA.

The cost can get pretty high if you aren't paying attention to what you are doing.

We're partners with Microsoft.

I'd highly recommend Microsoft, and I recommend it more than any other solution. Everything is very simple and straightforward. The only worry for some organizations may be the cost. You need to be really, really careful.

I'd rate the solution overall nine out of ten. I think it's really, really great. If the functions were a bit better, I'd give it a full ten out of ten.

We use Azure DevOps for managing our workflow, as well as the CI/CD.

We use the CD/CD for all of our deployment lifecycles.

The CI/CD portal is very user-friendly.

The platform is very easy to manage. It is easy to manage repositories between the business users and corporate users.

Fields can be customized and the reporting is good. The APIs that are exposed can generate management reports.

The most valuable feature is the test manager. 

Integration is easy to do. The single-sign-on facility is there in every aspect including Azure DevOps, Active Directory, our portals, and all of our development sites.

Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves.

We would like to have an indicator of the percentage of occupancy. Suppose a person is working on two different domains, and we have 70% on one project with 30% on the other, it should be able to report that. As it is now, we have to manually enter that data. If this functionality were provided then it would make it easier for users.

We have been using Azure DevOps for the past two to two and a half years.

We have had issues, usually related to the APIs, but the support team has always helped us to resolve them.

The Microsoft support team is prompt to respond and very good.

The price is cheaper than Jira and some of the other competing tools.

Overall, this is a good product and if the Gantt chart and occupancy reporting features are added then it will be the most powerful one in this space.

I would rate this solution an eight out of ten

The key thing I find benefits me is the ability to track right from the feature and determine what has happened. I have a direct link to the test and the metrics that are available.

There are a lot of helpful features available for tracking dependencies.

The dashboard could be improved. Although there is flexibility in configuring it, there are some metrics that we have to configure ourselves. Improving the metrics that are readily available on the dashboard would be very helpful.

I would like to see better integration with third-party solutions, where if they are part of the DevOps pipeline then the reporting could be made available on the dashboard.

Having some form of check modeling integrated into Azure would be useful.

I have been using Azure DevOps for the past four years.

We have had no issues in terms of stability.

The offerings in terms of scalability are good.

We have not had to depend much on Microsoft support for DevOps and project management. However, I can say that the general support that we get for Azure is good.

I have some experience with Jira from Atlassian, although I have worked with Microsoft Team Foundation Server from the beginning.

The initial setup was straightforward. While we were migrating, we had training from Microsoft, which was helpful.

I haven't really looked into other options.

Overall, this is a good product and one that I recommend. The features it has have helped us, especially with tracking dependencies.

I would rate this solution an eight out of ten.