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.

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.

I use it to, for example, build applications. Not just Subnet - also Java or in OGS. I deploy Windows applications and also mobile applications with Visual Studio App Center and Azure DevOps.

Azure services like serverless technology make it quicker and faster to deploy .NET applications, for example. Similarly, the Azure Portal is faster to put in services, for example, with specific functionality. These kinds of features are faster to deploy and to put in functionalities that are specific, which is great.

I like the Azure keyboard. Keyboard permits use, for example, connection streams in secret, in a safe manner. 

Sometimes I use also Azure SQL Database cloud, the serverless functionality. It's also very attractive because you can use something like a GP, like the protection of the data on the cloud. You can put a lot of information there, maybe not with banks, however, with other kinds of clients. 

The ability to have cognitive services is good. For example, I use a lot of Azure DevOps, for example, Cloud, Azure DevOps Cloud, and analytics views with, for example, Power BI on-premise if you have Power BI as a service. There is a lot of pipeline potential with Azure DevOps deploying, for example, Containers, to Kubernetes, Azure Kubernetes Service, and also a lot of Azure Container repositories and Azure Container instances. This is great for quickly deploying SonarQube in a container. These kinds of things are very attractive.

It's a pretty problem-free solution.

When we don't have some permissions, we have to research how to get them. It's not obvious. For example, deploying in order to do the connections, we need permissions for quotes or quotas. A specific quota might depend on an account. Sometimes we don't have the kind of support we need to work things out easily.

When you deploy in Yaml Pilot, for example, you need to note in Yaml how to associate the piling, the release with the word items. We need more information about how this is possible and more flexibility to make it happen. 

My organization is a Microsoft partner.

I have Microsoft certifications. I always develop in Visual Studio, .NET, or Core, and now I work with Azure DevOps and also in Azure Portal.

I deployed in a hybrid environment as the clients have a lot of things on-premises. For example, the databases I use, for example, Redgate, plus Azure DevOps, or Apex with Azure DevOps, to deploy databases. In some cases, a lot of banks prefer their data on-premise. In other cases, I deploy to Azure App Services, for example, in the cloud. Also, I see things with Amazon Web Services and telephone, like multi-cloud.

I would rate the solution at a ten out of ten as it never gives me any problems. 

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.

We use DevOps for backlogs and work items. We divide our releases into many sprints to keep our development on time, and we use DevOps to manage tasks for development or business teams.

DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams. We manage everything through this.

I want DevOps to have more automated reminders about tasks that don't need management. We don't have reminders, so a project manager must track the tasks. It's not automatic.

We've been using Azure DevOps for three years. 

DevOps is stable. 

DevOps is scalable. About 70 people use the solution on average. 

Another team handles the implementation, so I wasn't involved. I'm on the business team. Two engineers are responsible for deploying and managing DevOps. 

We pay for a yearly license. 

I rate Azure DevOps eight out of 10. I prefer Jira, but both solutions are very nice. 

Our only use case with DevOps was for integration with ReadyAPI.

The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests.

Something that could be improved is the initial setup with the integration of ReadyAPI.

I used this solution for six months.

Stability is fine. I was getting some errors, but that was due to my side of things.

Scalability is fine.

I would rate this solution 6 out of 10.

I did have some issues due to our organization, but it would be different for everyone. My advice is to reach out to support if you have any problems.

We use this solution for project management and delivery.

It is easy to use.

We are able to generate many different types of reports from Azure. It connects well to PowerBI. 

The performance is good.

They could have more reporting features added to the dashboard. There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps. 

We would like to have the same calculated reports that can be accessed in PowerBI, available in Microsoft Azure DevOps. 

We have been using Microsoft Azure DevOps for the last two and a half years.

Microsoft Azure DevOps is a stable product.

It is easy to scale. We have approximately 250 employees in our organization who use this solution.

We have contacted technical support. They provided us with a fast resolution.

We are using Azure, and TFS now. We are also planning to migrate to AWS as well.

The installation was easy.

We have an IT team of four to manage and deploy this solution.

I would definitely recommend this solution to others who are interested in using it.

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

I work as a DevOps Engineer. I use this solution as an end-user.

I definitely like the pipelines and the ease of management once you're in an enterprise. 

The controlling security, the ease of access, the free plans, and the developer plans.

I also like the licensing structure in general.

I would like there to be more seamless integration with GitHub. 

Azure DevOps seems to be targeted towards enterprises and GitHub is the ugly sister, so to speak, that you come about in the enterprise. 

There is no real interaction between the products, which is a real shame since they are both developed by Microsoft. 

Definitely, there should be more integration between GitHub and Azure DevOps.

I have been working with Microsoft Azure DevOps for a couple of years, ever since they changed their name from Visual Studio Team Services.

Microsoft Azure DevOps is definitely stable.

I have experience with Azure Bicep and Paraform.

The initial setup is quite easy.

The licensing structure is good.

Definitely, I would recommend this solution. I would still look into your team goals and what tools you already know. 

GitHub is more community-driven, with more modules that are easy to access. 

Azure DevOps is more integrated with Azure as a platform, and that is important to consider when you consider DevOps in general or Azure DevOps.

I would rate this solution a seven out of ten.