Microsoft Azure DevOps Reviews

We use Azure DevOps to place our corporate servers into the cloud. We perform evaluations in the cloud for clients. Occasionally, we provide a hybrid solution in a specific cloud. For corporate work, we usually use a different cloud. With Microsoft Azure DevOps, as with any DevOps, it is not always possible to identify specific use cases. How do you identify a specific feature from a hundred requirements into a specific use case? It is very easy to lose detail. Traditional teams and ways of working methodically for safety-critical systems are not always prepared to handle that. It is important to be able to handle hundreds of detail-oriented requirements.

Azure DevOps is now used for safety-critical systems, whereas in the past the traditional approaches were used in requirements management. This is more like the traditional waterfall model. Improvement is always unique to productivity. That's why we switched to Microsoft Azure DevOps. The software teams prefer it to IBM.

We can eliminate some of the middleman processes. In the process, we are merging DevOps with development and operations. So developers act like our operation team as well. That concept is a great exchange. It brings a high level of visibility. It helps the team and department cohesion, which helps to improve productivity. 

It also includes a high level of traceability and elimination of some of the unwanted silos in productivity. Testing and transparency need to be defined within the boundaries. If a backlog occurs, you should be able to group them as a whole. This means there is a backlogging to the team, as opposed to individual areas. Each area needs to be visible to other areas, at all times.

Microsoft needs to consider ruggedization and addressing specific disciplines. Fundamentally what I mean by that is you cannot merge everything. It should be able to handle the different types. There is ecosystems engineering, and there is software applications engineering. There is a need to bring these teams together, but the disciplines don't integrate very well, and so it won't work. For example, there is expertise in an area, and they tend to view the project from their own perspective. 

For example, the software UI/ UX team needs to view it from the UX perspective. Application engineers need to view it from the application viewpoint and the engineering perspective is different again. Although we need to be cohesive in our approach, we need to keep some boundaries as well. The idea of containers arises, such as those provided by the open source software product Kubernetes. We need to containerize different disciplines and then merge them. As a manager, I should be able to ask the formative team to focus on their creative section, and that their task is completed. In the Application layer, you also focus on their requirements and you establish traceability. Other teams may also be involved in linking to the overall requirements.

I have been using Azure DevOps for one year. It has been used in the company for about two years. It is used in the cloud and on-premises, as a hybrid cloud solution.

We implemented on-premise as a hybrid solution, and on the cloud.

I would give Microsoft Azure DevOps a six out of 10. Microsoft Azure DevOps is not perfected yet, as it needs to be more user friendly. If it can achieve that it will eventually reach a 10.

What I like the most is the DevOps Boards. It's easy to create a hierarchical project structure, assign tasks to people, and then track their tasks.

I also like the scheduling functionality.

I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified. 

Also, it would be nice to have a percentage complete. For example, if a task is in progress, how much of it is complete, how much is left outstanding. I'd like that to be something that the assignee fills in and that automatically reports back to me.

I have been using Microsoft Azure DevOps for six months.

It's a stable solution.

Microsoft Azure DevOps is scalable.

I have not contacted technical support.

Previously, I used Microsoft Project. We chose to use Microsoft Azure DevOps because I needed something that my stakeholders could access.

The initial setup was very straightforward.

The time it takes to deploy is dependent on the type of deployment. Deployment of software, or deployment of the project into the software? 

It took me a week to deploy the project into the software. It's approximately 800 PBIs.

Before implementing Microsoft Azure DevOps, I would suggest doing your research on how to configure it. It is a product that I recommend

I would rate this solution an eight out of ten.

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 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.

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. 

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.