Microsoft Azure DevOps Reviews

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 are currently involved in a financing exchange project, and we use this solution to keep track of the exchange activities within the backlog. We are not taking advantage of the repository and the code stuff at this stage. 

The most valuable feature for us at this stage is the Azure Boards.

I really like the user interface. For comparison, I have been using JIRA for several years now, and I am rather skilled at using that tool. The reason for my using Azure DevOps is because my client uses it. My first impression of DevOps, after using JIRA, is that it has a much better, more intuitive, and more user-friendly interface. That first impression is still valid, today.

There is a lack of integration and portability with other tools and products.

I would like to see better interoperability with the agile scaling frameworks.

When I first started using Azure it was impossible to figure out how to do the configuration correctly. Perhaps there should be a configuration environment that hides some features and is not open for everyone.

I find it difficult to find some of the features, although it may be that they are not enabled, or perhaps I have to take some time to better understand the tool.

I cannot really comment on the scalability of this solution. We are running in a microenvironment with only a few users and a few integrations. It is enough for us at the moment, but if we want to go forward and continue to work with it then that will be a discussion for later.

We have approximately fifty users right now. There are three or four administrators, and the remainder of them are end-users.

I have not contacted technical support. Coincidentally, I needed support today, so I went online to find the answer. The toolkit for helping yourself is there, but perhaps it should be more integrated into the solution.

I have used JIRA for several years, and although I am impressed with the interface in Azure DevOps, JIRA still has better integration with other tools.

The initial setup for this solution is much easier than for that of JIRA.

My advice for anyone implementing this solution is to have an expert for every fifty users of the solution. This person is responsible for configurations and so forth.

If you have a Microsoft environment then this is an easy choice for you, but if you don't then I think that JIRA would be a better choice.

I would rate this solution a seven out of ten.

We use Microsoft Azure DevOps for applications that analyze data and the data scientist creates the test data for the manual and automatic application tests. Here in Europe, we need anonymous synchronization of all data for testing.

We create special applications for creating data for direct tests.

Microsoft Azure DevOps has been very good for creating pipelines, and all the solutions for creating task management for developers and for the business. 

All of the tests of the applications are done on the mobile or web interface and it could be improved.

The connection to Power BI could improve. Power BI is a very good platform for reporting and presenting processes, but a good engine does not exist to present the process development in time in Power BI. It's a typical business reporting tool.

I have been using Microsoft Azure DevOps for approximately one year.

Microsoft Azure DevOps is highly stable.

There are two options to build. The first option is to build in the cloud, which is very stable but not quickly. The second is to build the systems in the local networks. 

We have 5 to 10 people using this solution in my organization. We have three DevOps and the others are the QA cluster.

We do not use support from Microsoft, we have not had any problems.

The initial setup of this solution was complex. Every part of the implementation was difficult.

For us to implement our production it took approximately 10 to 20 sprints. One sprint is two weeks.

We require a three-person team for the maintenance and support of the solution.

The price of the solution is expensive.

All people who work on projects must have good staff in development in .net, and need to have certificates. The minimal certificate is the AZ-204 Azure developer, it is obligatory.

I rate Microsoft Azure DevOps a nine out of ten.

The plugins are the biggest thing. I like how Visual Studio is designed as a shell application, and then the plugins make it do what you want it to do.

Microsoft could improve Visual Studio by making it easier to find the plugins you need to get your job done. Maybe they could implement an AI search instead of a simple tech search. Sometimes, people come up with a catchy name for something, and you don't know how it's spelled. For example, a developer might come up with a packet wizard and spell weird, like P-A-K-I-T.

I've been working with Microsoft Visual Studio since it first came out in 1997, so about 24 years.

Visual Studio is very stable.

I don't think scale applies to Visual Studio because it's a developer tool. And I haven't had a lot of experience with massive projects where multiple teams are working on the same source code. I've only worked on a team of a few people.

I think support is probably pretty decent, but I've never had to use it. I just look at Visual Studio's source code to troubleshoot it. 

The setup is pretty straightforward. Visual Studio runs pretty fast.

I'd say Visual Studio is a nine out of 10. If you're thinking about adopting Visual Studio, research the kind of functionality you need. The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in.

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 are using the tools in this solution mostly for planning our software projects by implementing Scrum. We use repositories, and create timelines for continuous deployments and integrations.

The reports have been most valuable. We have created some dashboards allowing us to be able to check our teams, their progress, and mission plans.

Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult.

I have been using this solution within the past 12 months.

Microsoft Azure DevOps is highly stable.

The support from Microsoft is great, if we need to solve some problems with Azure they are ready to help us. The support has been excellent.

Previously we used Visual Studio but then we changed some of our repositories for our projects to the cloud and now we use Microsoft Azure DevOps.

The solution is easy to install and it took us three months to implement. This includes the support for our teams and for them to come up with their strategy to manage our projects.

My advice to others wanting to implement this solution is they need to think about their inter-process before moving to this kind of solution. In many cases, we start to configure some projects using the tools, but if we do not have our roadmap and do not define our goals, we cannot take full advantage of the tools. There should be a lot of planning before moving to the projects.

I rate Microsoft Azure DevOps a nine out of ten.

We are an agile shop. We use it to build our sprints and for our user stories. We have everything aligned in epics and we track all of our requirements and our velocity.

We are still getting used to it and there is a lot that I haven't looked at yet. For me, at this early stage, the most valuable features are the basic functionality. This includes the ability to build and customize sprints.

I like the tracking and that we can monitor our velocity.

It took a bit longer to figure out, but now that we have, it's easy to use.

When converting to DevOps, it was difficult to map.

I have been using Microsoft Azure DevOps since October 2020 when we converted from Jira to DevOps.

It's stable now that it is up and running. It was a steep learning curve, but not the fault of DevOps. We did not put together adequate training.

Others in the company may have scaled this solution. I have not explored this area yet.

I have not contacted technical support.

Previously, we were using Jira. Now that DevOps is running, I find that for what I am doing, does the same things as Jira. The main difference is in naming convention and layout.

I wasn't part of the conversion from Jira to DevOps but it was a painful process. We lost data, things didn't map. My Scrum Master who used it was not happy with the process.

I would rate Microsoft Azure DevOps and eight out of ten.

We use Microsoft Azure DevOps for application lifecycle management, including source control-related things, pipelines, and also for work item management. In short, the whole ecosystem.

Within our organization, there are roughly one thousand core developers using this solution. We also have stakeholders, product vendors, Scrum masters, testers, and manual testers. 

Mainly the source code solutions and the pipelines. Work item management and the manual test I/O. Test automation, end-to-end testing, and the manual test experience. It's got something that you won't find in other products. The work item management is good enough for small to medium-sized teams, and for large projects with plenty of teams collaborating with each other.

We can achieve the boundaries of the system. Potentially, we could do it with other tools like Jira. Still, with Microsoft Azure DevOps, we can manage everything.

Currently, if you would like to use the full-set of customization features, for example, the process templates, the HL process, or the Scrum process, if you start from scratch right now, you'll have these options. But if you've been working for several years in an established ecosystem, then you're based on an old-fashioned way of working and you won't be able to use the recent customization features.

There are options to get around this, especially if you move to the cloud or if you copy things and migrate them, but that's a huge amount of work. It's best if you start from scratch in a new project — in a new environment. With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem.

We have been using this solution for roughly 10 years. 

This solution is stable. I don't have anything negative to report. 

Microsoft Azure DevOps is very scalable. It uses techniques from Microsoft itself, so if you have the knowledge of how to deal with that, you can scale it up and out as you wish.

Technical support is good. We have had a few cases where we needed support and they contacted us immediately. There was a willingness to find a solution and determine if there was a bug or if it was an oversight. We have a good relationship with Mircosoft support.

The initial setup is easy.

Most of our developers have an MSDN license which is linked to the Visual Studio development environment. 

We also have a corporate license for other products like Windows Server — it's all included in one package. An additional license is not required for the on-premise solution. If you go to the cloud, it's a different story. Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs.

Overall, on a scale from one to ten, I would give this solution a rating of eight. 

It could be a little bit more flexible in terms of work item management. Apart from that, I can't really think of many features that are missing. It supports all kinds of ecosystems; there are a lot of possibilities when it comes to interacting with other ecosystems. 

Try to follow the market standards. There's a whole huge community that supports it. The market is evolving very fast. Microsoft is acquiring other companies. They recently bought GitHub. It's hard to say which solution will survive — DevOps or GitHub. That may be an issue in the future.