Microsoft Azure DevOps Reviews

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

I have many microservices, and I am using Azure DevOps to deploy my microservices and build a global platform for payments.

Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release.

It should have security features for scanning the code and checking it for vulnerability and security. Currently, I am using other tools for this. It should also have integration with other tools to improve security.

I have been using this solution for two years.

It is stable.

It is scalable. Currently, we have 400 users, and they are DevOps engineers and developers.

They have helped me with the problems. They are very good.

I have only used Azure DevOps.

It is very simple to install. Its deployment takes a very short time.

I would recommend this solution. I like Azure DevOps.

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

We implement this solution to those wanting to improve their processes to make their business function better.

Some of the valuable features are the functionality and the wide range of capabilities.

Not all companies use the same methodology which could limit the use of this solution.

I have been using the solution for approximately two years.

The stability of the solution is great.

I have found the scalability good. We have approximately four specialists and ten testers using the solution in our organization.

I would recommend this solution to others if they have tools with Microsoft and the proper infrastructure because not all customers work with this methodology in the development team.

I rate Microsoft Azure DevOps a nine out of ten.

We use this solution for continuous integration. It provides us with strategic analysis. We use it to create and deploy virtual machines. In short, we mainly use it for integration and deployment.

Currently, there are five to ten of us working on conception. Soon, there will be more than 200 of us using this solution. 

The most interesting subject for me is the deployment part where you build virtual machines and enable them to learn. That's interesting to me.

As I'm in the very early stages of this story, this is a hard question for me to answer. However, I think that the integration is to some extent, immature.

Overall, so far we have no major issues to report. 

I have been evaluating this solution for roughly six to eight months. 

The initial setup was quite straightforward.

The licensing costs are reasonable. 

We also evaluated GitHub and GitLab. We actually have one deployment that is already ongoing in GitLab. 

Currently, we're evaluating both GitLab and Microsoft. We're trying to get a sense of which one is better for us. 

Overall, I would give this solution a rating of eight out of ten. 

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.

We use this solution for cloud administration, cloud infrastructure, the database, as an application server, development, and more.

I like the cloud infrastructure of Microsoft Azure DevOps.

I would like to see new features added.

My corporation is currently using this solution.

I have had no issues with the stability of this solution.

Scalability-wise, I have not had any problems.

Everything is fine with our internal customers and our corporation.

Technical support is good.

I don't have a problem with the pricing.

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

I am using it as a developer in the agile scrum area.

It has improved the team cooperation for building, developing, and releasing systems.

It is easy to use. The shared repository is useful. Everything is in one environment.

It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members.

I have been using this solution for one and a half years.

It is very stable. If it doesn't work, it is usually because of network issues.

I didn't need support from Microsoft. Any need for support was internally fulfilled by my colleagues.

I would recommend this solution. It is a nice environment for working in teams and implementing the DevOps philosophy. It provides good support for that.

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

We use the solution for performance testing in general.

One of the main features is the user interface is very good.

The user management in the solution could improve.

I have been using it for four years.

The support for this solution has been fine.

The price is reasonable for the solution.

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