We changed our name from IT Central Station: Here's why
Software Architect at a mining and metals company with 10,001+ employees
Real User
Compatible with our entire ecosystem
Pros and Cons
  • "It's got something that you won't find in other products."
  • "With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem."

What is our primary use case?

We use Microsoft Azure DevOps for application lifecycle management, including source control-related things, pipelines, and also for work item management. In short, the whole ecosystem.

Within our organization, there are roughly one thousand core developers using this solution. We also have stakeholders, product vendors, Scrum masters, testers, and manual testers. 

What is most valuable?

Mainly the source code solutions and the pipelines. Work item management and the manual test I/O. Test automation, end-to-end testing, and the manual test experience. It's got something that you won't find in other products. The work item management is good enough for small to medium-sized teams, and for large projects with plenty of teams collaborating with each other.

We can achieve the boundaries of the system. Potentially, we could do it with other tools like Jira. Still, with Microsoft Azure DevOps, we can manage everything.

What needs improvement?

Currently, if you would like to use the full-set of customization features, for example, the process templates, the HL process, or the Scrum process, if you start from scratch right now, you'll have these options. But if you've been working for several years in an established ecosystem, then you're based on an old-fashioned way of working and you won't be able to use the recent customization features.

There are options to get around this, especially if you move to the cloud or if you copy things and migrate them, but that's a huge amount of work. It's best if you start from scratch in a new project — in a new environment. With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem.

For how long have I used the solution?

We have been using this solution for roughly 10 years. 

What do I think about the stability of the solution?

This solution is stable. I don't have anything negative to report. 

What do I think about the scalability of the solution?

Microsoft Azure DevOps is very scalable. It uses techniques from Microsoft itself, so if you have the knowledge of how to deal with that, you can scale it up and out as you wish.

How are customer service and technical support?

Technical support is good. We have had a few cases where we needed support and they contacted us immediately. There was a willingness to find a solution and determine if there was a bug or if it was an oversight. We have a good relationship with Mircosoft support.

How was the initial setup?

The initial setup is easy.

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

Most of our developers have an MSDN license which is linked to the Visual Studio development environment. 

We also have a corporate license for other products like Windows Server — it's all included in one package. An additional license is not required for the on-premise solution. If you go to the cloud, it's a different story. Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs.

What other advice do I have?

Overall, on a scale from one to ten, I would give this solution a rating of eight. 

It could be a little bit more flexible in terms of work item management. Apart from that, I can't really think of many features that are missing. It supports all kinds of ecosystems; there are a lot of possibilities when it comes to interacting with other ecosystems. 

Try to follow the market standards. There's a whole huge community that supports it. The market is evolving very fast. Microsoft is acquiring other companies. They recently bought GitHub. It's hard to say which solution will survive — DevOps or GitHub. That may be an issue in the future. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Wilson  Gonzalez
DevOps Manager at a tech services company with 51-200 employees
Real User
Top 20
A DevOps solution with a great pipeline feature
Pros and Cons
  • "Everything that's related to the pipeline has been very good."
  • "I'd like to have something better for the test plan."

What is our primary use case?

We use Microsoft Azure DevOps to store our code, manage our code, and publish it.

How has it helped my organization?

Before we used Azure DevOps, our team used to promote the code manually. What they did was publish, copy the files and paste them on the server or run lines of code to get our services in production. That takes a lot of time. With the pipeline we're using, that time was reduced by ten times. We're ten times faster now.

What is most valuable?

Everything that's related to the pipeline has been very good. We're using this to promote our code and to secure it. The library and all the stuff that we can manage inside the pipeline is helping us a lot.

What needs improvement?

I'd like to have something better for the test plan. The test plan seems to be really manual even now. There's a lot of stuff to do there, and it could be improved. 

Sometimes, it's also difficult for us to handle all the connections with iOS. iOS connections are really very difficult. We're using a different product, which is part of Microsoft, called App Center. But sharing from Azure DevOps to App Center has been difficult. They should try to improve things related to iOS development or iOS production.

For how long have I used the solution?

I've been using Microsoft Azure DevOps for the last five years.

What do I think about the stability of the solution?

I wouldn't complain about stability. Sometimes we have a couple of maintenance windows, which is okay. We actually had a couple of problems, but I don't remember. I would say that it's under normal standards. I wouldn't complain about it.

What do I think about the scalability of the solution?

Microsoft Azure DevOps is scalable. It was easy to grow.

How are customer service and technical support?

If I ever raised any kind of a question to technical support, it was pretty good. I have asked a couple of questions in the technical area. They helped me, and it was good and pretty fast.

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

We used to use another solution, but I don't remember which one. We switched because of a big contract that our company had with Azure. We were going to have our servers with Azure, and it looked like they reviewed the pricing and made the change.

How was the initial setup?

The initial setup was really easy. I didn't even manage this before, but I'm the one who is running this now, and it's pretty easy. Something that made me a little bit confused was all the permissions you have to give to teams and people. Sometimes it's kind of tricky, but it's understandable.

Lately, the deployment's taking a little bit longer than before. I don't know what happened. I'll say that before our deployments took us maybe a couple of minutes. I didn't even measure that, but now it sometimes takes up to 40 minutes or an average of 30 minutes for each deployment.

What about the implementation team?

I implemented Microsoft Azure DevOps by myself.

What other advice do I have?

I would advise potential Microsoft Azure DevOps users to start exploring the free options, which are pretty good. I use it myself as an independent. As soon as you start using it, you'll know that you have to pay because it's a good tool that we can have to manage our code.

On a scale from one to ten, I would give Microsoft Azure DevOps an nine.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,208 professionals have used our research since 2012.
Manager Systems Engineering at a manufacturing company with 10,001+ employees
Real User
Helps to improve productivity but specific disciplines need to be addressed
Pros and Cons
  • "We can eliminate some of the middleman processes."
  • "It should be able to handle the different types. There is ecosystems engineering, and there is software applications engineering. There is a need to bring these teams together, but the disciplines don't integrate very well, and so it won't work."

What is our primary use case?

We use Azure DevOps to place our corporate servers into the cloud. We perform evaluations in the cloud for clients. Occasionally, we provide a hybrid solution in a specific cloud. For corporate work, we usually use a different cloud. With Microsoft Azure DevOps, as with any DevOps, it is not always possible to identify specific use cases. How do you identify a specific feature from a hundred requirements into a specific use case? It is very easy to lose detail. Traditional teams and ways of working methodically for safety-critical systems are not always prepared to handle that. It is important to be able to handle hundreds of detail-oriented requirements.

How has it helped my organization?

Azure DevOps is now used for safety-critical systems, whereas in the past the traditional approaches were used in requirements management. This is more like the traditional waterfall model. Improvement is always unique to productivity. That's why we switched to Microsoft Azure DevOps. The software teams prefer it to IBM.

What is most valuable?

We can eliminate some of the middleman processes. In the process, we are merging DevOps with development and operations. So developers act like our operation team as well. That concept is a great exchange. It brings a high level of visibility. It helps the team and department cohesion, which helps to improve productivity. 

It also includes a high level of traceability and elimination of some of the unwanted silos in productivity. Testing and transparency need to be defined within the boundaries. If a backlog occurs, you should be able to group them as a whole. This means there is a backlogging to the team, as opposed to individual areas. Each area needs to be visible to other areas, at all times.

What needs improvement?

Microsoft needs to consider ruggedization and addressing specific disciplines. Fundamentally what I mean by that is you cannot merge everything. It should be able to handle the different types. There is ecosystems engineering, and there is software applications engineering. There is a need to bring these teams together, but the disciplines don't integrate very well, and so it won't work. For example, there is expertise in an area, and they tend to view the project from their own perspective. 

For example, the software UI/ UX team needs to view it from the UX perspective. Application engineers need to view it from the application viewpoint and the engineering perspective is different again. Although we need to be cohesive in our approach, we need to keep some boundaries as well. The idea of containers arises, such as those provided by the open source software product Kubernetes. We need to containerize different disciplines and then merge them. As a manager, I should be able to ask the formative team to focus on their creative section, and that their task is completed. In the Application layer, you also focus on their requirements and you establish traceability. Other teams may also be involved in linking to the overall requirements.

For how long have I used the solution?

I have been using Azure DevOps for one year. It has been used in the company for about two years. It is used in the cloud and on-premises, as a hybrid cloud solution.

What about the implementation team?

We implemented on-premise as a hybrid solution, and on the cloud.

What other advice do I have?

I would give Microsoft Azure DevOps a six out of 10. Microsoft Azure DevOps is not perfected yet, as it needs to be more user friendly. If it can achieve that it will eventually reach a 10.

Which deployment model are you using for this solution?

Hybrid 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.
Anthony Gregg
Technical Engineer (Retail Group) at a retailer with 10,001+ employees
MSP
Top 5Leaderboard
A comprehensive, easy-to-use, stable, and well-integrated solution that does everything in the development life cycle
Pros and Cons
  • "All features are good. Pipelines feature is great, and Boards and Artifacts features are also really good. It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It is very easy. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated."
  • "The administrative capabilities of the tool need a huge improvement. Its Wiki and reporting also need a lot of improvement. Their support can also be better."

What is our primary use case?

It is used for development and life cycle management within the company. We use the SaaS version. It is called Azure DevOps services.

How has it helped my organization?

It has absolutely improved the way our organization functions from a development lifecycle point of view. It has enabled teams to be more Agile and flexible.

What is most valuable?

All features are good. Pipelines module is comprehensive, Boards and Artifacts modules are also really extensive.

It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It has a easy to use UI. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated.

What needs improvement?

The administrative capabilities of the tool need a huge improvement. Its Wiki and Reporting functions also need a lot of improvement. Their support can also be better.

For how long have I used the solution?

I have been using it ever since it was created in 2012

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

It is very scalable because it is on the cloud. We have a very large user base and they're all IT-related. The users are engineers, product managers, and management. It is the entire IT organization.

How are customer service and technical support?

We use their technical support a lot. We have internal support, but we will also reach out to Microsoft to resolve problems. Their support is very good, but there is always room for improvement. It depends on the subject area. Sometimes, they have people who are not as well versed as others.

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

We've been pretty much on the Microsoft products. We used to use Team Foundation Server, which was a Microsoft product. Before that, it used to be Visual Source Safe. We also used to be on PVCS, SVN and CVS.

How was the initial setup?

Being a SaaS solution, there is no setup.

What about the implementation team?

It was implemented in-house as we have a high level of in-house expertise in the ALM space.

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

This area is very different for each and every organization and I would recommend that they research cost and pricing for their situation.

Which other solutions did I evaluate?

No, we did not evaluate any other options since we are heavily tied to the Microsoft stack. However over time, we have adopted other platforms (Java, Node, Python and others) since Azure DevOps is cross platform compatible with Linux, Windows, iOS and Andriod.

What other advice do I have?

If you're looking for a cross-platform solution that end-to-end does everything in the development life cycle, this would be a very good solution for you. If you're looking for a more siloed product that is specifically focused on one particular area of the lifecycle, this is definitely still an option, but you should also evaluate other options as well (Atlassian, IBM Rational,  MIcro Focus ALM, GitHub etc) for completeness.

I would rate Microsoft Azure DevOps a solid eight out of ten. It is really good at what it does, but it also has some solid areas of improvement that are needed. Once they have addressed those, it could be hard to beat.

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?

Disclosure: I am a real user, and this review is based on my own experience and opinions.
CTO at Southernsoft Technologies
Real User
Top 20
Intuitive and easy to use with good stability
Pros and Cons
  • "The one thing that really stands out to me is how you can filter and how you can do your reporting and filter the tasks and everything by user."
  • "We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."

What is our primary use case?

I primarily use the solution on projects often. We use it for our Git repository and the CI/CD.

What is most valuable?

I love how easy the solution is to use. It’s intuitive. I don’t need to reference a manual. Everything is just very naturally laid out.

You can link your tasks and assign people. To me, it just makes sense. The user experience is excellent.

I like the Kanban tasks and their various features. It’s all very straightforward.

The one thing that really stands out to me is how you can filter and how you can do your reporting and filter the tasks and everything by user. Every time I try to do that in Jira, for example, it's a pain.

The stability of the product is quite good.

What needs improvement?

I’m not sure what needs improvement. I don't even think I'm using everything. There are still a lot of things on the testing side that I'm not using. That said, there's, there's a lot that it can do. I wouldn't even know where to get started on discussing what it needs or lacks.

We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up.

For how long have I used the solution?

I’ve been using the solution for about four years now. It’s been a while.

What do I think about the stability of the solution?

For the most part, the stability is very good. There was one time there was a bit of a performance issue, however, it was just due to the fact that the project manager was overwhelmed. It slowed down and got laggy. We put everything on one story, one epic, and we realized we needed to split it up.

What do I think about the scalability of the solution?

The product can scale. With the projects that I work on I just pick up Azure DevOps. It just makes sense. Everything from the beginning, for example, how the story starts right up to how it gets deployed and everything, is well laid out and you can adjust as needed.

On the project that I'm doing right now, maybe have a team of ten. On other projects, for example, at my previous company, we had a hundred devs or so using it.

How are customer service and support?

Technical support has been very good. We used to call Microsoft and they would help us. They gave great support. We’re quite happy with their responsiveness and level of knowledge.

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

I also use Jira alongside Azure DevOps. I use both of them.

I find DevOps easier to use and better laid out. I find Jira difficult and confusing.

How was the initial setup?

The initial setup is pretty straightforward.

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

I can’t speak to the exact pricing. It’s not an aspect of the product I deal with.

What other advice do I have?

We’re a customer and an end-user.

I’m a big fan of DevOps. It’s a good project and I haven’t seen anything else like it.

As we’re on the cloud deployment of the solution, we’re always on the latest version.

I’d advise new users, if they are a Microsoft shop, to choose DevOps over Jira. It just makes more sense.

I’d rate the solution at a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Cloud Solution Architect at a tech services company with 201-500 employees
Reseller
Easy to set up, allows for third-party extensions, and is pretty scalable
Pros and Cons
  • "It is possible to add third-party extensions to increase the usability of the product."
  • "Some things like project management, tasks, progress, and having work progress views require us to use some external tools, or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps."

What is our primary use case?

We primarily use the solution for our internal development and we have some clients that require some consulting around some DevOps functionality.

We use the product for the development process for the repository, for the tracking of the tasks in the boards, and for the pipeline for CINCD.

What is most valuable?

The test plan is one feature that we are exploring more right now. This is a great feature that we want to deeper into.

We have a solid base. We can do everything with DevOps.

It is possible to add third-party extensions to increase the usability of the product.

The initial setup is very simple. 

We have found the solution to be scalable.

The solution, for the most part, is stable. 

What needs improvement?

Some things, like project management, tasks, progress, and having work progress views, require us to use some external tools or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps. They need to expand the solution's offering.

For how long have I used the solution?

While I have used the solution for two years, the company has some personnel that have used it for longer. Our development team may have used it for four or five years. 

What do I think about the stability of the solution?

The product is stable. We had some regional degradations a few months ago, however, it wasn't too much. For the most part, it's reliable and there aren't bugs or glitches. 

What do I think about the scalability of the solution?

The solution is scalable. If we need to expand it we can do so. 

How are customer service and support?

We've never had to contact technical support. I cannot speak to how helpful or responsive they would be, as I've never dealt with them directly. 

How was the initial setup?

The initial setup is very simple and straightforward. It is not difficult or complex. 

We use the online version. We don't have to deploy the tool. We don't have to put in a lot of effort as we already have the pipelines in the TFS. We just move it to Azure DevOps. 

Which other solutions did I evaluate?

I'm a solution provider. I sell Azure DevOps and I have a client that was looking to analyze some differences between Jira and Azure DevOps. Therefore, I have evaluated Jira a bit for them.

What other advice do I have?

We are both a reseller and a partner of Microsoft.

We always use the latest version of the solution. 

I would recommend this product to other companies and users. If a company or a team doesn't know how to work with Azure DevOps, the advice I would give is to find someone that knows the tool and do a POC first to make sure you understand everything a bit better before diving right in. 

In general, I would rate the solution at 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:
Flag as inappropriate
Director at a computer software company with 10,001+ employees
Real User
Top 5
Easy to comprehend and easy to use but the pricing should be easier to manage
Pros and Cons
  • "The simplicity is very good and the customer experience is also great."
  • "It should be easier to manage Licenses especially because it's in the cloud."

What is our primary use case?

My team uses this solution for the CI/CD deployment, and code check-ins.

We are also using Azure Boards for tracking our work, all of the requirements, the backlogs the sprints, and the release planning.

What is most valuable?

What I like the most is that it is easy to comprehend, and it's easy to use.

The simplicity is very good and the customer experience is also great.

What needs improvement?

I am not suggesting this solution should be cheaper. I would like to see a bucket of licenses. for example, 10 licenses or 100 licenses that could be monitored to know how many of those licenses have been used. The price would be deducted accordingly.

I should not have to contact Microsoft daily to request a license or two. There should be a mechanism in place where you are able to find out where you are out of 100 licenses, or that you have used 90 licenses in that year.

I should be given a credit line of 10 licenses at the end of the year or at the end of the month.

It should be easier to manage licenses, especially because it's in the cloud. You should know the usage and based on the usage, you should be able to make decisions.

For how long have I used the solution?

I have been using Microsoft Azure DevOps for one year.

We are using the latest version.

What do I think about the stability of the solution?

It's a stable product. I have not experienced any issues.

What do I think about the scalability of the solution?

This is an area that has yet to be explored fully. We haven't taken it to this level.

We are a team of 25 to 30 members, which is fine for us. Every time we scale up we need a new license and that takes time, it's not just a click and it's done.

I don't know if it will be scalable for 200 to 300 people.

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

Previously, I was working with Jira.

How was the initial setup?

I was not involved in the installation. My team completed it.

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

Price is an area that could be improved. There are products on the market with a fixed price of 50 or 100 people, you are a bucket price. 

With Azure, you have to pay for every user.

It's good to have a bucket such as 50 to 100, or 100 to 200, and flexible pricing.

The issue may be from having more than one license. When you procure one license or two licenses, it becomes difficult.

It should be easier to procure a license, it should not be one by one. We don't know how many members I will have on my team three months from now.

What other advice do I have?

We plan to continue using this solution.

I would recommend this solution, but I would not know their business needs.

Based on the various features, the deployments, licensing, pricing, and the customer experience, I would rate Microsoft Azure DevOps a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Hamid Nia
Software Architect at EML
Real User
Top 20
Easy to implement, good CD pipeline, and very stable
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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

How are customer service and technical support?

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.

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

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

How was the initial setup?

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.

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

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

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros sharing their opinions.