Microsoft Azure DevOps Reviews

We are trying to move our entire DevOps cycle to Azure DevOps. It includes test management, source code control, and some parts of CSED.

It is deployed on the cloud, so we always have its latest version.

Most of the features are very valuable for us, especially the source code control and task management.

The main issue that I have is the connection speed. Sometimes, the response is too slow. I am based in Taiwan, and I am not sure if it is because of broadband or something else.

Its initial configuration is also a little bit difficult.

I have been using this solution for almost one year.

It is stable.

It is scalable. Currently, we have around ten users. We hope to increase its usage.

I didn't have to get in touch with them. I didn't have any technical issues.

We have used Jira and TFS. Microsoft Azure DevOps is very useful in terms of management. We are trained to be the users of the DevOps services, but with Jira and TFS, we also had to manage the server, which we didn't want. We wanted to eliminate this kind of effort and just wanted to publish our own developments without having to manage the server.

It is a cloud solution, so there is no installation. Its initial configuration takes some time and is not very easy. 

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

It is used for development and life cycle management within the company. We use the SaaS version. It is called Azure DevOps services.

It has absolutely improved the way our organization functions from a development lifecycle point of view. It has enabled teams to be more Agile and flexible.

All features are good. Pipelines module is comprehensive, Boards and Artifacts modules are also really extensive.

It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It has a easy to use UI. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated.

The administrative capabilities of the tool need a huge improvement. Its Wiki and Reporting functions also need a lot of improvement. Their support can also be better.

I have been using it ever since it was created in 2012

It is very stable.

It is very scalable because it is on the cloud. We have a very large user base and they're all IT-related. The users are engineers, product managers, and management. It is the entire IT organization.

We use their technical support a lot. We have internal support, but we will also reach out to Microsoft to resolve problems. Their support is very good, but there is always room for improvement. It depends on the subject area. Sometimes, they have people who are not as well versed as others.

We've been pretty much on the Microsoft products. We used to use Team Foundation Server, which was a Microsoft product. Before that, it used to be Visual Source Safe. We also used to be on PVCS, SVN and CVS.

Being a SaaS solution, there is no setup.

It was implemented in-house as we have a high level of in-house expertise in the ALM space.

This area is very different for each and every organization and I would recommend that they research cost and pricing for their situation.

No, we did not evaluate any other options since we are heavily tied to the Microsoft stack. However over time, we have adopted other platforms (Java, Node, Python and others) since Azure DevOps is cross platform compatible with Linux, Windows, iOS and Andriod.

If you're looking for a cross-platform solution that end-to-end does everything in the development life cycle, this would be a very good solution for you. If you're looking for a more siloed product that is specifically focused on one particular area of the lifecycle, this is definitely still an option, but you should also evaluate other options as well (Atlassian, IBM Rational,  MIcro Focus ALM, GitHub etc) for completeness.

I would rate Microsoft Azure DevOps a solid eight out of ten. It is really good at what it does, but it also has some solid areas of improvement that are needed. Once they have addressed those, it could be hard to beat.

I took a part-time job doing a mentorship to guide the students on how to use cloud computing on the AW and Azure cloud resources. For that project, we go through each and every service on cloud computing that is part of the service platform. The new technology is called server-less technology. The goal of the mentorships is showing students how to fundamentally use these resources and explain the advantages and disadvantages of cloud computing over on-premises solutions.  

Currently, I do not know if there is really a single feature that stands out as the most valuable. If you consider our use case and that we were using Azure essentially as a teaching tool, it was the tool itself that was valuable.  

I do not have in-depth experience with Microsoft Azure, but it is like other services such as AWS. Currently, the number of services are increasing on Azure actually at a faster rate than with Google Cloud. If you are working with Microsoft products like Office 365 the best cloud solution would be on Azure services. The cost is also better than AWS.  

Microsoft has also built an association with other cloud products for helping to migrate your licenses to the cloud. This works out well if you have a substantial investment in licensing for Microsoft products on-premises. Being able to bring that license to the cloud is a good transitionary solution.  

I have been running reports on the availability of the major competitors in the cloud services to use as a demonstration in webinars and comparison of services. The most available solution on the cloud in user availability by minutes is Google Cloud. Google is the number one solution and the second one is AWS. The third one is Microsoft Azure.  

Compared to the availability of the other two major cloud solutions, Microsoft Azure needs to make an improvement in their availability. This report suggests that the Azure team needs to do some major changes to match the availability of the other services and make the product more competitive.  

In DevOps (software development and IT operations), server-less architecture and QNX platform integrations are things that need to be added to Azure. Currently, I am not sure that this is the case. But previously, I have had experience trying to use Azure with service and integration with the QNX platform and it is not as good as Google Cloud. Azure has improved its current set of data services on the cloud. But Google Cloud is doing more right now to bring those technologies and make them available to developers or enterprise solutions. So, QNX integration needs polishing.  

We have been using the product for only the last two months.

I have not experienced any issues with stability.  

In general, I have seen no real issues with scalability. It is a cloud platform and scalability should usually be available on demand.  

I used Google Cloud on one of my previous projects but currently, we are using the on-premise solution. So we are hosting everything locally on-premises. We do not have any current cloud provider for the business as a whole. We are using AWS for security and backup for the production environment but mostly we rely on the on-premise solutions at the moment.  

We use the S3 compute instance of AWS only. We do not use any other AWS services. We just use VM's that we create on the S3 instance.  

Setup is not so much of an issue as the product is on the cloud. The services are essentially on demand for the product. What you do with the services is what may take more time and consideration.  

I am not comfortable sharing the details of cost because there may be different pricing schemes, but compared to AWS, Azure is less expensive. So in the pricing in this class of services, Azure is good. It can work well for small to medium enterprises. But this solution is may not be good for those who are not enterprise-level users. Small cloud computing providers have better pricing than the bigger cloud computing providers like AWS and Microsoft Azure and may be a better choice for non-enterprise use.  

Still, Azure is priced better than AWS. Price may not be the only thing to consider.  

I have had the opportunity to use a variety of different solutions and it has not really come down to a situation where one is replaced with another. There is an ongoing evaluation of the products as newer technology including the most well known, like AW, Google, and Azure. AWS is the most expensive cloud hosting. In my estimation, that is the best product right now, but things are changing quickly.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Microsoft Azure DevOps as an eight-out-of-ten. It is not quite up to the level of other offerings in some ways but it is improving all the time.  

My clients use Azure DevOps primarily for managing code deployment pipelines. We follow a structured process of pushing code from the development environment to testing and then to production, and Azure DevOps is crucial in this workflow. We leverage its version control capabilities to maintain and track our codebase efficiently. Additionally, we make use of its dashboard service to monitor and manage employee hours, helping us keep a close eye on project timelines and resource allocation.

The most valuable aspect of Azure DevOps for me is its robust version control functionality, which is critical for our workflow. I find it particularly useful how easy it is to automate pipelines. When we push code changes, the system automatically runs the entire pipeline, and the clear visualization of logs is a great benefit. This feature allows us to quickly pinpoint issues and understand what went wrong with our processes or tools, making troubleshooting much more efficient.

While there is always room for improvement, I don't have any urgent issues or specific feature requests right now. I'm content with Azure DevOps as it is. Its functions are standard and easy to use for those familiar with such tools. However, the only thing that could be improved is the stability of the solution.

I have been using Microsoft Azure DevOps for two months.

The solution is generally stable but not entirely issue-free. While problems do occur occasionally, they have become less frequent, occurring around six times less often than before. For example, a recent issue occurred when a dependency was updated, causing the pipeline to crash. However, with the help of logs and troubleshooting, we were able to identify and resolve the problem by making adjustments to the Docker file. I would rate the stability as an eight out of ten. There is room for improvement in terms of stability, as there are occasional issues that require manual intervention to address. While progress has been made, there is a desire to achieve a level of stability where network removal is not necessary in the first place.

Azure DevOps is highly scalable and works effectively even for large-scale projects. It can handle the demands of extensive engineering work and is generally robust in terms of scalability.

The technical support is good and quite responsive.

I have experience with using GitLab. Comparing GitLab and Azure DevOps, GitLab excels in functionality and offers excellent integration capabilities with Azure DevOps. However, Azure DevOps has a more user-friendly UI. The choice between the two depends on specific project needs and preferences.

The installation of Azure DevOps is straightforward because it is a web-based platform. You don't need to create solutions or go through complex setup procedures, making it a user-friendly option. Maintenance for Azure DevOps is minimal, especially if you have automated processes in place. If your solution uses Docker and you have set up automated updates on Docker Hub, the environment can essentially upgrade itself without much proactive maintenance. However, if issues arise, you can make adjustments to the configurations as needed, allowing for a more reactive approach to maintenance.

My advice to those looking to use Azure DevOps would be to make good use of the documentation available on their website. It is a valuable resource that can help answer questions and provide clarity on various aspects of the platform. Overall, I would rate Microsoft Azure DevOps as an eight out of ten.

The main use of this solution are to combine software development and IT operations. Also, we use it for automation with version control and microservices. Automation is a core principle for achieving DevOps success and CI/CD is a critical component. 

The application of continuous delivery and DevOps to data analytics has been termed DataOps. DevOps focuses on the deployment of developed software, whether it is developed via Agile or other methodologies. ArchOps presents an extension for DevOps practice, starting from artifacts, instead of source code, for operational deployment.

This solution has offered lots of improvements. The most important improvement was to provide continuous delivery with high-quality software. It helps with version control with automation using CI/CD components. It also helps to develop software using the agile methodology. 

The ability of different disciplines (development, operations, and infosec) to achieve outcomes has been great. Increased focus on test automation and continuous integration methods are helpful. It helps release new features continuously into large-scale high-availability systems while maintaining a high-quality end-user experience.

The most valuable feature is automation with version control. 

DevOps initiatives can create cultural changes in companies by transforming the way operations, developers, and testers collaborate during the development and delivery processes. We can release new features continuously into large-scale high-availability systems while maintaining a high-quality end-user experience. 

Adopting DevOps will also help eliminate the old and monotonous way of agile activity among big IT teams like network, Storage Team, Linux/Unix, Windows, etc.

It’s commonly observed that you cannot just change a company’s culture on command. You can influence the culture, shift it, and while it can evolve over time, it’s nearly impossible to just instruct all employees to simply change the way they think and act about specific things. 

The culture of any organization starts at the top of the leadership hierarchy and trickles down throughout, filling every empty space. It is essential that you get buy-in from the top management down to everyone in the pipeline. 

In order to do this, all involved need to understand the advantages the shift is going to have on the organization and on the team members.

I've been using the solution for the last two years.

The scalability is very good.

We didn't use any solution before.

We also looked at AWS.

We use Microsoft Azure DevOps to maintain our project. We create a project in a good DevOps, and then we add the backlog items. The product owner adds the backlog items, and then the development team. The repository is also built into that. We have a private Git report for the project. Under reports, we can create a repository for the big projects and maintain the source code. 

Developers can commit and make a full request. For example, configure Jenkins, reconfigure Jenkins with the repository credentials, and then use it for linking. We don't use the pipeline available to us, and we use Jenkins for CSC.

In our organization, Microsoft Azure DevOps helps senior leadership go in and check the project status and how much effort has been put in by the development team. They can also pick, choose, and add features to be used by the development team. It's like a backlog management tool that helps improve and support projects. 

It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful. 

Integration and plugins for other tools could better. Like if you want to integrate the DevOps with other tools that are in the market. This could be for the engineering tools to check code quality, application security tools, and DevOps dashboard tools. 

They could also make the implementation easier. The test plan also has basic features that are not user-friendly. It should also have integrations with test automation tools. We need a test plan, automation testing, and EA-based testing.

We have been using Microsoft Azure DevOps for more than four years.

We haven't got any issues with the technical support area.

The initial setup is very straightforward. 

Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users.

I would recommend this solution to new users if it's a simple project. If you want JIRA, you'll need to have JIRA software for backlog management. 

On a scale from one to ten, I would give Microsoft Azure DevOps an eight.

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.

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.