Microsoft Azure DevOps Reviews

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.

We use Azure DevOps as a way to organize our development. As a means of facilitating application deployment from pre-production to production. We use it to organize our environment and identification systems. If you don't have the power or permission to do something, you can't do it. With Azure DevOps, we can create profiles that developers can use right away to go from pre-production to production.

Microsoft Azure DevOps is a very useful system. Before using this solution, we had to deploy our applications, from pre-production to production, manually.

We are entry-level users when it comes to Azure DevOps. We haven't had to set up anything complex as of yet. So far, we are very satisfied with this service.

This solution is very stable. On a scale from one to ten, stability-wise, I would give it a rating of nine.

I've never had to scale it up or down, so I can't comment on that.

If we experience any issues, I am not the one who contacts support. Other team members handle that.

We had some hands-on help from Microsoft engineers with deployment, so for us, it was straightforward. 

Overall, on a scale from one to ten, I would give this solution a rating of nine. If Microsoft Azure DevOps were more accessible in south Brazil, I would give it a rating of ten. Although, the reason for this may be due to the price.

Our only use case with DevOps was for integration with ReadyAPI.

The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests.

Something that could be improved is the initial setup with the integration of ReadyAPI.

I used this solution for six months.

Stability is fine. I was getting some errors, but that was due to my side of things.

Scalability is fine.

I would rate this solution 6 out of 10.

I did have some issues due to our organization, but it would be different for everyone. My advice is to reach out to support if you have any problems.

I am familiar with the VSTS environment, grading tests, plan, and tracking dashboard activity.

In my previous company, we used this solution to create test cases, test reports, test execution, task boards, and we use the dashboard for the product activity.

I really like the Microsoft DevOps survey.

I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix.

I have never seen a table or a Matrix in DevOps for traceability for either software or hardware upgrades. I am not aware of whether the website has these capabilities.

I had planned to recommend this product to my current company but the traceability is missing and could not consider it.

I have been using this solution for three or four years.

It has some bugs that we reported and they have been fixed, which is good.

I would rate Microsoft Azure DevOps a nine out of ten.

I'm using it for specifications of the requirements, for example, or a user for research specifications. I'm also using it to build up test cases right now.

Overall, the solution is pretty good. It fulfills most of our requirements.

The stories and test cases on offer are great.

The initial setup was pretty self-explanatory. It was straightforward.

The pricing seems to be reasonable.

The solution needs to add the capability for building live documents. 

I would like to see a bit more project tracking. There should be more Kanban views. There maybe should be a few more reports. If the reporting was increased a bit, it would make it so that you can check a bit more information around the progress of the project. That would help with project management and progression. 

I've been using the solution about twice a week for the last few months. It hasn't been that long and it's not a daily occurrence. In total, it's maybe only been two or three months.

So far, I've found the solution to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable.

We have about 3 people using the product currently in my company, and about 30 customers.

I've never had to contact technical support. We haven't faced any issues that would require us to. Therefore, I have not idea how they would be. I can't speak to how knowledgeable or responsive they are. At this point, I have no insights to share.

I have worked with other DevOps tools previously. I've worked with Jira and Polarion in the past. I haven't necessarily worked with them together or consecutively. It all depends on individual project requirements. 

That said, I am not using Polarion anymore.

The initial setup was not overly complex. It was pretty straightforward. A company should have too much trouble with it.

The pricing of the solution seems to be pretty good. It doesn't strike me as being too high.

I'm just a customer and end-user. I don't have a business relationship with Microsoft.

Overall, I would rate the solution at a seven out of ten. It's been okay so far. We're satisfied with the solution overall.

We use Azure DevOps for managing our workflow, as well as the CI/CD.

We use the CD/CD for all of our deployment lifecycles.

The CI/CD portal is very user-friendly.

The platform is very easy to manage. It is easy to manage repositories between the business users and corporate users.

Fields can be customized and the reporting is good. The APIs that are exposed can generate management reports.

The most valuable feature is the test manager. 

Integration is easy to do. The single-sign-on facility is there in every aspect including Azure DevOps, Active Directory, our portals, and all of our development sites.

Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves.

We would like to have an indicator of the percentage of occupancy. Suppose a person is working on two different domains, and we have 70% on one project with 30% on the other, it should be able to report that. As it is now, we have to manually enter that data. If this functionality were provided then it would make it easier for users.

We have been using Azure DevOps for the past two to two and a half years.

We have had issues, usually related to the APIs, but the support team has always helped us to resolve them.

The Microsoft support team is prompt to respond and very good.

The price is cheaper than Jira and some of the other competing tools.

Overall, this is a good product and if the Gantt chart and occupancy reporting features are added then it will be the most powerful one in this space.

I would rate this solution an eight out of ten

As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there.

Apart from that, the reporting structure could be provided as well. Depending on how the company is using the technology, there may be other Microsoft tools that are better so that the integration and reporting will be easier.

I've been using Microsoft Azure DevOps for almost five or six years.

It is stable, and we have had no issues with it.

It is scalable.

I would rate this solution at eight on a scale from one to 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.