Microsoft Azure DevOps Review

Good user interface, constantly updated, and the technical support is prompt


What is our primary use case?

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. 

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Azure DevOps services for two years.

What do I think about the stability of the solution?

This is a stable service.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
**Disclosure: My company has a business relationship with this vendor other than being a customer: partner
More Microsoft Azure DevOps reviews from users
...who work at a Energy/Utilities Company
...who compared it with JIRA Portfolio
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
522,281 professionals have used our research since 2012.
Add a Comment
ITCS user
Guest