Microsoft Azure DevOps Reviews

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.

We are a reseller of solutions and provide maintenance to our customers. Azure DevOps is one of the products that we have experience with.

Our customers use this product when they want to enter the DevOps space and integrate or consolidate all of their existing tools. It allows them to communicate seamlessly between development, their operations, and other team members.

This platform provides a large span of tools and technologies.

I would like to see better integration and collaboration between tools. There are different companies offering different tools, and how well something is integrated contributes to the completeness of the solution. 

The platform needs to be updated because things are still in the process of change.

I have been working with Microsoft Azure DevOps for almost three years.

We have had no complaints about stability.

Scalability has not been a problem.

We have not been in contact with technical support.

The initial setup is complex. It really depends on those who are using it in the company and exactly what they're utilizing with respect to tools. It also depends on whether they want to integrate it.

We have an in-house team for deployment.

The price of this solution is fair.

There are a lot of different tools on the market such as Jira, so I would look at DevOps as one option and how it is going to handle things in your environment.

I would rate this solution a six out of ten.

We are a small product team and we do software development. I'm part of the testing team and I use Azure DevOps to manage all of my test activities. This includes my test plan, where I create my test cases, write test scripts, execute them, and publish the results using the dashboards.

I like a lot of the features in Azure DevOps.

The creation of test plans is valuable and I like the reporting features that it offers. For example, I like the charts, as well as reporting progress.

The interface is user-friendly.

I have not been able to use the integration with automation features, such as test management automation, with a framework that is written in Java. Currently, Azure offers frameworks that are written in C#. I have not found anything in the Microsoft documentation to say that it supports other languages.

I have been using Microsoft Azure DevOps for approximately two years.

Being a SaaS product, sometimes we experience hangs. However, that is okay because in general, it is very much stable. If there are any outages then I get prior notification of such events.

I have not tried scaling it. In my team, we have approximately 30 people who are using it.

For me, the first point of contact is my internal organization and not Microsoft directly. However, if there are any changes that require Microsoft's intervention then there is an intermediate team who coordinates it. The response has been pretty good and I am happy with the support.

I have used several tools in the past including Zephyr and the Rational Quality Manager.

The initial setup is pretty straightforward. We needed to set up a Microsoft account, and that gives access to the projects. Basically, the IT department or IT administrators take care of the access.

As a member of the team, once access is provided, I can just start using it. It is plug-and-play, as far as I'm concerned.

It is a subscription model and I only pay for what I use.

Very recently, I was doing comparative studies of available test management solutions on the market and I find Azure DevOps to be pretty good.

Overall, this is a good product and I recommend it.

I would rate this solution an eight out of ten.

We are using this solution for workflow management, especially when using a Kanban board to monitor the small assignments. Also, some programming for some of the disciplines. It's still in its infant stages.

It's a complete solution that has everything you need. 

It covers all of the development workflows to the initial planning, testing, coding, and even to launch the subsequent feedbacks.

Also, it has marketing reports.

It's very promising. They are very well positioned to take over some pretty heavy contestants in that area.

I think that they have some menus there that are not very well placed. For example, I was searching for some extensions in the marketplace and I couldn't find my way back to the console. It's not very well designed.

The general user interface is nice. It's intuitive, but I had the luck to discover something that is not very well designed. The fact that I can't return back to the console is very strange. I couldn't find my way back. I had to log off and log on again and get back to the console in a very awkward way.

I have been using this solution for a few weeks.

We are using the latest version.

It's a stable solution.

As per the documentation that I have read, it's pretty scalable. My brother, who works with this solution practically every day, says it's scalable.

We plan to continue using this solution.

I have not yet had any experience with technical support.

Previously, I just used GitHub, so just Version Control for code and not much more. 

I used also their integrated development environments including Visual Studio Code and Visual Studio. These solutions are built by Microsoft.

It's straightforward. With the cloud solution, there is no installation.

I could create the main console for the project very quickly, with just a name and description and the rest is the default.

This is a product that I can recommend to other users.

I would rate this solution an eight out of ten.

I am a consultant and this is one of the tools that I use to help develop solutions for my clients.

The most valuable feature is the complete integration between test cases, pipelines, and issue management.

The test management section needs to be improved. It is easy to use but they can make changes such that it is more comfortable for the users.

I would like to see a full-quality dashboard added. For example, if I am not using their pipeline then I would still like to see the dashboard available.

I have been using Azure DevOps for more than two years.

I have found it stable, so far.

This product is very scalable. I am currently using it for about 10 users and if I want to add more then I have to pay more money.

I have not yet been in a position where I needed technical support for this product. In the past, I have dealt with Microsoft's technical support for other products and I have found them to be fine.

I have also worked with similar tools such as GitLab, GitHub, Bitbucket, and then Jira.

Because I am a consultant, I work with multiple tools and the choice is that of my client.

I find that the pricing is good, and it is competitive with the other vendors in the market.

My advice to anybody who is considering Azure DevOps is that it is quite easy to onboard. It is a good product if you really want to work in a close-knit environment.

I would rate this solution an eight out of ten.

We use Azure DevOps for managing our workflow, as well as the CI/CD.

We use the CD/CD for all of our deployment lifecycles.

The CI/CD portal is very user-friendly.

The platform is very easy to manage. It is easy to manage repositories between the business users and corporate users.

Fields can be customized and the reporting is good. The APIs that are exposed can generate management reports.

The most valuable feature is the test manager. 

Integration is easy to do. The single-sign-on facility is there in every aspect including Azure DevOps, Active Directory, our portals, and all of our development sites.

Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves.

We would like to have an indicator of the percentage of occupancy. Suppose a person is working on two different domains, and we have 70% on one project with 30% on the other, it should be able to report that. As it is now, we have to manually enter that data. If this functionality were provided then it would make it easier for users.

We have been using Azure DevOps for the past two to two and a half years.

We have had issues, usually related to the APIs, but the support team has always helped us to resolve them.

The Microsoft support team is prompt to respond and very good.

The price is cheaper than Jira and some of the other competing tools.

Overall, this is a good product and if the Gantt chart and occupancy reporting features are added then it will be the most powerful one in this space.

I would rate this solution an eight out of ten

We are a manufacturing company and I am a technical consultant who is responsible for managing the software applications that are outsourced for development. In this role, I have gained experience using Microsoft Azure DevOps.

I have also used it as a software developer in companies that I previously worked for.

I like the entire tool because it is a one-stop-solution for DevOps.

The Scrum functionality in project management is helpful, as are the code repositories. It has support for pipelines.

There are certain areas in Azure DevOps that are better in other products. These are things that I need to more fully explore.

I have been working with Azure DevOps for approximately four years.

The stability is good and I haven't had any issues with it.

At this time, the majority of our software application development is outsourced so there is not much in terms of DevOps. However, in the future, I am planning to implement DevOps here. Once that happens, I expect that our usage of this solution will increase.

I have not needed to contact Microsoft's technical support.

The initial setup is straightforward and easy. It takes very little time to deploy.

I deployed this solution without any help.

Personally, I like this product and it is one that I recommend. That said, based on my experience, I cannot say that it is perfect.

I would rate this solution a seven out of ten.

The Repos, Wikis, and pipelines are all excellent features.

The solution could work to improve their reporting.

The stability of the solution is good.

The scalability of the solution is good. I would give it a four or five-star rating. We have plans to increase usage. Right now we have about 100 users on the solution.

Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support.

We did not previously use a different solution.

The initial setup is straightforward. We just implement it from the cloud. We took it and configured it with our local website infrastructure, so there was nothing much to do.

There is a licensing fee of $6/user per month. That's not too much money for us. There aren't really any additional costs beyond that.

We considered using Jenkins, but we decided to use Azure DevOps because we have an enterprise agreement with Microsoft. It was much easier.

We are using the public cloud deployment model.

Potential users should not hesitate to move to Azure DevOps. It keeps on progressing and keeps on adding new features all of the time, so it's a solution that I would highly recommend people use.

I would rate the solution eight out of ten.