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.

The company that we were working with was in development using a Microsoft platform. We used Azure to integrate the complete project management and DevOps work.

This solution works with other Microsoft solutions pretty easily. It was easy to integrate everything into all the other tools that we were using. It integrates very seamlessly.

I have not come across information for integrating this solution with others, such as ServiceNow. I am not sure if the integration would be straightforward to implement. There should be readily available information to accomplish these integrations.

I have been using the solution for approximately two years.

The project that we were using the solution for was a small implementation, I cannot fully comment on how scalable it is. I did not have enough data to comment if it was good. However, we did not have any issues.

The customer support is good.

The installation time of this solution depends on the environment it is being implemented in. We had a couple of projects that took around two weeks of implementation. This included the whole integration of the DevOps and everything together.

We had an expert that did the implementation of the solution for us. He did not face any problems.

There is a license for this solution.

We plan to continue offering this product to our customers and I would recommend it.

I rate Microsoft Azure DevOps a seven out of ten.

Some of the valuable features are the interface and the workflows are easy to learn and to manage. It has all the features that are required on each account.

There are some areas that need improvement such as tracking. There is not anything major that needs to be improved in the future, just minor adjustments are needed. The solution works well.

I have been using the solution for a few years.

The solution is stable.

I have found the solution to be scalable, we have approximately 30 people using it.

I have not used the support. However, you receive all the documentation with the solution needed.

I would recommend this solution, it is a good tool to use.

I rate Microsoft Azure DevOps an eight out of ten.

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 implement this solution to those wanting to improve their processes to make their business function better.

Some of the valuable features are the functionality and the wide range of capabilities.

Not all companies use the same methodology which could limit the use of this solution.

I have been using the solution for approximately two years.

The stability of the solution is great.

I have found the scalability good. We have approximately four specialists and ten testers using the solution in our organization.

I would recommend this solution to others if they have tools with Microsoft and the proper infrastructure because not all customers work with this methodology in the development team.

I rate Microsoft Azure DevOps a nine out of ten.

We use DevOps for backlogs and work items. We divide our releases into many sprints to keep our development on time, and we use DevOps to manage tasks for development or business teams.

DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams. We manage everything through this.

I want DevOps to have more automated reminders about tasks that don't need management. We don't have reminders, so a project manager must track the tasks. It's not automatic.

We've been using Azure DevOps for three years. 

DevOps is stable. 

DevOps is scalable. About 70 people use the solution on average. 

Another team handles the implementation, so I wasn't involved. I'm on the business team. Two engineers are responsible for deploying and managing DevOps. 

We pay for a yearly license. 

I rate Azure DevOps eight out of 10. I prefer Jira, but both solutions are very nice. 

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 use the solution for all our CI/CD automation needs.

The simplicity and ease of use are two features that we have found to be most valuable.

The solution can be improved by having better integration with other cloud platforms.

We have been using Microsoft Azure DevOps for a couple of years.

The product is stable.

The solution is scalable.

We have plans to increase usage so that it will be on an org-wide scale. We plan to go up from our present number of 100 users to 300.

We've never had occasion to utilize technical support.

As the solution is cloud-based, installation was not required.

We pay a monthly license for Microsoft Azure DevOps.

The solution is cloud-based.

There are 150 people using this product in our organization, only end-users. 

There are five people responsible for deployment and maintenance. Anyone who wishes can make use of the solution.

I would recommend this solution to others contemplating its use.  

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