Microsoft Azure DevOps Reviews

We normally use DevOps. On the application, everything has gone DevOps, however, we don't use the functions. All applications developed there have gone under Azure or AWS. We normally develop them to be able to not be dependent on anything, so if we want to deploy them in another environment, we can deploy them easily. If we want to use it in Azure, we use it in Azure. If we want AWS, we use it in AWS.

I like the CD pipeline. It's the most valuable feature for us. It's so easy to integrate into the CD/CI environment. I mostly love that one.

The initial setup is quick and easy.

The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code. 

If you want to use the DPR it's a bit harder due to the fact that it's only 30 days.

We've been using the solution for a year and a half at this point.

The stability of the product has been good so far. I can't say that I've witnessed glitches. There aren't bugs. It doesn't crash or freeze. It's reliable, as far as I can tell.

We don't have any issues with the scalability of the solution. If we need to, we're able to scale.

We've never contacted Microsoft for technical assistance. 

We are Microsoft partners. We have several Azure experts on our development team, and we have a tech that came from the US and did the training for us. We have a very strong understanding of the product and therefore we don't need help with troubleshooting or anything of that nature.

We also currently use AWS, however, I prefer Microsoft's solution as it's a bit easier to use overall.

We did not find the initial setup to be complex. The implementation is straight forward. 

Deployment is quick and typically only takes a few days or so.

We have ten people that handle maintenance. They are in different parts of the world. We have two in Australia, for example, and two in the USA.

The cost can get pretty high if you aren't paying attention to what you are doing.

We're partners with Microsoft.

I'd highly recommend Microsoft, and I recommend it more than any other solution. Everything is very simple and straightforward. The only worry for some organizations may be the cost. You need to be really, really careful.

I'd rate the solution overall nine out of ten. I think it's really, really great. If the functions were a bit better, I'd give it a full ten out of ten.

We use Azure DevOps for managing our workflow, as well as the CI/CD.

We use the CD/CD for all of our deployment lifecycles.

The CI/CD portal is very user-friendly.

The platform is very easy to manage. It is easy to manage repositories between the business users and corporate users.

Fields can be customized and the reporting is good. The APIs that are exposed can generate management reports.

The most valuable feature is the test manager. 

Integration is easy to do. The single-sign-on facility is there in every aspect including Azure DevOps, Active Directory, our portals, and all of our development sites.

Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves.

We would like to have an indicator of the percentage of occupancy. Suppose a person is working on two different domains, and we have 70% on one project with 30% on the other, it should be able to report that. As it is now, we have to manually enter that data. If this functionality were provided then it would make it easier for users.

We have been using Azure DevOps for the past two to two and a half years.

We have had issues, usually related to the APIs, but the support team has always helped us to resolve them.

The Microsoft support team is prompt to respond and very good.

The price is cheaper than Jira and some of the other competing tools.

Overall, this is a good product and if the Gantt chart and occupancy reporting features are added then it will be the most powerful one in this space.

I would rate this solution an eight out of ten

The key thing I find benefits me is the ability to track right from the feature and determine what has happened. I have a direct link to the test and the metrics that are available.

There are a lot of helpful features available for tracking dependencies.

The dashboard could be improved. Although there is flexibility in configuring it, there are some metrics that we have to configure ourselves. Improving the metrics that are readily available on the dashboard would be very helpful.

I would like to see better integration with third-party solutions, where if they are part of the DevOps pipeline then the reporting could be made available on the dashboard.

Having some form of check modeling integrated into Azure would be useful.

I have been using Azure DevOps for the past four years.

We have had no issues in terms of stability.

The offerings in terms of scalability are good.

We have not had to depend much on Microsoft support for DevOps and project management. However, I can say that the general support that we get for Azure is good.

I have some experience with Jira from Atlassian, although I have worked with Microsoft Team Foundation Server from the beginning.

The initial setup was straightforward. While we were migrating, we had training from Microsoft, which was helpful.

I haven't really looked into other options.

Overall, this is a good product and one that I recommend. The features it has have helped us, especially with tracking dependencies.

I would rate this solution an eight out of ten.

We are a manufacturing company and I am a technical consultant who is responsible for managing the software applications that are outsourced for development. In this role, I have gained experience using Microsoft Azure DevOps.

I have also used it as a software developer in companies that I previously worked for.

I like the entire tool because it is a one-stop-solution for DevOps.

The Scrum functionality in project management is helpful, as are the code repositories. It has support for pipelines.

There are certain areas in Azure DevOps that are better in other products. These are things that I need to more fully explore.

I have been working with Azure DevOps for approximately four years.

The stability is good and I haven't had any issues with it.

At this time, the majority of our software application development is outsourced so there is not much in terms of DevOps. However, in the future, I am planning to implement DevOps here. Once that happens, I expect that our usage of this solution will increase.

I have not needed to contact Microsoft's technical support.

The initial setup is straightforward and easy. It takes very little time to deploy.

I deployed this solution without any help.

Personally, I like this product and it is one that I recommend. That said, based on my experience, I cannot say that it is perfect.

I would rate this solution a seven out of ten.

Building fast and reliable, amplified feedback loops in all stages of our software delivery and operations lifecycle. The business strives for built-in quality to ensure that everyone have correctly done their job. 

I trust my team with peer reviews of our designs, code, test and infrastructure.

I'm familiar with Azure DevOps in the sense that my group directive has based the administration, architecture, and development on Azure. So whichever hat that I need to wear at the time that's the one I can wear.

I would say that Pipelines is Azure's most valuable feature. Also generally, Azure enables us to create a staging environment through to a production environment in an easier way and then get the code and run that. It also has decent pull requests and things like that.

Azure DevOps is a very cross-platform product. One of the issues that I have currently with the company is that they are using two different parts of technology. They were using JIRA for their sprint work and they were also using Confluence, as well as other Enterprise software. I advised them that all their sprint planning, backlog work, and everything else, can be done out of Azure DevOps from one central place. I know the Microsoft team will always look at improvements because I know that they are constantly looking at improvements to products while listening to their customers and looking at a global scale. I'm keeping my ear to the ground, as I always do.

The product keeps evolving and at the moment there are a lot of good parts There are petabytes of data. Anytime somebody does a pull request or anything else, Microsoft is notified about it. So if somebody, somewhere is always looking at that and watching, that can be a revolutionary product. It's a product that can continuously grow and evolve in time. Even if it is not yet what you call a finished article, it's a growing and evolving product.

Everybody has a slightly different take on what solutions or what part of the solution they would like to be improved. You can always improve a platform. Microsoft is always listening to customers and they will bring out a new version. The platform is quite user-friendly at the moment because you can use any program or language with it. You can't say you need another program, because as far as I'm concerned the main ones can be integrated with Azure. The newer ones like Go, as well as older ones like Python, Java, and PSP,  can all be integrated with that platform.

I suppose when we hear about that release, I have no doubt that because Microsoft captures a lot of metrics and information that they monitor, like capturing data about what or how people use their product, they can see where the usage is and where they might want to remove a feature. That analysis and also comes from Microsoft's monitoring capabilities.

I thought it was very stable. They didn't have any shaky moments. Predominantly with Azure DevOps you need one thing only: a solid internet connection. If you've got a solid Internet connection, you just push everything up to the platform or run an integral request. I haven't had any issues with that. Some people might have, but it all comes down to their internet connection.

This solution is extremely scalable.

It helps a lot in Microservices or service technologies. Using the infrastructures of code enables a productivity increase of a thousand percent. I was speaking with a company that was pulling 12 requests at one time but using competitive technology like DevOps they were able to pull over 2000 requests at the same time. It's extremely scalable and you can use it to scale down when it needs it. It's a completely autonomous product, that allows you to scale whatever you need.

I have five or six back end developers that use it every day. They learn every day, so whatever code or scripts they write are in Azure DevOps. They're not using any another tool to do it, they are pulling it with the platform because you can't tell other people about a platform if you aren't using it yourself. The first thing they do is log on to DevOps.

There will be an increase in our usage of the product. We are looking to expand at some point. The more people that come on board, the more use there is for the product.

We haven't had a requirement to contact their technical support. I have contacted their technical support before under some other projects and got a really good response from the person on the other end of the phone. They are always looking to help you solve more solutions as quickly as they possibly can.

I don't think I have had a bad experience; I've always had continuity. They were able to get me the problem resolved, whether it was a P1 or P4 issue. I've never had a problem with the technical support.

I have experience with Amazon Web Services. As the Azure product has matured a lot in the last two to three years, it deserves its market share at the moment. We were using other products, like Visual Studio, a web service which is an old name for Visual DevOps. We were also using things like Team Foundation Server (TFS). We were just using some of the older tech.

The initial setup was straightforward.

We did the implementation ourselves.

I'm working on the high-level design and the low-level design so I know where we're going to start, and whether we've got a blank slate. I've worked with many firms in the past and companies have their own design in place. Usually, some of these companies material is outdated and Microsoft will probably move the bar several times. We are Microsoft accredited so we stay in touch with the technology more recently than most. We've constantly been informed of the latest technology and the latest products that are evolving on the platform. That includes those that are in preview, which I hope will become available, as well as those that are going to be deprecated. We're basically in full harmony with Microsoft and their products.

We most definitely achieved an ROI.

Check out the pricing information from Azure Cost and analysis information.

No Visual Studio Team Services and Visual code were the preferred options.

The first thing that I would suggest is to read the documentation for the platform. The online documentation changes pretty much every other week; there is always something new coming out. Practice, practice, and practice. Test, practice, and repeat. You need to know your way around the platform and the only way to do that is by hands-on practice. You can't break the environment, but you can speed things up on the thirteenth hour. It depends on how you configure things since every configuration is different. It's an excellent product that is taking into account current technology, yet also flexible enough to use with future technology.

At the moment I would rate Azure DevOps as a nine out of ten. The reason I wouldn't give anything a ten is because it's constantly evolving. There is room for improvement, as this is not the finished article at all. The reason I would give it a nine is the information to get the best usage out of the product is readily available. I've been using Microsoft tech for over 25 years now and back in the day it was difficult to get information out of Microsoft even when you were an MCPN. You would have a special link to go through a Microsoft back door to gain information. That's completely different to the advice that you would get related to Microsoft.com. Now Microsoft is completely different with everything readily available. You can download it in pdot format and the document could be 2000-3000 pages. They leave no stone unturned.

The only problem I would say at the moment is a friend of mine said that the Microsoft test book is taking a long time to come out because he wants to take the exam. Some people need to read the information and retain the information that way. Sometimes you go on these courses that are not run by Microsoft directly. They can be very flaky and don't have all the information or experience of using the product in normal working life.

If there is anything I would ask for, it's to get the documentation out on hardback so that we can add it to our libraries. That would be very good.

The Repos, Wikis, and pipelines are all excellent features.

The solution could work to improve their reporting.

The stability of the solution is good.

The scalability of the solution is good. I would give it a four or five-star rating. We have plans to increase usage. Right now we have about 100 users on the solution.

Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support.

We did not previously use a different solution.

The initial setup is straightforward. We just implement it from the cloud. We took it and configured it with our local website infrastructure, so there was nothing much to do.

There is a licensing fee of $6/user per month. That's not too much money for us. There aren't really any additional costs beyond that.

We considered using Jenkins, but we decided to use Azure DevOps because we have an enterprise agreement with Microsoft. It was much easier.

We are using the public cloud deployment model.

Potential users should not hesitate to move to Azure DevOps. It keeps on progressing and keeps on adding new features all of the time, so it's a solution that I would highly recommend people use.

I would rate the solution eight out of ten.

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.

Agile scrum project management of a software product in a start-up company. We are a team of 11 people located in different countries.

We have team members in different locations of the world. Azure DevOps is the main communication tool between the product owners, UX designers, and developers.

Its configurable dashboard offers various display options for the stakeholders of the project.

• Dashboard
• Query
• Sub-tasks configuration
• Extensions library
• Visual Studio and other MS product integrations.

• It would be better to have a free-text query editor. 
• Product management/roadmap planning features are missing.
• Parent Column is added in listings and we expect to see it in queries as well

Refreshing the browser is needed when a data is updated. I am expecting Microsoft to prepare an Azure DevOps application running on PC and downloaded from the MS app store.

It is easy to use if you are already familiar with Microsoft products.