Microsoft Azure DevOps Reviews

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.

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.

There are two versions of Azure DevOps: the cloud version and the on-premises version. We use the cloud version in very few situations, but most of our software is based on Azure DevOps on-premises.

We are a software house, and we develop software. We use it to store our source code; that is, it is the repository for our source code.

We have different teams working on different products, and each one uses a different methodology and a different process. Azure DevOps helps with that. For instance, one group may be using Scrum as a methodology to develop their software. The other group could also be using Scrum but with CDCI (continuous development, continuous integration), which helps a lot when you have to develop, test, and deploy the solution.

I think the most usable thing is that you can follow the whole progress of the development process. This makes it very useful for us.

As for improvement, the first one is pricing. For us, luckily because we are partners, it's free. Microsoft gold partners do not have to pay, but if you're not a partner, the product is very expensive.

The second would be that the tool should integrate with some of the competitors. It doesn't matter if it's a big market; it's difficult when you have to integrate with other competitor's tools, like JIRA, for instance.

If you look at the competitor's tools, they integrate easily with Microsoft, but on Microsoft's side, it's not as easy. They have been changing, but still, there are a number of gaps there.

I've got teams that want to use Microsoft Project, not only to control the whole process of the development but also to control the whole project and software. I think Project should be integrated with DevOps.

We have been using this solution for 10 years.

It is very stable. I think the system is down only a couple of hours per year, so it's very stable.

It's very scalable. We started using this solution 10 years ago, and it has evolved, We also have grown our software production, and so far, we have scope with all these situations.

We haven't had any problems with the product, but every time we had some questions, technical support staff answered pretty fast, in less than 24 hours.

The initial setup is pretty easy.

For the deployment, I think we had two people: one person from infrastructure and one who was a specialist in Azure DevOps. For maintenance, because we have about 80 people using this software, we only have one and a half people taking care of the software. That is, the infrastructure person does this part-time. He doesn't spend the whole day taking care of DevOps.

The ROI is very positive for us, but it's difficult to say how it would be if we had to pay for the solution. It's a very worthwhile product, but again, we don't have any comparisons because we don't pay anything for it.

Microsoft Azure DevOps is an expensive solution.

Get to know the product because it is complex and has many different possibilities.

It is worth having it, but you have to have an in-depth understanding and know what it is capable of doing. Otherwise, you're going to install it, and then it will be like having a very nice car in your garage that you don't know how to drive.

On a scale from one to ten, I would rate Microsoft Azure DevOps at eight.

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. 

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 provide this solution to our clients. The company we're currently assisting has had a lot of issues using Jenkins and decided to move the CI/CD pipelines to Azure DevOps. I'm a solution architect and we are partners with Microsoft. 

The solution offers great features including the project management feature and the Git-based repository. There is also the Azure pipelines and release artifact so you have all the functionality in one tool. It's also a relatively cheap solution.  

The only area that requires improvement is the interface. 

Stability is good. 

Scalability is good. 

The technical support is good.

The initial setup is easy. We had a team of three engineers dealing with implementation. 

Licensing costs are very reasonable compared to other solutions. It's a good price.

My only advice would be to go for the cloud version of DevOps, it's a better product. 

I rate the solution eight out of 10. 

We use Azure DevOps for the entire lifecycle of software development, starting with requirements analysis. After that, we use it to continue the process of development and deployment.

Azure DevOps is user-friendly. The UI and the UX are perfect. Their software covers the whole development cycle, from requirements analysis to deployment. In particular, it's helpful in the requirements analysis phase. You can apply your methodology or Agile framework from the beginning. After choosing the framework, like Agile or Scrum, Azure DevOps provides many features, like user stories, tasks, managing boards, and those kinds of things.

Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace. 

This makes up for any possible deficiency in Azure DevOps features. If you want some capability that Azure DevOps doesn't provide, you can develop your plugin or customize any part of it. The options for customization make it worthwhile for any software development.

Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it.

I've been working with DevOps for about five years.

DevOps is totally stable. And if there are any problems, Microsoft patches them as soon as possible.

When you enter into Microsoft ecosystem, you can scale any part of the product in this ecosystem. For example, you can connect Azure DevOps to Microsoft SharePoint for knowledge or document management. You can connect Azure DevOps to OneDrive for storage. You can connect it with Skype for chatting or Outlook. 

We don't use support from Microsoft. We mostly solve problems by searching for solutions on sites like GitHub and that kind of thing. 

I've used Atlassian products like Jira, Confluence, and HipChat, but I prefer Azure DevOps and the Microsoft ecosystem.

It is effortless to set up DevOps. All Microsoft products are user-friendly and easy to install. If you run into any obstacles, you can use Microsoft library or MSDN for any further help that you need. Microsoft provides a lot of wizards that you can use to solve your problem.

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.

We primarily use the solution for our internal development and we have some clients that require some consulting around some DevOps functionality.

We use the product for the development process for the repository, for the tracking of the tasks in the boards, and for the pipeline for CINCD.

The test plan is one feature that we are exploring more right now. This is a great feature that we want to deeper into.

We have a solid base. We can do everything with DevOps.

It is possible to add third-party extensions to increase the usability of the product.

The initial setup is very simple. 

We have found the solution to be scalable.

The solution, for the most part, is stable. 

Some things, like project management, tasks, progress, and having work progress views, require us to use some external tools or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps. They need to expand the solution's offering.

While I have used the solution for two years, the company has some personnel that have used it for longer. Our development team may have used it for four or five years. 

The product is stable. We had some regional degradations a few months ago, however, it wasn't too much. For the most part, it's reliable and there aren't bugs or glitches. 

The solution is scalable. If we need to expand it we can do so. 

We've never had to contact technical support. I cannot speak to how helpful or responsive they would be, as I've never dealt with them directly. 

The initial setup is very simple and straightforward. It is not difficult or complex. 

We use the online version. We don't have to deploy the tool. We don't have to put in a lot of effort as we already have the pipelines in the TFS. We just move it to Azure DevOps. 

I'm a solution provider. I sell Azure DevOps and I have a client that was looking to analyze some differences between Jira and Azure DevOps. Therefore, I have evaluated Jira a bit for them.

We are both a reseller and a partner of Microsoft.

We always use the latest version of the solution. 

I would recommend this product to other companies and users. If a company or a team doesn't know how to work with Azure DevOps, the advice I would give is to find someone that knows the tool and do a POC first to make sure you understand everything a bit better before diving right in. 

In general, I would rate the solution at an eight out of ten.