Microsoft Azure DevOps Reviews

We use Microsoft Azure DevOps for our source control, change request management, and a small amount of Wiki.

Microsoft Azure DevOps has helped our organization from having completely automated builds. The developers can send their own code to QA without needing a release manager or lead or IT person moving the code over.

The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow.

I have used Microsoft Azure DevOps for approximately one year.

Last week the builds did stop working for some unknown reason, and then started again. Most of the time the stability is fine, but there are occasions when there's a problem on Microsoft's side, where it creates problems for us.

The solution is scalable but you have to pay for it.

We have approximately 40 people using this solution consisting of developers, QAs, and product owners. We are extensively using this solution in our organization.

I wish the dashboards and the release process were integrated better. The use of Kanban dashboards could be a lot better. They don't have a Kanban dashboard. They have a dashboard with one sprint but it's not exactly the same as a Kanban dashboard. You are not able to do much with them. 

We have not needed to contact the support.

The installation is straightforward. We can create a whole new organization in less than a day.

We did the implementation ourselves. I do most of the maintenance but it is mostly maintenance-free.

There are additional costs for some functionality, such as increased scalability.

My advice to others is for them to do their research before implementing this solution.

I rate Microsoft Azure DevOps a seven out of ten.

I primarily use the solution for more of an end-to-end pipeline. 

The integration with the full end-to-end suite is great. The integration between the Kanban all the way through, including the traceability all the way through to the other end is very useful. You're able to test and you have your repositories and the ability to integrate with pipelines. 

There are great automation tools. 

The solution is very stable.

The scalability is quite good.

Individually, the components and not quite as good as others in the market. For example, the DevOps test plan isn't quite as good as a Micro Focus ALM QC. That said, when you integrate it into that entire pipeline, it's better.

Microsoft initiates changes so quickly, it's hard to keep up. It would be helpful if there was more documentation and more training to go with all of the changes. Chris:

With Microsoft, I would prefer to have more test plans. It's very difficult to find individual test plan module training.

The solution is quite stable. It's pretty reliable. there aren't bugs or glitches. It doesn't crash or freeze. 

The solution is very scalable. It's easy to expand.

I've had no problems with technical support, however, I'll get put in the fast-track programs. I always get very fast responses. 

I also use Micro Focus. For older style waterfall projects, it's best to go with Micro Focus probably, barring pricing and other consideration. However, in an agile environment, a Microsoft Azure-based product such as DevOps is great due to the pipeline and the whole integration end-to-end is just better.

I'm also familiar with Jira, which has better features in various areas. The problem is it moves so fast and new versions are always coming out and it can be hard to keep up.

I'm an implementor. I work with a variety of clients. 

I'd rate the solution at a nine out of ten. It's great for agile and we've been pretty happy with it as an end-to-end solution. 

If you're moving into an agile CI/CD, DevOps is the way to go. If you're still thinking about old manual start testing, Micro Focus is probably the way to go. That said, more standalone manual testing is better supported by Micro Focus.

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.

The company that we were working with was in development using a Microsoft platform. We used Azure to integrate the complete project management and DevOps work.

This solution works with other Microsoft solutions pretty easily. It was easy to integrate everything into all the other tools that we were using. It integrates very seamlessly.

I have not come across information for integrating this solution with others, such as ServiceNow. I am not sure if the integration would be straightforward to implement. There should be readily available information to accomplish these integrations.

I have been using the solution for approximately two years.

The project that we were using the solution for was a small implementation, I cannot fully comment on how scalable it is. I did not have enough data to comment if it was good. However, we did not have any issues.

The customer support is good.

The installation time of this solution depends on the environment it is being implemented in. We had a couple of projects that took around two weeks of implementation. This included the whole integration of the DevOps and everything together.

We had an expert that did the implementation of the solution for us. He did not face any problems.

There is a license for this solution.

We plan to continue offering this product to our customers and I would recommend it.

I rate Microsoft Azure DevOps a seven 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.

We are a reseller of solutions and provide maintenance to our customers. Azure DevOps is one of the products that we have experience with.

Our customers use this product when they want to enter the DevOps space and integrate or consolidate all of their existing tools. It allows them to communicate seamlessly between development, their operations, and other team members.

This platform provides a large span of tools and technologies.

I would like to see better integration and collaboration between tools. There are different companies offering different tools, and how well something is integrated contributes to the completeness of the solution. 

The platform needs to be updated because things are still in the process of change.

I have been working with Microsoft Azure DevOps for almost three years.

We have had no complaints about stability.

Scalability has not been a problem.

We have not been in contact with technical support.

The initial setup is complex. It really depends on those who are using it in the company and exactly what they're utilizing with respect to tools. It also depends on whether they want to integrate it.

We have an in-house team for deployment.

The price of this solution is fair.

There are a lot of different tools on the market such as Jira, so I would look at DevOps as one option and how it is going to handle things in your environment.

I would rate this solution a six out of ten.

We are using this solution for workflow management, especially when using a Kanban board to monitor the small assignments. Also, some programming for some of the disciplines. It's still in its infant stages.

It's a complete solution that has everything you need. 

It covers all of the development workflows to the initial planning, testing, coding, and even to launch the subsequent feedbacks.

Also, it has marketing reports.

It's very promising. They are very well positioned to take over some pretty heavy contestants in that area.

I think that they have some menus there that are not very well placed. For example, I was searching for some extensions in the marketplace and I couldn't find my way back to the console. It's not very well designed.

The general user interface is nice. It's intuitive, but I had the luck to discover something that is not very well designed. The fact that I can't return back to the console is very strange. I couldn't find my way back. I had to log off and log on again and get back to the console in a very awkward way.

I have been using this solution for a few weeks.

We are using the latest version.

It's a stable solution.

As per the documentation that I have read, it's pretty scalable. My brother, who works with this solution practically every day, says it's scalable.

We plan to continue using this solution.

I have not yet had any experience with technical support.

Previously, I just used GitHub, so just Version Control for code and not much more. 

I used also their integrated development environments including Visual Studio Code and Visual Studio. These solutions are built by Microsoft.

It's straightforward. With the cloud solution, there is no installation.

I could create the main console for the project very quickly, with just a name and description and the rest is the default.

This is a product that I can recommend to other users.

I would rate this solution an eight 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.