Microsoft Azure DevOps Reviews

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.  

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.

The most valuable aspect of the solution is the complete tool orchestration within the DevOps. It's great for operations, monitoring, and building tests for deployment.

I like the user interface. It's excellent.

The solution is easy to implement and easy to use.

We've been using their documentation seamlessly. It's been great.

I love it because we have Microsoft Exchange Office 365 and we have all those reports already in place (especially if you're using quality reporting). We get that as an add-on. It comes within the package, so everything is very compatible. The analytics on offer are also very good.

The solution offers great plugins and has great integration capabilities. It runs on configuration management tools like Ansible and Puppet. The monitoring they have for plugins is also excellent. 

Whatever you might need, they seem to have it.

We're quite happy with the tool right now. We're not really using it too much. We are also just starting on it, to be honest, so what we've needed so far we've found that it offers. There isn't anything missing that I can see. 

One thing I would note is that it's hard to know what is included or not in the product. Especially when you begin to try and compare it to other solutions. When you go to a site like VersionOne, they tell you Azure DevOps doesn't have this or that, and when you go to Microsoft, it says VersionOne doesn't have this or that. They could do a better job of laying out exactly what is on offer so customers know going in exactly what they'll get.

I've been using the solution for three years.

In terms of stability, I would say we have no problem with the solution. We have been using the tool for all of our projects and we have no problems with that aspect. If users use virtual missions when they run the testing, everything is even easier.

Scalability, at least for the time that we have been using the solution, hasn't been a problem. We are able to adjust and expand any time of VMs. Any organization that needs to grow its usage should be able to do so easily.

Currently, 40 people are using the solution for one of the projects we're running. We have whoever you could think of in an agile team on it. Everybody from the business analyst to the product managers, to the testers, to the developers, and even to business end-users are on it.

I'm not sure if our organization plans on expanding its usage in the future.

I've never personally had to contact technical support, and I haven't heard from anyone in my team about any negative results. I'm not sure if I'd be able to evaluate their services at this time.

We previously used Jira, however, we have not switched over completely to Azure DevOps. We now use both.

With manuals, the implementation is much easier. It is quite straightforward.

We are not doing any kind of maintenance on the solution. We don't need to because it's so fast. We are not paying for everything in terms of infrastructure development. 

I'm not sure about the pricing. It's not an aspect of the solution I currently deal with.

We're currently looking at VersionOne and CollabNet just to see how they compare to what we currently use, which includes Microsoft Azure DevOps.

I'm new to this company. I've been here only for a year. The previous company, I was using Agile Central, which I really liked because of the user interface. Central was previously called Rally. However, after coming to this company, as they have Jira, I've been using Jira and also, for this one project, Microsoft Azure DevOps. I need to begin considering what I should do at an enterprise level. I'm looking at a variety of options including Microsoft DevOps, VersionOne, CollabNet, and a few more. 

Since we have Microsoft Azure DevOps already in place, I would like something that's similar and competitive. 

I'm not sure which version of the solution we're using at this time.

I personally just love using Microsoft DevOps. I would recommend the solution to anyone. Organizations considering the solution should just go for it and they should get the complete orchestration.

I'd rate the solution eight out of ten. I don't think that I have explored everything extensively yet. Any product definitely will have its own gaps, and since I'm not in a position to understand it 100%, I want to play it safe on ranking it at eight.

I use the solution in my company to mostly build CI/CD pipelines.

The benefits from the use of the product in our company stem from the ease that the tool provides when working with different teams. The product is also helpful in assigning tasks to team members easily. Following step-by-step processes, including testing and integration of the testing phase, all the other areas are easy with the use of the tool.

The product is easy to use. There are many options to choose from in the solution. Working with different teams in my company becomes easy when everything is integrated into Microsoft Azure DevOps.

The tutorials for building pipelines are an area that is a bit technical for a beginner. I would want the product to have some comments on the pipeline side to help beginners understand more about the solution.

I have been using Microsoft Azure DevOps for around 6 months.

It is a stable solution. I did not face any issues with the tool.

The product is scalable. That would already work with third-party platforms. In the future, I believe that the solution will be integrated with other platforms.

Around five to six people in my company use the product.

The product is deployed only at a single place in our company.

The product's initial setup phase was not complex, especially since the work items are mostly descriptive, making it an area that everywhere can use easily. The CI/CD part is a bit technical. One can get a hold of the CI/CD part over a period of time, so I don't think it is a difficult task.

Our company's team handled the product's rollout phase. The rollout phase was divided into parts. A single person did not carry out the rollout phase. I only took care of some of its parts. I cannot tell the exact time taken by our company to deal with the product's rollout phase.

My company utilizes Microsoft Azure DevOps for continuous integrations and deployments of CI/CD workflow since my company uses IaC. My company uses pipelines for continuous integrations. Moreover, one of the teams in my company uses the tools available in Microsoft Azure DevOps and various work items in it to integrate into the project.

My company utilizes Microsoft Azure DevOps for project management and collaboration across the software development lifecycle with the help of work items, like Azure Boards, which is a necessary part of team management. The task assigned to our company's team members is integrated into Azure Boards.

The feature of Azure Repos I find to be the most effective for source control management stems from the fact that it is integrated with third-party platforms, like Jenkins and GitHub, making it an option that is very usable in our company's environment.

I won't be able to comment on the product's reporting part. Our company's project manager takes care of the product's reporting part. To date, I have had no concerns with the project visibility area in the product. Working with Microsoft Azure DevOps is great because it provides top-notch integration capabilities.

Microsoft Azure DevOps has improved the productivity and efficiency of my company's development team. In the past, when my company wasn't using the portal in Microsoft Azure DevOps, there used to be no continuous integrations. After my company started to use Microsoft Azure DevOps, we got to know about the CI/CD pipelines. Now, it is easy for us to make changes in the code, and simultaneously, the code starts working at the production end. My company majorly uses the solution for CI/CD pipelines.

Speaking about the integration part, I would say that my company mostly works with Terraform as it is a scripting language. Along with Microsoft Azure DevOps, my company has only worked with Terraform for now. Though my company works with other platforms, like GitHub, we haven't done projects with GitHub. Working with TerraForm and Microsoft Azure DevOps has been great.

The tool's maintenance part is great. I did not face any issues during maintenance.

I recommend the product to those who plan to use it.

I suggest others watch some online tutorials before purchasing the product, as it can help them get the basic information related to the solution, making it easier for them to use it.

I rate the overall tool a nine to nine and a half out of ten.

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.

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.