Microsoft Azure DevOps Review

Helpful in tracking issues and works extremely well in terms of the build time, but it is complicated and should provide the ability to write your own scripts


What is our primary use case?

We are using it for the source-code repository, automated bill process, very limited automated testing, and tracking trouble tickets or feature requests. We are using its latest version.

What is most valuable?

The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason.

What needs improvement?

They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server.

I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script.

For how long have I used the solution?

I have been using this solution for a total of four years.

What do I think about the stability of the solution?

From what we've used it for so far, I have not seen any problems.

What do I think about the scalability of the solution?

We're using perhaps 10% of what it is capable of doing. It is far more capable than what we are using right now. With further experimentation and training, I'll probably go from 10% utilization of its capabilities to about 50% or 60% in the next couple of months. We'll never use 100% of what it is capable of doing, but it should handle 95% of everything we need to do. We can always write our own plugins to handle the side things that we need.

Scalability is not really applicable with the code that we write, but the build times and things like that typically take under 15 seconds before we get our responses back. So, it works extremely well.

In terms of the number of users, there are six of us who are software developers. Some of the managers might also partially use the reporting capabilities.

How are customer service and technical support?

I haven't called them up.

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

I've used JIRA and a number of different systems going back almost 20 years. We were doing our development using Microsoft tools, and it just made sense to use what they integrate with. Azure DevOps is the perfect environment because we're using Microsoft technology for other stuff. It is always going to have slight favoritism towards the other Microsoft tools.

How was the initial setup?

The basic setup works very quickly, but there are so many things and options.

What about the implementation team?

We did it ourselves, which is one of the problems. We don't know what we're doing.

What's my experience with pricing, setup cost, and licensing?

I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees.

What other advice do I have?

It is a really complicated product. All DevOps stuff is complicated. The advice that I would give to anybody doing DevOps is to have a goal in mind of what you want to do. Then the product will do what you wanted it to do. 

I would rate Microsoft Azure DevOps a four out of ten because I don't know it enough to rate it.

Which deployment model are you using for this solution?

Private Cloud

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

Microsoft Azure
**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: April 2021.
476,163 professionals have used our research since 2012.
Add a Comment
Guest