Microsoft Azure DevOps Reviews

The ability to interact with various other Azure services like for a deployment or using CICD was very helpful because when we leverage it for Azure IT helps. There's no CICD pipeline available. They provided us with some of the plugins to deploy that onto the Azure IOT edge.

They do very frequent releases, there's a complete change in UI kind of stuff. Sometimes it feels like they change it too often. They fix issues and add new features quite regularly which is good. 

They leverage a lot of new features, new features get released frequently, and sometimes the change management on our side is a bit complicated because we'll see something and there's an entirely different way how it is presented. You need to get it all working again.

Previously we asked them for more analytics on top of what they already had so that we could look at it comprehensively and see how the projects are progressing. They implemented these changes for us. 

It's stable. It's good. If there are some features missing we connect with the Microsoft team and then they get it developed and we utilize it.

It is very scalable. We use it for quite a lot of projects including running the data and all that stuff. We do quite a lot of analysis and analytics on top of that.

We have hundreds of users using this solution.

We don't really use technical support for incidents but more for developing new features. 

I've been using Microsoft based solutions, like VST and then like before that DSS. It was a natural progression from VSTS into Azure DevOps.

The initial setup is straightforward. We've been using Microsoft products for a while. 

It's a good tool, quite rich, it has a lot of features, and quite a lot of analytical capabilities which are built on top of it so that you can see how your projects are going and all that stuff. It's a good tool.

I would rate it a nine out of ten.

Agile scrum project management of a software product in a start-up company. We are a team of 11 people located in different countries.

We have team members in different locations of the world. Azure DevOps is the main communication tool between the product owners, UX designers, and developers.

Its configurable dashboard offers various display options for the stakeholders of the project.

• Dashboard
• Query
• Sub-tasks configuration
• Extensions library
• Visual Studio and other MS product integrations.

• It would be better to have a free-text query editor. 
• Product management/roadmap planning features are missing.
• Parent Column is added in listings and we expect to see it in queries as well

Refreshing the browser is needed when a data is updated. I am expecting Microsoft to prepare an Azure DevOps application running on PC and downloaded from the MS app store.

It is easy to use if you are already familiar with Microsoft products. 

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.

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.

The two most valuable features are Azure Pipelines for DevOps automation, and Azure Test Plan for test management.

It is quite easy to create a pipeline, from continuous integration to automated testing, to continuous delivery, performance testing, and continuous deployment. It's graphical representation and tools are easy to use.

The automated testing in DevTest is the big advantage of Azure DevOps.

Non-functional testing such as security testing, penetration testing, and performance testing could be improved. 

This Cloud solution is very stable.

We have approximately one hundred users, the majority of which are developers. There are some project managers and team leads, as well as different levels of management who present to stakeholders.

Currently, two or three of our development teams use Azure DevOps. In the future, we plan to include five more teams. This will grow the number of active users from one hundred to two or three hundred.

I have not used Microsoft support directly. We have an internal support team that is dedicated to Office 365, Azure DevOps, and other Microsoft solutions.

Prior to this, we used Team Foundation Server versions 2017 and 2018 on-premise, and it was a stable solution.

We also used the Atlassian stack, including Jira, Bamboo, and Confluence, all on-premise. The problem is that the on-premise version has an expiry. We moved to a cloud solution because it is easy to support, easy to upgrade, and easy to stage our products. It is distributed between our offices, as we have development teams split into different locations around the country. The cloud-based solution is the best way to integrate our development effort.

I have also worked with HP ALM/Quality Center in the past.

The initial setup for this solution is quite easy.

Our internal DevOps team handled the implementation.

I have worked with other products, and this is the best solution in the market in 2019.

Deployment of solutions on Azure DevOps is a perfect way to provide Disaster Recovery and High Availability. This is a straightforward solution, and I would suggest not wasting any time looking at others.

Right now, this is the best solution.

I would rate this solution ten out of ten.

I like the management features and the user interface is very friendly.

It is not clear what features have been added or enhanced since the last version. My customer used a previous version and it did not meet their expectations, so clarification with respect to the new version is needed on their website or other venues.

I would like to see more customization available to the administrator. You need to change the workflow of the end result.

I did not load the application heavily, but it was stable.

I only tested this solution with a single user. I think that it is scalable, as long as you increase the resources as you move to a larger scale.

I have not been in touch with technical support yet.

The initial setup is very simple.

I performed the setup myself, on my laptop.

I would advise someone considering this solution to use Microsoft because it is very user-friendly, it can run on small levels of applications, can be calibrated to the application, it can be scaled to a larger scale, from small scale to larger scale. It's very stable, you just need to increase the receptors if you need to scale to a larger scale. 

I would rate this solution a nine out of ten.

Full DevOps suite.

Allows for source control and CI/CD pipelines while linking back to the work items on the Kanban board.

CI/CD pipelines and repositories.

Information to make it easier to choose items from the marketplace (like MS verified), etc.  Otherwise, every item requires a full InfoSec review.

• 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.