Microsoft Azure DevOps Reviews

I am using it as a developer in the agile scrum area.

It has improved the team cooperation for building, developing, and releasing systems.

It is easy to use. The shared repository is useful. Everything is in one environment.

It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members.

I have been using this solution for one and a half years.

It is very stable. If it doesn't work, it is usually because of network issues.

I didn't need support from Microsoft. Any need for support was internally fulfilled by my colleagues.

I would recommend this solution. It is a nice environment for working in teams and implementing the DevOps philosophy. It provides good support for that.

I would rate Microsoft Azure DevOps 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.

• Source code management
• Git repository management including a visualizing for the pull requests process
• Build automation
• Continuous integration
• Project management
• Test management 
• Release automation
• Deployments automation
• Artifacts management
• Package management
• Agile planning 
• Dashboards and reports
• Requirement management
• Work estimation 
• Capacity management
• Backlogs and Kanban boards for different teams
• Load test 
• Integration test automation and unit test projects with status reports on the test results.

Azure DevOps helps us to implement all our DevOps practices with a complete end-to-end cycle starting from code commit till the production deployment including continuous feedback.

This enables us to release the silos between the teams and enhance collaboration. Also, it gives us more control on the project delivery lifecycle and to fix the issues more earlier than before as we are aligned and working on one integrated system which can give us reports about any piece of info.

• Linking the project teamwork (bugs, tasks, user stories, test cases ) with the code, build, release, delivery
• It's a matter of integration to have only one platform for all your software development life cycle.

• Enable more control on Application Insights integration to open different types of work items as this is area still need more enhancements.
• Test management extension is too high to be paid on a monthly basis.
  
• Test and feedback chrome extension still need more development as they are not very stable.

We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps.

We've been using Azure DevOps for three years.

DevOps' stability is great. No problems.

The infrastructure is good so far, and expanding our user base isn't a problem. Microsoft takes care of the infrastructure.

We are billed for a single license, no matter how many users. 

I rate Azure DevOps eight out of 10. 

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.

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