Microsoft Azure DevOps Reviews

We are using this solution for CI/CD projects, for Scrum, Agile planning, testing, and business management system solutions. 

We are also using it for continuous integration, and continuous delivery of DevOps.

I am also using the Git Repositories, which is the main source control for me in the organization. We were using it on-premises and now planning to move it to the Cloud.

They are calling it repository and they are supporting an old protocol, which is a popular protocol called Git repository.

The most valuable features of this solution are the CI/CD pipeline, and the testing automation.

It's good that they are bringing more options to this environment, and to deploy to virtual machines.

The testing agents needs to be improved, they need to work on it.

They can enhance the areas related to continuous integration and build automation. They can add more technologies for the build.

The integration with the Azure infrastructure as a code and include more templates for infrastructure as a code in the continuous integration phase and the build phase.

They can add more flexibility to the continuous deployment.

Artifact management is also an area that needs some enhancements.

I think automation and integration with the CI/CD lifecycle it's good but it's using agents.

I am using a different tool for testing automation because I have not found any use cases on it. This feature is not covered. I'm using only testing and business management. I'm not using the testing automation feature that is provided by Azure DevOps.

I would like to see more integration with other platforms and more flexibility.

They have to add more features such as schedules and more flexibility in the platform. This will allow me to build my space and time based on the schedule and based on a calendar.

I would also like to see a release calendar so that I can plan my releases based on my sprints. 

This is required and it would give this solution more maturity. Between Scrum, Agile Planning, or Project planning with the build and deploy prophecies.

I have been using Microsoft Azure DevOps for three years.

We are using the latest version of this solution.

It's a stable solution. We have not experienced any issues.

It's a scalable product. We have more than 50 users in our organization using this solution.

I plan to continue using it in the future.

Previously, I used TeamCity, Jenkins, I used Chef, and many other technologies.

The initial setup is straightforward, it's a cloud service, so it's plug and play.

I would recommend Microsoft Azure DevOps for other users who are interested in using it.

I would rate this solution an eight out of ten.

We primarily use the solution for our Agile teams, however, we started off using it with our executive suite. Our executive team now meets in sprints every day. Sometimes it's a short 15 minutes, other times it can be up to an hour. We have two-week sprints and daily scrums associated with it. We've also rolled that down from the executive. We've got seven formal Agile teams running throughout the organization across our businesses. We probably have at least 40% of our staff now trained in Agile and using DevOps to execute the projects.

As an Agile team, we're now able to move much faster than we could, even pre-COVID.

Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting. That in itself has had a huge effort on the number of meetings. In the past, you would almost wait a month before you could get all the executive teams together. Now, we've got meetings daily. Due to the regular meetings, we're utilizing daily scrums and two-week sprints, and we've been able to move a lot faster than we've ever had before as far as initiatives. 

Frankly, throughout this whole COVID situation, being able to respond the way we have to some of the changes that were going on has been amazing. I don't think that would have happened if we weren't an Agile team.

There are a lot of features that we could probably work with a bit differently as we learn more about the tool. Right now, we're just really using it from a task management perspective. We've only been using it a year. There may still be more to learn and unpack.

Some of the queries, the way they're built, need to be looked at. We need better query tools.

Being able to report back to boards, to regulators, and the activities and stuff would be helpful. The queries do require somebody else to actually write them. There should, however, be a way to make things a little simpler in that space. Right now it's on us to figure out how to get better at making queries effectively and in such a way we're just not reporting on tasks complete.  

We track the associated feature story. In many ways you can actually go back and see the story, and see the progress you've made on initiatives due to the fact that you can see all the decisions that have been made along the way. If there's a way that person could dig into that and pull more information or insights, that would be very helpful as it would assist us in improving future projects or even help us forecast on an existing project. 

I use the solution daily. We launched it in the company in January. We've been using it across all our Agile teams here for 12 months here.

The stability of the solution is very good. I haven't had issues with bugs or glitches. It doesn't crash or freeze. It's a reliable solution.

The solution's level of scalability is good. We're a smaller organization. We've only got 300 people in total, and out of those, probably 40% of our entire staff use the product. About 120 people probably are in there on a daily basis. That's everyone from executives down to programmers. It's extremely cross-functional across our organization.

I haven't had to reach out to DevOps themselves personally, so I wouldn't have experience there. However, if we ran into any issues, my technology teams would contact them.

We didn't previously use a different solution. That's why we looked for an automation tool. We switched to DevOps mostly due to the fact that our development team was utilizing DevOps as part of their own Agile operations. A number of teams were also already sort of experienced. There are a number of individuals in the company who were experienced that way, and we had homegrown support in some ways when we launched it. It just made sense to go with DevOps as opposed to bringing in something new.

The initial setup wasn't complex. It was pretty straightforward. We didn't run into any issues that complicated the process of implementation.

We did look at Jira briefly, however, it didn't look that different from DevOps and we knew many of our team members were already comfortable with this solution so we didn't pursue it.

We're just Microsoft customers. We don't have any business relationship with the company.

I'm not sure which version of the solution we're using.

I'd strongly recommend the solution to other organizations. I can't see us ever reversing back now after being on this for a year.

Overall, I would rate the solution at an eight out of ten. It's relatively easy to use and it does what we need it to do.

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.

The key thing I find benefits me is the ability to track right from the feature and determine what has happened. I have a direct link to the test and the metrics that are available.

There are a lot of helpful features available for tracking dependencies.

The dashboard could be improved. Although there is flexibility in configuring it, there are some metrics that we have to configure ourselves. Improving the metrics that are readily available on the dashboard would be very helpful.

I would like to see better integration with third-party solutions, where if they are part of the DevOps pipeline then the reporting could be made available on the dashboard.

Having some form of check modeling integrated into Azure would be useful.

I have been using Azure DevOps for the past four years.

We have had no issues in terms of stability.

The offerings in terms of scalability are good.

We have not had to depend much on Microsoft support for DevOps and project management. However, I can say that the general support that we get for Azure is good.

I have some experience with Jira from Atlassian, although I have worked with Microsoft Team Foundation Server from the beginning.

The initial setup was straightforward. While we were migrating, we had training from Microsoft, which was helpful.

I haven't really looked into other options.

Overall, this is a good product and one that I recommend. The features it has have helped us, especially with tracking dependencies.

I would rate this solution an eight out of ten.

We use Microsoft Azure DevOps for management, e.g. managing items that we need to work on, planning activities, connecting to components to get information on how long the developer is working on the items assigned, etc. We use the solution for our projects.

We have internal users from the development team, and we have the work logs that we need to work on for each customer. We match those to have control over the projects and the budget. We have a component plugged into the solution for the billables and performance delivery. What we don't have yet is optimization, and that is something that needs to be improved in Microsoft Azure DevOps, but the solution has all the activities and the budgeting functions, so the project is working good. We're making an exact component in seven days that we can use with the solution.

One of the features I found most useful in Microsoft Azure DevOps is that we can use it to plan activities. We use the dashboard to work on the tasks we have, and also use it to find out what could be better. It's also useful when you have many customers and many people working together on different projects.

In our case, we have one developer working on more than one project within the same day, week, or month, and Microsoft Azure DevOps helps give better control of his schedule, making it easier to find out if the developer still has availability to take on new work. The solution helps us see the work status and availability of team members, making work management and task management better.

The validation and quality offered by Microsoft Azure DevOps are very good. The user experience is good. The speed of the solution is also good, e.g. the pages load fast.

The optimization feature in Microsoft Azure DevOps needs improvement.

Sometimes, having control over multiple projects for a customer could be difficult. If you're a developer, you need to know if you still have time to work on more activities within the day. When you're working on one project for one customer, Microsoft Azure DevOps is great, but when your team is working on different projects for several clients, it may be too hard to handle, e.g. you really need to organize and plan the activities, so planning is another area for improvement in the solution.

Planning includes budgeting, e.g. creating a budget for each project, especially if the developer is working on multiple projects of customers. You need to have control and see to it that you are within budget, but it can be hard because you can't always see the daily, weekly, or monthly activities of the developer, particularly if the developer doesn't keep the calendar updated. We want to be able to view the complete list of activities of the developer, whether daily, weekly, or monthly, to make planning and budgeting easier.

I'd also like the Microsoft Azure DevOps Gantt chart to be improved. We need to see in the schedule how to plan the fields out. We have daily activities and we'd like to use the Gantt chart to make our work approach more successful.

We've been a partner of Microsoft for 10 years, and we've been using Microsoft solutions for 10 years.

Microsoft Azure DevOps is stable. Sometimes there's a little lag, but the next day, it'll work fine. The solution works fine.

Microsoft Azure DevOps is a scalable solution.

Setting up Microsoft Azure DevOps was easy.

We use Microsoft solutions as part of management. We use Microsoft's platform.

We use the latest version of Microsoft Azure DevOps for our projects.

We have 15 people who are in charge of the deployment and maintenance of the solution. Per project, we have one or two developers who utilize Microsoft Azure DevOps: At the beginning, we have the front end developer and the cloud personnel who create the environment, the designer who works to create the right frame, the right materials, the layout, and the design for the project, and at the middle, we have four to five operators.

The platform works well so we didn't have the need to open a ticket or contact Microsoft technical support.

I really like Microsoft Azure DevOps, so I recommend it to people who want to start using it. My advice to them is that it's a huge platform, so it won't be easy the first time. When you test the platform, you need to spend time and make an effort to understand how it works, but it's the best solution. It's the top solution. 

Another advice to new users of Microsoft Azure DevOps is that it's harder to have a macro view of all the processes together. When we needed to cross-match a lot of information from the different processing teams of customers, we found it difficult. You also need to plan well, particularly plan when your developer can work on more than one project. When you have many projects, you need to handle the processes well, e.g. create separate folders for each customer, separate projects, etc., to keep the information separate and be more organized.

Microsoft Azure DevOps could still be improved more, so I'm rating it an eight out of ten.

We are a partner of Microsoft, and we use Microsoft solutions. What we recommend to our customers is for them to use the Microsoft environment, server and databases. We work with some of the solutions and technologies from Microsoft.

We are using Microsoft Azure DevOps for the repository for Git.

We are migrating to the on-premise version of GitLab. We do not use any advanced tools. We are planning to do more with DevOps and are evaluating other tools to incorporate in our process of development.

We use the functionality of Git for our development. We do not use the other tools that are integrated into the DevOps. We use it because we have an enterprise agreement with Microsoft.

Microsoft Azure DevOps integrates well with other components, such as Synapse, which is a data warehouse tool of Azure. It is a framework platform for BI and integrated with other tools, such as Power BI.

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

The solution is stable.

There are other solutions available that are open source and free, such as GitLab.

We are switching from Microsoft Azure DevOps to GitLab because we have the infrastructure and we are migrating part of our service to on-premise which includes our VMs. We decided to install GitLab because it is open-source, free, we can install it in-house, and we have some members that have experience with that product. We are now starting to migrate some projects.

I would recommend this solution to companies that use the incorporated services provided, it is very good to adapt as a DevOps tool.

I have not used the solution extensively enough to give the solution a higher rating.

I rate Microsoft Azure DevOps an eight out of ten.

We use Microsoft Azure DevOps to maintain our project. We create a project in a good DevOps, and then we add the backlog items. The product owner adds the backlog items, and then the development team. The repository is also built into that. We have a private Git report for the project. Under reports, we can create a repository for the big projects and maintain the source code. 

Developers can commit and make a full request. For example, configure Jenkins, reconfigure Jenkins with the repository credentials, and then use it for linking. We don't use the pipeline available to us, and we use Jenkins for CSC.

In our organization, Microsoft Azure DevOps helps senior leadership go in and check the project status and how much effort has been put in by the development team. They can also pick, choose, and add features to be used by the development team. It's like a backlog management tool that helps improve and support projects. 

It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful. 

Integration and plugins for other tools could better. Like if you want to integrate the DevOps with other tools that are in the market. This could be for the engineering tools to check code quality, application security tools, and DevOps dashboard tools. 

They could also make the implementation easier. The test plan also has basic features that are not user-friendly. It should also have integrations with test automation tools. We need a test plan, automation testing, and EA-based testing.

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

We haven't got any issues with the technical support area.

The initial setup is very straightforward. 

Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users.

I would recommend this solution to new users if it's a simple project. If you want JIRA, you'll need to have JIRA software for backlog management. 

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

We use this solution for continuous integration. It provides us with strategic analysis. We use it to create and deploy virtual machines. In short, we mainly use it for integration and deployment.

Currently, there are five to ten of us working on conception. Soon, there will be more than 200 of us using this solution. 

The most interesting subject for me is the deployment part where you build virtual machines and enable them to learn. That's interesting to me.

As I'm in the very early stages of this story, this is a hard question for me to answer. However, I think that the integration is to some extent, immature.

Overall, so far we have no major issues to report. 

I have been evaluating this solution for roughly six to eight months. 

The initial setup was quite straightforward.

The licensing costs are reasonable. 

We also evaluated GitHub and GitLab. We actually have one deployment that is already ongoing in GitLab. 

Currently, we're evaluating both GitLab and Microsoft. We're trying to get a sense of which one is better for us. 

Overall, I would give this solution a rating of eight out of ten.