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.

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.

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.

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.