Microsoft Azure DevOps Review

Integrates will with Git and other Microsoft products and scales well

What is our primary use case?

In the first years, we had the solution, we did not use it for all of its models - not for the full life cycle. Now, within the past year or year and a half, we wanted to make the best out of it. We now use all the models and all the development lifecycle.

What is most valuable?

The product has integrated all the relevant models of task management requirements, source control, back management, test management, et cetera. You have a full ALM suite.

The connection to Git, which was bought by Microsoft, is also good. We use Git as a version control tool. 

Microsoft has good integration with its other products, such as Office, Teams, et cetera. 

The solution has proven itself to be very mature and robust. It's quite stable.

The scalability potential is very good. 

What needs improvement?

I'm not sure if "missing" is the right phrase, however, I am interested in, with all of these tools, if the connection to requirements management tools like DCRM, DOORS, et cetera, would be possible. That's a weak spot in most of the vendors.

We would like some bidirectional synchronization. It's the requirement if you want to analyze it to software requirements, et cetera. That's something that most of the tools aren't that good at.

For how long have I used the solution?

I've been using the solution for around three or four years at this point. It's been a while.

What do I think about the stability of the solution?

The product is mature and robust and quite stable. I haven't experienced any problems at all with it. It doesn't crash or freeze. It doesn't seem to have bugs or glitches that affect it. We have the support in-house on servers and we haven't had any problems with defining collections for example.

What do I think about the scalability of the solution?

It is my understanding that the solution is very stable. As an example, our organization has many teams and many departments and we use it across them all the time with no problem. We started using it originally when we had several teams, and now we have tens of teams, and it scaled up to meet our needs and we haven't had any issue with doing so.

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

We also use Jira. I myself do not use Jira, however, it is used by other teams and colleagues within our organization.

How was the initial setup?

I can't speak to the implementation process, as our IT handled it. I was not a part of the initial setup. I can't speak to if it was complex or straightforward, or how long it took to set up.

Which other solutions did I evaluate?

We are currently evaluating both Jira and DevOps against each other. We use both in several development units. Lately, I've been looking for some comparisons and reviews, and material regarding those platforms and the comparison between them. I'm wondering to myself whether it's good for our company to have both, or to choose one of them to be the standard platform of our company. That's the main subject that I'm interested in.

What other advice do I have?

We are customers and end-users. We don't have a business relationship with Microsoft.

I'm a manager, and therefore I don't personally use it on a daily basis anymore, however, I manage teams that work directly with the product.

I'd rate the solution at an eight out of ten. If I compare it against other products, it holds its own. It's quite a good solution overall and we've been happy with its capabilities.

I would recommend it to other organizations or companies. I'd advise them, however, to use the source control and to wisely choose which kind of collection they want to set up and configure. It's something very important that will set a company up for success. 

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
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: May 2021.
502,335 professionals have used our research since 2012.
Add a Comment