Microsoft Azure DevOps Reviews

We use it for planning, pipeline management and testing, as well as using it as a CI/CD tool.

I like the agile management of projects, running stand-ups and the like. The pipeline management feature is great.  

We'd like to see an improvement in reporting across multiple projects. The same applies to improving program visibility so that project managers can get that pane of glass to assist with their work. It would be a big win for a lot of users as well as a good addition to the tool. 

We've been using this solution for close to four years. 

The solution is stable. There are still the occasional issues but on average it's very stable. 

The solution is easily scalable because it runs on the cloud and everything is managed by Microsoft. We don't do anything in terms of increasing capacity so when more users are added the increased capacity is automatically managed. 

We haven't made a lot of calls to technical support but when we have their response has been good and quick. 

We have a DevOps engineer who carried out the implementation for us and I believe it was relatively easy. 

I rate this solution eight out of 10.

I work as a DevOps Engineer. I use this solution as an end-user.

I definitely like the pipelines and the ease of management once you're in an enterprise. 

The controlling security, the ease of access, the free plans, and the developer plans.

I also like the licensing structure in general.

I would like there to be more seamless integration with GitHub. 

Azure DevOps seems to be targeted towards enterprises and GitHub is the ugly sister, so to speak, that you come about in the enterprise. 

There is no real interaction between the products, which is a real shame since they are both developed by Microsoft. 

Definitely, there should be more integration between GitHub and Azure DevOps.

I have been working with Microsoft Azure DevOps for a couple of years, ever since they changed their name from Visual Studio Team Services.

Microsoft Azure DevOps is definitely stable.

I have experience with Azure Bicep and Paraform.

The initial setup is quite easy.

The licensing structure is good.

Definitely, I would recommend this solution. I would still look into your team goals and what tools you already know. 

GitHub is more community-driven, with more modules that are easy to access. 

Azure DevOps is more integrated with Azure as a platform, and that is important to consider when you consider DevOps in general or Azure DevOps.

I would rate this solution a seven out of ten.

We are using it for managing the teams and planning the screens and scope of work. We are also using it for building pipelines for automation of builds.

Monitoring is most valuable.

Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials.

It is stable.

Their technical support is pretty good.

Our IT department installs this solution.

Before using this solution, I would advise getting somebody who really knows how to use this solution and learning about how to do customizations based on your organization's needs.

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

I am using the solution to create continuous integration and deployment agents on the server environments. We are also involved in some projects where we create user stories and features created on the solution.

The most valuable features are continuous integration and deployment, and simplicity.

The active directory password system needs some improvement because many times the password for the active directory expires before the set time. Additionally, in the beginning, when I get the repository and check in my code on the dashboard to see who made changes, it shows that another user made the change that did not. This could be fixed in a future release.

 have been using the solution for three years.

The solution is stable.

I have found the scalability of the solution to be good.

I did not contact support but I was able to find all the information I needed on the internet.

The installation is straightforward.

There is a license for this solution.

I have experience with other solutions and with this one, you can add many addons without any difficult configuration. It has all the code and related items together, it is a total package.

I highly recommend this solution to others.

I rate Microsoft Azure DevOps a nine out of ten.

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 the solution to store all our source codes. It's a solution that stores everything. We are an in-house development and we produce a lot of codes.

We also use it to control our development process. We follow some methodologies. Every every team has a different methodology, for instance, Chrome, Agile, et cetera. The whole process from the planning process until we deploy the solution, everything is controlled by DevOps.

The solution is very good at automating various aspects of the DevOps process. You can automate almost everything. You don't have any human intervention. It's almost automatic. As long as you finish your code and put it in, the software gets the code and tests it. If it is okay, it will go ahead and integrate it and put it in production without any human intervention. This is excellent.

The tool allows you to connect with many external tools. You can improve the whole process that way. We use a couple of things, however, there is a plethora of things you can put together in your solution.

The initial setup is very easy.

Despite the fact that you can automate most of the things, you still have to produce some scripts. There are things that are not very user-friendly. The tasks are achievable, however, it's not easy. You have a lot of steps until you can get the thing automated.

In the past, Microsoft DevOps was integrated with Microsoft Project. Out of the box. Right now, it's no longer that way. That would be interesting to have.

It would be great if I could integrate with a human resource type of software that could control timesheets.

I've been using the solution for 15 years now. It's been a while. It's well over a decade of experience.

The product is extremely stable. We've used it for 15 years and haven't had any serious issues. There are a few bugs or glitches but nothing tha can comprimses the day to day operation, and they usually fixed in the next release. It doesn't crash or freeze, though sometimes gets a bit slower due to databes overheadd, so maintance has to be done. It's reliable.

We are a small team, and therefore we don't need to scale. However, I've heard both that it grows 10% a year without issue and that it scales very easily and very well. As far as I know, a company can scale it if they need to.

We have between 50 to 70 people using it, including staff and managers, et cetera.

I have used technical support a couple of times. Typically, it's good. It's usually a couple of hours and then, they answer you. Nevertheless, you can go to the online site and most of the time you can solve the problems just by reading. They have a lot of documentation available. 

That said, when we dealt with them directly, they were pretty fast. I'd say we are satisfied with their level of service.

The initials tup is not complex. It's a very easy, very straightforward process. A company shouldn't have any trouble with implementation. It only takes a couple of hours. It's pretty quick to deploy for DevOps purposes.

We are just a customer.

We intend to move from on-premises to the cloud next year.

I'd recommend this solution. It's a worthwhile investment.

I would rate the solution at a nine out of ten. We've been quite satisfied with it overall.

We are using Microsoft Azure DevOps for tracking the requirements and tracking the issues.

Any issues that we have, are tracked and logged.

Also, we check the developer's workload.

It can be used for different purposes as well. For example, it can be used by software companies and different software teams for collaboration.

What I like the most about this product is that it's free and it's secure.

You can easily assign it.

It integrates well with other Microsoft products, such as Outlook.

If we experience a login issue, it sends a notification to one of my developers and you also receive an email notification, ensuring that there is no way that a developer can miss working on it or miss seeing it in emails.

The user interface could be improved.

I have been using this solution for approximately two years. 

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

We have not had to scale it, as we have a very small team with only four members who use this solution on a daily basis.

We have not had to contact technical support. There hasn't been a need, it's very simple.

If you have any issues, you are sent a link through email, you click on the link to address your specific requirements and close it.

You will receive an email notification to confirm that the case is closed.

Previously, we were using Microsoft Excel. We decided to use Microsoft Azure DevOps because it allowed us to assign tasks and get a notification.

The initial setup is simple.

It was easy to deploy and within a day, I was able to learn it and work on it.

I did not use a vendor or an integrator, I did it on my own. It's a Microsoft product and we all use Microsoft.

Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects.

I would recommend this solution. It's a good tool and it's free.

Instead of spending money on premium tools, you can at least start with Microsoft Azure DevOps and then upgrade it slowly.

You can learn how to use this tool in less than a day.

If you have Microsoft 365, this comes with it for free.

It doesn't require any maintenance.

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

All of the features related to release management are very good. We use release management and dev management, and the dashboard is good. The ability to specify multiple platforms in release management, by using Docker, is valuable.

Better integration with the Linux operating system would be an improvement for this solution.

I would like to see more third-party plugins; by comparison, the open source solution, Jenkins, has thousands of plugins available.

The Wiki for this solution is not very good.

There is a problem when you want to run a release pipeline for an organization that needs enhanced security. There is no option to configure a dynamic login for a station that is running the tests. The only solution in the platform is to configure an agent that uses a fixed username and password login. There is no option to change the username or password for the login dynamically. If I want to run multiple tests, with different users, then I cannot do it. When it comes to running tests, it needs an option to use different users or authentications. This is a very important feature that is missing.

This solution is very stable.

Scalability is not particularly relevant. It depends on what kind of scaling you want to do. Generally, it has very good support for scaling.

There are hundreds of developers using this solution.

We only had one issue, and I would rate their technical support at medium, based on that experience. The issue was related to shrinking a database, where it was not working well. It took a long time for Microsoft support to fix the problem.

We did not use another solution prior to this one. However, I use other tools in conjunction with Azure DevOps. One of these is Jenkins, for CICD, and I also use the Atlassian Suite.

The initial setup for the latest version was very straightforward. The upgrade was quick and lightweight.

I handled the implementation on my own.

This is a solution that I would recommend.

Azure DevOps is a leading platform, but some things can be better. 

I would rate this solution a seven out of ten.