Microsoft Azure DevOps Reviews

I use the solution in my company to mostly build CI/CD pipelines.

The benefits from the use of the product in our company stem from the ease that the tool provides when working with different teams. The product is also helpful in assigning tasks to team members easily. Following step-by-step processes, including testing and integration of the testing phase, all the other areas are easy with the use of the tool.

The product is easy to use. There are many options to choose from in the solution. Working with different teams in my company becomes easy when everything is integrated into Microsoft Azure DevOps.

The tutorials for building pipelines are an area that is a bit technical for a beginner. I would want the product to have some comments on the pipeline side to help beginners understand more about the solution.

I have been using Microsoft Azure DevOps for around 6 months.

It is a stable solution. I did not face any issues with the tool.

The product is scalable. That would already work with third-party platforms. In the future, I believe that the solution will be integrated with other platforms.

Around five to six people in my company use the product.

The product is deployed only at a single place in our company.

The product's initial setup phase was not complex, especially since the work items are mostly descriptive, making it an area that everywhere can use easily. The CI/CD part is a bit technical. One can get a hold of the CI/CD part over a period of time, so I don't think it is a difficult task.

Our company's team handled the product's rollout phase. The rollout phase was divided into parts. A single person did not carry out the rollout phase. I only took care of some of its parts. I cannot tell the exact time taken by our company to deal with the product's rollout phase.

My company utilizes Microsoft Azure DevOps for continuous integrations and deployments of CI/CD workflow since my company uses IaC. My company uses pipelines for continuous integrations. Moreover, one of the teams in my company uses the tools available in Microsoft Azure DevOps and various work items in it to integrate into the project.

My company utilizes Microsoft Azure DevOps for project management and collaboration across the software development lifecycle with the help of work items, like Azure Boards, which is a necessary part of team management. The task assigned to our company's team members is integrated into Azure Boards.

The feature of Azure Repos I find to be the most effective for source control management stems from the fact that it is integrated with third-party platforms, like Jenkins and GitHub, making it an option that is very usable in our company's environment.

I won't be able to comment on the product's reporting part. Our company's project manager takes care of the product's reporting part. To date, I have had no concerns with the project visibility area in the product. Working with Microsoft Azure DevOps is great because it provides top-notch integration capabilities.

Microsoft Azure DevOps has improved the productivity and efficiency of my company's development team. In the past, when my company wasn't using the portal in Microsoft Azure DevOps, there used to be no continuous integrations. After my company started to use Microsoft Azure DevOps, we got to know about the CI/CD pipelines. Now, it is easy for us to make changes in the code, and simultaneously, the code starts working at the production end. My company majorly uses the solution for CI/CD pipelines.

Speaking about the integration part, I would say that my company mostly works with Terraform as it is a scripting language. Along with Microsoft Azure DevOps, my company has only worked with Terraform for now. Though my company works with other platforms, like GitHub, we haven't done projects with GitHub. Working with TerraForm and Microsoft Azure DevOps has been great.

The tool's maintenance part is great. I did not face any issues during maintenance.

I recommend the product to those who plan to use it.

I suggest others watch some online tutorials before purchasing the product, as it can help them get the basic information related to the solution, making it easier for them to use it.

I rate the overall tool a nine to nine and a half out of ten.

It is for all the DevOps functions, such as managing the deployment of the code to the production environment. 

It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues.

Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications only the repository is done, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working.

I have been using this solution for more than two years.

It is stable. It is also good performance-wise. There are no issues.

We have more than 800 developers who are using this solution, and this is only a portion of the company. Across the company, there are many groups, and we have more than 2,00,000 employees. We are using DevOps across many customer projects and environments, and more than 50% of our projects are on DevOps.

Their support is good.

It is a cloud solution, and there is no installation. You just start using it.

We have one or two admins per project for deployment and maintenance.

I would definitely recommend this solution to others. They can go ahead and use it.

I would rate it a seven out of 10.

We are using Microsoft Azure DevOps for the repository for Git.

We are migrating to the on-premise version of GitLab. We do not use any advanced tools. We are planning to do more with DevOps and are evaluating other tools to incorporate in our process of development.

We use the functionality of Git for our development. We do not use the other tools that are integrated into the DevOps. We use it because we have an enterprise agreement with Microsoft.

Microsoft Azure DevOps integrates well with other components, such as Synapse, which is a data warehouse tool of Azure. It is a framework platform for BI and integrated with other tools, such as Power BI.

I have been using Microsoft Azure DevOps for approximately three years.

The solution is stable.

There are other solutions available that are open source and free, such as GitLab.

We are switching from Microsoft Azure DevOps to GitLab because we have the infrastructure and we are migrating part of our service to on-premise which includes our VMs. We decided to install GitLab because it is open-source, free, we can install it in-house, and we have some members that have experience with that product. We are now starting to migrate some projects.

I would recommend this solution to companies that use the incorporated services provided, it is very good to adapt as a DevOps tool.

I have not used the solution extensively enough to give the solution a higher rating.

I rate Microsoft Azure DevOps an eight out of ten.

We use Microsoft Azure DevOps to maintain our project. We create a project in a good DevOps, and then we add the backlog items. The product owner adds the backlog items, and then the development team. The repository is also built into that. We have a private Git report for the project. Under reports, we can create a repository for the big projects and maintain the source code. 

Developers can commit and make a full request. For example, configure Jenkins, reconfigure Jenkins with the repository credentials, and then use it for linking. We don't use the pipeline available to us, and we use Jenkins for CSC.

In our organization, Microsoft Azure DevOps helps senior leadership go in and check the project status and how much effort has been put in by the development team. They can also pick, choose, and add features to be used by the development team. It's like a backlog management tool that helps improve and support projects. 

It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful. 

Integration and plugins for other tools could better. Like if you want to integrate the DevOps with other tools that are in the market. This could be for the engineering tools to check code quality, application security tools, and DevOps dashboard tools. 

They could also make the implementation easier. The test plan also has basic features that are not user-friendly. It should also have integrations with test automation tools. We need a test plan, automation testing, and EA-based testing.

We have been using Microsoft Azure DevOps for more than four years.

We haven't got any issues with the technical support area.

The initial setup is very straightforward. 

Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users.

I would recommend this solution to new users if it's a simple project. If you want JIRA, you'll need to have JIRA software for backlog management. 

On a scale from one to ten, I would give Microsoft Azure DevOps an eight.

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. 

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. 

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.

We use Microsoft Azure DevOps for applications that analyze data and the data scientist creates the test data for the manual and automatic application tests. Here in Europe, we need anonymous synchronization of all data for testing.

We create special applications for creating data for direct tests.

Microsoft Azure DevOps has been very good for creating pipelines, and all the solutions for creating task management for developers and for the business. 

All of the tests of the applications are done on the mobile or web interface and it could be improved.

The connection to Power BI could improve. Power BI is a very good platform for reporting and presenting processes, but a good engine does not exist to present the process development in time in Power BI. It's a typical business reporting tool.

I have been using Microsoft Azure DevOps for approximately one year.

Microsoft Azure DevOps is highly stable.

There are two options to build. The first option is to build in the cloud, which is very stable but not quickly. The second is to build the systems in the local networks. 

We have 5 to 10 people using this solution in my organization. We have three DevOps and the others are the QA cluster.

We do not use support from Microsoft, we have not had any problems.

The initial setup of this solution was complex. Every part of the implementation was difficult.

For us to implement our production it took approximately 10 to 20 sprints. One sprint is two weeks.

We require a three-person team for the maintenance and support of the solution.

The price of the solution is expensive.

All people who work on projects must have good staff in development in .net, and need to have certificates. The minimal certificate is the AZ-204 Azure developer, it is obligatory.

I rate Microsoft Azure DevOps a nine out of ten.