Microsoft Azure DevOps Reviews

We normally use DevOps. On the application, everything has gone DevOps, however, we don't use the functions. All applications developed there have gone under Azure or AWS. We normally develop them to be able to not be dependent on anything, so if we want to deploy them in another environment, we can deploy them easily. If we want to use it in Azure, we use it in Azure. If we want AWS, we use it in AWS.

I like the CD pipeline. It's the most valuable feature for us. It's so easy to integrate into the CD/CI environment. I mostly love that one.

The initial setup is quick and easy.

The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code. 

If you want to use the DPR it's a bit harder due to the fact that it's only 30 days.

We've been using the solution for a year and a half at this point.

The stability of the product has been good so far. I can't say that I've witnessed glitches. There aren't bugs. It doesn't crash or freeze. It's reliable, as far as I can tell.

We don't have any issues with the scalability of the solution. If we need to, we're able to scale.

We've never contacted Microsoft for technical assistance. 

We are Microsoft partners. We have several Azure experts on our development team, and we have a tech that came from the US and did the training for us. We have a very strong understanding of the product and therefore we don't need help with troubleshooting or anything of that nature.

We also currently use AWS, however, I prefer Microsoft's solution as it's a bit easier to use overall.

We did not find the initial setup to be complex. The implementation is straight forward. 

Deployment is quick and typically only takes a few days or so.

We have ten people that handle maintenance. They are in different parts of the world. We have two in Australia, for example, and two in the USA.

The cost can get pretty high if you aren't paying attention to what you are doing.

We're partners with Microsoft.

I'd highly recommend Microsoft, and I recommend it more than any other solution. Everything is very simple and straightforward. The only worry for some organizations may be the cost. You need to be really, really careful.

I'd rate the solution overall nine out of ten. I think it's really, really great. If the functions were a bit better, I'd give it a full ten out of ten.

I do not recall which version we are using. 

The solution is good for everything, including end-to-end planning and its deployment and testing. 

I like that the solution is stable and that all ends of the process are integrated seamlessly into the tool. These are the solution's greatest strengths. 

The solution should have fewer updates. We need the updates for July. Microsoft tools are sometimes too feature heavy and offer more features than the person actually needs to use. This is why I did not rate it as a ten out ten. 

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We initially found ourselves struggling with this process.

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

The solution is very stable. 

The solution is very scalable. 

I feel the technical support to be fine. We have not encountered any issues in this regard. 

Prior to Microsoft Azure DevOps, we were using Jira and, before this, KFS. 

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We struggled with this initially.

The installation was undertaken by a consultant. 

There was a team of, perhaps, five engineers involved. 

I am not aware of any licensing subscriptions for the solution. 

I would very much recommend the solution to others. 

I don't see the need for more integration with other platforms, as the solution is already pretty well integrated, at least, that is, for our needs. 

I rate Microsoft Azure DevOps as a nine or ten out of ten. 

We are exploring this solution. There is not enough protection in the environment at the moment. It's been almost six months since we started the process of exploring the DevOps environment in Microsoft Azure DevOps.

We have a customized development methodology so that it is easily marked to our existing environment. Currently, we required that all these systems blend easily in this one environment. We can actually use all the large frameworks within DevOps properly and automate most of our support, starting from planning through support to deployment.

It has a good GUI, and it's very user-friendly. It is also a familiar environment as we are used to it. All our users are very comfortable working with it. I think the Azure methodology and all those DevOps features in the dashboard are very effective in our environment. 

It's very implementable in our environment compared to the other DevOps environments which we experienced. I won't name them, but this one part of DevOps we have found very easy in our environment because the infrastructure there is fairly supportive and very integrable to the current DevOps environment we use.

The testing environment and different pipelining concepts can be improved. It can also be more user-friendly. They can actually incorporate all those other features, current tools and have those mind maps.

They could add some good analytic features. I think they can be more enriched with some good reporting features. They can also improve the designing tools.

We have been using Microsoft Azure DevOps for about six months. 

Microsoft Azure DevOps is a stable product. I feel it's stable enough for us at the moment. 

The initial setup is not overly complex. It's fairly straightforward. Other than the Java environment variables which lack documentation, it's not complex and easy to follow.

The main agile features are very expensive.

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

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.

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.

With Azure DevOps, I plan and track my project using Azure Boards, manage my code with Azure Repos, and automate build, test, and deployment processes using Azure Pipelines. This streamlines my development workflow and ensures efficient collaboration and project management.

The most valuable feature in automating our build and release processes with Azure DevOps is the scheduling capability. At the end of each sprint, we schedule automatic releases to QA and development environments, ensuring our latest code gets deployed without manual intervention. Additionally, triggering pipelines upon code upload to the main repository adds significant value to our development workflow.

Azure DevOps could be improved with more security plugins, especially for SaaS scanning and vulnerability scans.

I have been working with Azure DevOps for two years.

I would rate the stability of Azure DevOps as a ten out of ten.

I would rate the scalability of Azure DevOps as a ten out of ten. At our company, it is used daily.

Technical support from Microsoft is very helpful, especially when I need assistance with tasks like migrating work items between Azure DevOps and other platforms. I would rate the support as a ten out of ten.

Positive

The initial setup is easy. Deployment typically takes around ten minutes at most. We have set up an automated process that recreates everything, so even if there is damage to the VM or target machine, we can quickly retrieve and redeploy everything ourselves.

We require about two DevOps engineers to maintain Azure DevOps for our company, which has around 400 users in total.

I would rate the costliness of Azure DevOps at a seven out of ten.

We ensure the security of our company's source code uploaded to Azure Repos by using a SonarQube Plugin and then automate its deployment to various environments like development and QA. Once approved by QA, we deploy to the production environment, passing through our firewall for protection. This streamlined process ensures efficient and secure CI/CD pipelines with Azure DevOps.

Azure Boards has significantly improved our project tracking and adjustability. It is a powerful tool where we can easily trace work items and monitor the progress of our projects.

Azure Boards is a powerful tool for tracing work items and project progress. It simplifies uploading and versioning of project assets and tools, enabling easy refreshes or benchmarks.

Overall, I would rate Azure DevOps as a nine out of ten. I would recommend it to others.

We manage the full scope of all our projects on Azure DevOps, including all of our kits, bags, and user storage. DevOps encompasses the CI/CD process of every build as well as the customer requirements, QA, and deployment.

Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy.

I've been using DevOps for approximately four years.

Azure DevOps is mostly stable.

We've used Microsoft support but for .NET Core or Azure DevOps.

Installing Azure DevOps is pretty straightforward at the installation or admin stage. Deployment time depends on the service on my side, so it's mostly very fast.

It's a great product for the CI/CD process, but DevOps lacks some features for project management, guide, user story, etc., so it's far from perfect. Compared to monday.com, JIRA, or others, they have some work to do.