Microsoft Azure DevOps Reviews

We have separate DevOps processes for different teams. We're implementing agile processes, so we have cells for each product, and each cell has its own DevOps process. This means we have a DevOps process in GitHub, GitLab, and another tool. We have lots of costs and can't share experience between teams.

The idea was to unify everything in one product to ensure that we standardize DevOps practices on the same tool to have better knowledge and expertise and focus on a specific tool.

We had a lack of governance over DevOps processes, so we had some quality issues in the end when we released the software products. DevOps has helped to resolve those issues.

Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development. 

I think Azure DevOps could improve the traceability or business intelligence about the execution of DevOps processes. 

I've been using DevOps for three years.

Azure DevOps is scalable. 

We have good people with a lot of experience in DevOps, so it's not complex for us. The most significant difficulty in adopting the tool was changing our past processes to move to the standardization model we defined with Microsoft DevOps.

We have a yearly agreement with Microsoft to cover the different companies.

I rate Azure DevOps nine out of 10. I would give it a perfect 10 if Microsoft offered personalized support. Sometimes we call Microsoft with requests, and it would be nice to have personalized processes with our specialized services.

We have two different approaches for products. One is to support products that we provide our customers. The other is creating a digital transformation strategy for new products. We are using DevOps in the latest products, and in the future, we are going to grow with support for products we have produced in the digital transformation. This is part of our roadmap to implement DevOps in all the processes in every technological area of our companies.

We are a team of 12 consultants specializing in this solution. We have customers with approximately 200 users each, and we have been able to reduce our customers' deployment time by using Azure DevOps or TFS.

Additionally, our customers have been able to measure and improve their development process, by generating some KPI's as 'average defect fixing time', 'effort deviation', and 'velocity' among others, due to the continuous use of Azure DevOps.

The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS.

The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project.

Additionally, I would like to see more powerful dashboards that could be used instead of Power BI. Azure DevOps or TFS does not support graphics from hierarchy queries. It would be powerful to have because some customers don't have Power BI licenses.

We have been working with Azure DevOps or TFS for the past 11 years.

It is totally stable.

The documentation is good and thus, we have not had to contact technical support very often. However, when we have escalated an issue to technical support, they have been good.

The initial setup can be straightforward if the consultant is knowledgeable.

The pricing is very competitive because of the whole development cycle by Azure DevOps. You don't have to buy and integrate several different tools.

Azure DevOps or TFS is a very good tool for development teams. It's easy to use. However, you would need the help of a consultant who has a lot of experience with the tool. This is because the tool let's you do things in many ways, but not all of them will be the right way to do it. It would be better to invest in the services of an experienced consultant.

Overall, I would rate TFS or Azure DevOps at nine out of ten.

It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable. 

We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results.

We would like to have templates for work items. They are available in the Azure DevOps services on the server, but they are not available in the on-prem solution. We are using an on-prem server, and we are using version 2020.1119.

I have been using this solution for almost four to five years.

It works well. There are no issues.

It is easy to scale. In our organization, some teams are using it, and some teams are not using it. We probably have 80 to 100 people.

Their technical support is good. We haven't faced many issues. As far as I remember, we have had only one issue. We raised a ticket for that, and they resolved the issue.

I have also used Jira. We have more control over Jira than Azure DevOps, but we are using Azure DevOps for our technical side because our VMs and build pipelines are on Azure. So, it is better for us to use one solution rather than using multiple solutions.

It is straightforward. It is not that complex.

In terms of maintenance, we only do maintenance when we have new upgrades. Other than that, we don't need to maintain it much. We have optimized the TFS and Azure DevOps database, and we have done indexing and optimized it. It is pretty good.

I would rate Microsoft Azure DevOps an eight 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.

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.

There are many valuable features including dashboards, sprints, queries, pipelines, artifacts, and the cover repository.

I would like to see improvement in the metrics and the dependencies. I would also like to see the option to define the dependencies within all teams in the same project. We have a team level, a program level, and a portfolio level. For the metrics portion, I would like to see some drag-and-drop features for the dashboards that would make it possible to aggregate data from the different teams.

The plugin for the iteration walls can also use improvement as it does not work well.

I have been using the solution for three years.

It is stable. Whenever there has been an issue the solution slowed down but there was never any data loss.

The solution appears to be scalable.

I am not familiar with the initial setup.

The implementation was done in-house.

The cost is reasonable. For the basic license, it is around five euros per month. 

I rate the solution nine out of ten.

If someone is considering developing and deploying the infrastructure in this solution, then using this tool is perfect because it's fully integrated with the pipelines and with a server core repository. When you are building infrastructure, then you are able to use the same tool to deploy the server, deploy infrastructure, and all within a few minutes. This gives you access to the same tool, task management, dashboards, pipelines, and the server core repository. So everything you need to develop a server is integrated into the same tool.

We use Microsoft Azure DevOps for CICD, and to organize it in order to visualize the ongoing work.

It allows you to save time while also providing a governance visualization of ongoing activities and transparency.

The most valuable feature of this solution is that it saves time.

The price could be reduced. It is expensive, especially when it comes to infrastructure.

The integration could be better. Being more technology-agnostic through ease of integration would be beneficial. Once you start working for Microsoft, you are frequently tied to Microsoft.

I have been using Microsoft Azure DevOps for the last ten years.

Microsoft Azure DevOps is a stable solution.

Microsoft Azure DevOps is scalable.

I would say the technical support is fine, but I have not had any trouble with the solution.

I have some experience using Jira.

It is very expensive in comparison to others.

As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users.

I have recently researched Jira, Microsoft DevOps, TFS, and Micro Focus.

Mostly, because of the pricing, I would rate Microsoft Azure DevOps a seven out of ten.

We are using Azure DevOps for continuous integration and continuous deployment.

Microsoft Azure DevOps has helped the developers a lot and we are deploying process changes very frequently and simultaneously. A lot of my team members that are developers are updating the code in parallel using Git. Additionally, Microsoft Azure DevOps is providing a very good approval mechanism. Overall it is benefiting by creating efficiency in production deployment and applications, our new releases are running well. The security of secured is good.

We are facing a lot of issues in the development of containerized solutions. We are facing a lot of challenges in this area. They could make the process simpler.

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

The technical support from Microsoft Azure DevOps is good. Whenever we have raised a ticket with priority, we had a very good response from the technical team. My experience with Microsoft support is very good.

The integrations of Microsoft Azure DevOps are good and the implementation is not difficult. The testing of the solution went well.

I have seen a return on investment from using Microsoft Azure DevOps.

We have spread the knowledge about Microsoft Azure DevOps to a lot of our customers. We have organized a lot of training sessions because we are Microsoft's gold partner. That is why we promote all the tools and technologies which are part of Microsoft and we're also using them.

I rate Microsoft Azure DevOps a nine out of ten.