Microsoft Azure DevOps Reviews

I work as a DevOps Engineer. I use this solution as an end-user.

I definitely like the pipelines and the ease of management once you're in an enterprise. 

The controlling security, the ease of access, the free plans, and the developer plans.

I also like the licensing structure in general.

I would like there to be more seamless integration with GitHub. 

Azure DevOps seems to be targeted towards enterprises and GitHub is the ugly sister, so to speak, that you come about in the enterprise. 

There is no real interaction between the products, which is a real shame since they are both developed by Microsoft. 

Definitely, there should be more integration between GitHub and Azure DevOps.

I have been working with Microsoft Azure DevOps for a couple of years, ever since they changed their name from Visual Studio Team Services.

Microsoft Azure DevOps is definitely stable.

I have experience with Azure Bicep and Paraform.

The initial setup is quite easy.

The licensing structure is good.

Definitely, I would recommend this solution. I would still look into your team goals and what tools you already know. 

GitHub is more community-driven, with more modules that are easy to access. 

Azure DevOps is more integrated with Azure as a platform, and that is important to consider when you consider DevOps in general or Azure DevOps.

I would rate this solution a seven out of ten.

We are using it for managing the teams and planning the screens and scope of work. We are also using it for building pipelines for automation of builds.

Monitoring is most valuable.

Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials.

It is stable.

Their technical support is pretty good.

Our IT department installs this solution.

Before using this solution, I would advise getting somebody who really knows how to use this solution and learning about how to do customizations based on your organization's needs.

I would rate Microsoft Azure DevOps an eight out of ten.

Broadly speaking, we use the product for .net websites, APIs, data integration, migration, data analysis, job orders, and workflows.

The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved. 

We have been using Microsoft Azure DevOps for more than seven years.

The product is easy to use and very stable.

The product is scalable.

We feel our experience with technical support to be straightforward. They have responded to our requests for help or support in good time and make themselves available for questions.

The installation of Microsoft Azure DevOps is straightforward. The steps are already in place and one only need follow them. We were able to handle this by ourselves.

The product is deployed to the cloud and we have five developers responsible for this. 

We are using the latest version of the product.

Our organization has five people who are using it. 

We plan to continue to use Microsoft Azure DevOps because our development or our environment is one of Microsoft's.

My advice to someone considering implementing the product is that it is good. I work in a Microsoft school so this is the environment with which everyone is acquainted.

I would rate this solution a nine out of ten. 

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

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.

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.

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.

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

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.

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

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.

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.

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.

I implemented Microsoft Azure DevOps by myself.

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.

The solution can be used for immutable infrastructure or for microservices.

The most valuable feature is the ease of use and performance.

There could more integration with other platforms.

I have been using this solution for approximately two years.

I have found the stability good.

We have approximately 20 people using the solution in my organization.

The technical support from Microsoft is really good.

We purchase the solution on an annual basis.

I have evaluated AWS.

I would recommend this solution.

I rate Microsoft Azure DevOps an eight out of ten.

I'm using it for specifications of the requirements, for example, or a user for research specifications. I'm also using it to build up test cases right now.

Overall, the solution is pretty good. It fulfills most of our requirements.

The stories and test cases on offer are great.

The initial setup was pretty self-explanatory. It was straightforward.

The pricing seems to be reasonable.

The solution needs to add the capability for building live documents. 

I would like to see a bit more project tracking. There should be more Kanban views. There maybe should be a few more reports. If the reporting was increased a bit, it would make it so that you can check a bit more information around the progress of the project. That would help with project management and progression. 

I've been using the solution about twice a week for the last few months. It hasn't been that long and it's not a daily occurrence. In total, it's maybe only been two or three months.

So far, I've found the solution to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable.

We have about 3 people using the product currently in my company, and about 30 customers.

I've never had to contact technical support. We haven't faced any issues that would require us to. Therefore, I have not idea how they would be. I can't speak to how knowledgeable or responsive they are. At this point, I have no insights to share.

I have worked with other DevOps tools previously. I've worked with Jira and Polarion in the past. I haven't necessarily worked with them together or consecutively. It all depends on individual project requirements. 

That said, I am not using Polarion anymore.

The initial setup was not overly complex. It was pretty straightforward. A company should have too much trouble with it.

The pricing of the solution seems to be pretty good. It doesn't strike me as being too high.

I'm just a customer and end-user. I don't have a business relationship with Microsoft.

Overall, I would rate the solution at a seven out of ten. It's been okay so far. We're satisfied with the solution overall.

We provide this solution to our clients. The company we're currently assisting has had a lot of issues using Jenkins and decided to move the CI/CD pipelines to Azure DevOps. I'm a solution architect and we are partners with Microsoft. 

The solution offers great features including the project management feature and the Git-based repository. There is also the Azure pipelines and release artifact so you have all the functionality in one tool. It's also a relatively cheap solution.  

The only area that requires improvement is the interface. 

Stability is good. 

Scalability is good. 

The technical support is good.

The initial setup is easy. We had a team of three engineers dealing with implementation. 

Licensing costs are very reasonable compared to other solutions. It's a good price.

My only advice would be to go for the cloud version of DevOps, it's a better product. 

I rate the solution eight out of 10. 

We use this solution for project management and delivery.

It is easy to use.

We are able to generate many different types of reports from Azure. It connects well to PowerBI. 

The performance is good.

They could have more reporting features added to the dashboard. There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps. 

We would like to have the same calculated reports that can be accessed in PowerBI, available in Microsoft Azure DevOps. 

We have been using Microsoft Azure DevOps for the last two and a half years.

Microsoft Azure DevOps is a stable product.

It is easy to scale. We have approximately 250 employees in our organization who use this solution.

We have contacted technical support. They provided us with a fast resolution.

We are using Azure, and TFS now. We are also planning to migrate to AWS as well.

The installation was easy.

We have an IT team of four to manage and deploy this solution.

I would definitely recommend this solution to others who are interested in using it.

I would rate Microsoft Azure DevOps an eight out of ten.