Microsoft Azure DevOps Reviews

We adopted the SAFe Framework, and more than 10 teams are using the process or workflow template from Azure DevOps for SAFe. Also, we're currently using DevOps for future planning and backlog management following the scrum approach on the team and coordination level. The company plans to extend this with Lean Portfolio Management. 

Time to Market: Teams deliver more in less time.

Azure Pipeline is the most valuable feature.

The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension.

I've been using DevOps for about three years.

DevOps is very stable.

DevOps is scalable. We have about 65 users working with it, including the product manager, product owner, scrum master developer, tester, line managers, and architects. 

We haven't experienced any significant issues so far, but any issues we've had were fixed fast, so I would say I'm very satisfied with the support.

Positive

We were using Jira, but we switched to DevOps. It was a strategic decision to reduce the complexity of the toolchains. We wanted a Microsoft solution, so we chose Azure DevOps.

Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements. We did it ourselves in three days. Since we used the default templates,  we didn't have to change the standard Azure DevOps services. Two people are responsible for deployment and maintenance: DevOps engineer and Release Train Engineer

I rate Azure DevOps seven out of 10. DevOps isn't so easy. In general, the solution is straightforward and suits our purposes, but it's a little bit tricky to customize the workflow. It's simple to implement the SAFe Framework, but it's not easy to customize compared to Digital.ai Agility. There's a huge gap.

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 it for planning, pipeline management and testing, as well as using it as a CI/CD tool.

I like the agile management of projects, running stand-ups and the like. The pipeline management feature is great.  

We'd like to see an improvement in reporting across multiple projects. The same applies to improving program visibility so that project managers can get that pane of glass to assist with their work. It would be a big win for a lot of users as well as a good addition to the tool. 

We've been using this solution for close to four years. 

The solution is stable. There are still the occasional issues but on average it's very stable. 

The solution is easily scalable because it runs on the cloud and everything is managed by Microsoft. We don't do anything in terms of increasing capacity so when more users are added the increased capacity is automatically managed. 

We haven't made a lot of calls to technical support but when we have their response has been good and quick. 

We have a DevOps engineer who carried out the implementation for us and I believe it was relatively easy. 

I rate this solution eight out of 10.

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 the solution to store all our source codes. It's a solution that stores everything. We are an in-house development and we produce a lot of codes.

We also use it to control our development process. We follow some methodologies. Every every team has a different methodology, for instance, Chrome, Agile, et cetera. The whole process from the planning process until we deploy the solution, everything is controlled by DevOps.

The solution is very good at automating various aspects of the DevOps process. You can automate almost everything. You don't have any human intervention. It's almost automatic. As long as you finish your code and put it in, the software gets the code and tests it. If it is okay, it will go ahead and integrate it and put it in production without any human intervention. This is excellent.

The tool allows you to connect with many external tools. You can improve the whole process that way. We use a couple of things, however, there is a plethora of things you can put together in your solution.

The initial setup is very easy.

Despite the fact that you can automate most of the things, you still have to produce some scripts. There are things that are not very user-friendly. The tasks are achievable, however, it's not easy. You have a lot of steps until you can get the thing automated.

In the past, Microsoft DevOps was integrated with Microsoft Project. Out of the box. Right now, it's no longer that way. That would be interesting to have.

It would be great if I could integrate with a human resource type of software that could control timesheets.

I've been using the solution for 15 years now. It's been a while. It's well over a decade of experience.

The product is extremely stable. We've used it for 15 years and haven't had any serious issues. There are a few bugs or glitches but nothing tha can comprimses the day to day operation, and they usually fixed in the next release. It doesn't crash or freeze, though sometimes gets a bit slower due to databes overheadd, so maintance has to be done. It's reliable.

We are a small team, and therefore we don't need to scale. However, I've heard both that it grows 10% a year without issue and that it scales very easily and very well. As far as I know, a company can scale it if they need to.

We have between 50 to 70 people using it, including staff and managers, et cetera.

I have used technical support a couple of times. Typically, it's good. It's usually a couple of hours and then, they answer you. Nevertheless, you can go to the online site and most of the time you can solve the problems just by reading. They have a lot of documentation available. 

That said, when we dealt with them directly, they were pretty fast. I'd say we are satisfied with their level of service.

The initials tup is not complex. It's a very easy, very straightforward process. A company shouldn't have any trouble with implementation. It only takes a couple of hours. It's pretty quick to deploy for DevOps purposes.

We are just a customer.

We intend to move from on-premises to the cloud next year.

I'd recommend this solution. It's a worthwhile investment.

I would rate the solution at a nine out of ten. We've been quite satisfied with it overall.

We are using Microsoft Azure DevOps for tracking the requirements and tracking the issues.

Any issues that we have, are tracked and logged.

Also, we check the developer's workload.

It can be used for different purposes as well. For example, it can be used by software companies and different software teams for collaboration.

What I like the most about this product is that it's free and it's secure.

You can easily assign it.

It integrates well with other Microsoft products, such as Outlook.

If we experience a login issue, it sends a notification to one of my developers and you also receive an email notification, ensuring that there is no way that a developer can miss working on it or miss seeing it in emails.

The user interface could be improved.

I have been using this solution for approximately two years. 

It's a stable solution, we have not experienced any issues.

We have not had to scale it, as we have a very small team with only four members who use this solution on a daily basis.

We have not had to contact technical support. There hasn't been a need, it's very simple.

If you have any issues, you are sent a link through email, you click on the link to address your specific requirements and close it.

You will receive an email notification to confirm that the case is closed.

Previously, we were using Microsoft Excel. We decided to use Microsoft Azure DevOps because it allowed us to assign tasks and get a notification.

The initial setup is simple.

It was easy to deploy and within a day, I was able to learn it and work on it.

I did not use a vendor or an integrator, I did it on my own. It's a Microsoft product and we all use Microsoft.

Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects.

I would recommend this solution. It's a good tool and it's free.

Instead of spending money on premium tools, you can at least start with Microsoft Azure DevOps and then upgrade it slowly.

You can learn how to use this tool in less than a day.

If you have Microsoft 365, this comes with it for free.

It doesn't require any maintenance.

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

All of the features related to release management are very good. We use release management and dev management, and the dashboard is good. The ability to specify multiple platforms in release management, by using Docker, is valuable.

Better integration with the Linux operating system would be an improvement for this solution.

I would like to see more third-party plugins; by comparison, the open source solution, Jenkins, has thousands of plugins available.

The Wiki for this solution is not very good.

There is a problem when you want to run a release pipeline for an organization that needs enhanced security. There is no option to configure a dynamic login for a station that is running the tests. The only solution in the platform is to configure an agent that uses a fixed username and password login. There is no option to change the username or password for the login dynamically. If I want to run multiple tests, with different users, then I cannot do it. When it comes to running tests, it needs an option to use different users or authentications. This is a very important feature that is missing.

This solution is very stable.

Scalability is not particularly relevant. It depends on what kind of scaling you want to do. Generally, it has very good support for scaling.

There are hundreds of developers using this solution.

We only had one issue, and I would rate their technical support at medium, based on that experience. The issue was related to shrinking a database, where it was not working well. It took a long time for Microsoft support to fix the problem.

We did not use another solution prior to this one. However, I use other tools in conjunction with Azure DevOps. One of these is Jenkins, for CICD, and I also use the Atlassian Suite.

The initial setup for the latest version was very straightforward. The upgrade was quick and lightweight.

I handled the implementation on my own.

This is a solution that I would recommend.

Azure DevOps is a leading platform, but some things can be better. 

I would rate this solution a seven out of ten.

Microsoft Azure DevOps is used for source code versioning, issue tracking, documentation storage, and sharing.

My team likes the integration that Microsoft Azure DevOps has with GitHub and Microsoft Teams. The solution is well integrated with other Microsoft tools in one place, it is very good.

Microsoft Azure DevOps could improve by having better integration with other email servers.

I have been using Microsoft Azure DevOps for a few years.

Microsoft Azure DevOps is quite stable. When we were configuring some continuous integration pipelines, we had some issues, but it was not a large issue.

The solution is scalable enough for what we use it for, we have small teams of approximately 25 people. It's more than enough right now.

We didn't have many incidents to contact the support about. However, they were decent.

I was previously using Jira.

The initial setup is straightforward. The configuration of Microsoft Azure DevOps could be better. The documentation needs to be improved.

The implementation and maintenance of the solution are done by our DevOps department.

We do not pay licenses for this solution.

I would recommend this solution to others.

I rate Microsoft Azure DevOps an eight out of ten.