Microsoft Azure DevOps Reviews

We use Microsoft Azure DevOps for application lifecycle management, including source control-related things, pipelines, and also for work item management. In short, the whole ecosystem.

Within our organization, there are roughly one thousand core developers using this solution. We also have stakeholders, product vendors, Scrum masters, testers, and manual testers. 

Mainly the source code solutions and the pipelines. Work item management and the manual test I/O. Test automation, end-to-end testing, and the manual test experience. It's got something that you won't find in other products. The work item management is good enough for small to medium-sized teams, and for large projects with plenty of teams collaborating with each other.

We can achieve the boundaries of the system. Potentially, we could do it with other tools like Jira. Still, with Microsoft Azure DevOps, we can manage everything.

Currently, if you would like to use the full-set of customization features, for example, the process templates, the HL process, or the Scrum process, if you start from scratch right now, you'll have these options. But if you've been working for several years in an established ecosystem, then you're based on an old-fashioned way of working and you won't be able to use the recent customization features.

There are options to get around this, especially if you move to the cloud or if you copy things and migrate them, but that's a huge amount of work. It's best if you start from scratch in a new project — in a new environment. With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem.

We have been using this solution for roughly 10 years. 

This solution is stable. I don't have anything negative to report. 

Microsoft Azure DevOps is very scalable. It uses techniques from Microsoft itself, so if you have the knowledge of how to deal with that, you can scale it up and out as you wish.

Technical support is good. We have had a few cases where we needed support and they contacted us immediately. There was a willingness to find a solution and determine if there was a bug or if it was an oversight. We have a good relationship with Mircosoft support.

The initial setup is easy.

Most of our developers have an MSDN license which is linked to the Visual Studio development environment. 

We also have a corporate license for other products like Windows Server — it's all included in one package. An additional license is not required for the on-premise solution. If you go to the cloud, it's a different story. Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs.

Overall, on a scale from one to ten, I would give this solution a rating of eight. 

It could be a little bit more flexible in terms of work item management. Apart from that, I can't really think of many features that are missing. It supports all kinds of ecosystems; there are a lot of possibilities when it comes to interacting with other ecosystems. 

Try to follow the market standards. There's a whole huge community that supports it. The market is evolving very fast. Microsoft is acquiring other companies. They recently bought GitHub. It's hard to say which solution will survive — DevOps or GitHub. That may be an issue in the future. 

We are exploring this solution. There is not enough protection in the environment at the moment. It's been almost six months since we started the process of exploring the DevOps environment in Microsoft Azure DevOps.

We have a customized development methodology so that it is easily marked to our existing environment. Currently, we required that all these systems blend easily in this one environment. We can actually use all the large frameworks within DevOps properly and automate most of our support, starting from planning through support to deployment.

It has a good GUI, and it's very user-friendly. It is also a familiar environment as we are used to it. All our users are very comfortable working with it. I think the Azure methodology and all those DevOps features in the dashboard are very effective in our environment. 

It's very implementable in our environment compared to the other DevOps environments which we experienced. I won't name them, but this one part of DevOps we have found very easy in our environment because the infrastructure there is fairly supportive and very integrable to the current DevOps environment we use.

The testing environment and different pipelining concepts can be improved. It can also be more user-friendly. They can actually incorporate all those other features, current tools and have those mind maps.

They could add some good analytic features. I think they can be more enriched with some good reporting features. They can also improve the designing tools.

We have been using Microsoft Azure DevOps for about six months. 

Microsoft Azure DevOps is a stable product. I feel it's stable enough for us at the moment. 

The initial setup is not overly complex. It's fairly straightforward. Other than the Java environment variables which lack documentation, it's not complex and easy to follow.

The main agile features are very expensive.

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

I used Azure DevOps for work item management, sprint planning, source code repository, continuous integration, continuous build, and continuous release. I build whole chains.

The most valuable feature is that it's fully integrated, where we have a single place to do everything that we need.

Testing is really good, it has come a long way.

It is the single source of proof or the single system of record that does everything you need, you don't have to put the different pieces together to form the whole chain.

We can do everything in one single platform, which is why it does a good job.

Requirements management is an area that can be improved.

Integration with Microsoft teams would be a good idea.

I have been using Microsoft Azure DevOps for five years.

It's stable. It's been pretty good, especially in the last two years.

There are no issues with scalability. We have approximately 50 people in our organization who are using it.

We have contacted technical support and they are excellent. I would rate them a nine out of ten.

I am using a mismatch of tools from HP and Atlassian, but they did not give us an integrated toolchain. Microsoft Azure does it exceptionally well.

It is reasonably straightforward, but it is only as straightforward as the problems that you are trying to solve.

If you are trying to set up the whole chain, then the problem is complex, and the solution has to be as equally complex.

The price is reasonable, but of course, you can find others that are cheaper such as Atlassian. But, if you look at the more serious products like Polarion, it's very competitive. 

If you have good Microsoft programs, it's nearly free.

I would certainly recommend this product.

There are a lot of parts to the toolchain for DevOps, so take each area at a time. My advice is to take one step at a time, don't overdo it, and over time build out all of the capacity difficulties. Automation is also one of the biggest things.

Overall, it seems like a really good solution.

I would rate it a ten out of ten.

We use the solution to store all our source codes. It's a solution that stores everything. We are an in-house development and we produce a lot of codes.

We also use it to control our development process. We follow some methodologies. Every every team has a different methodology, for instance, Chrome, Agile, et cetera. The whole process from the planning process until we deploy the solution, everything is controlled by DevOps.

The solution is very good at automating various aspects of the DevOps process. You can automate almost everything. You don't have any human intervention. It's almost automatic. As long as you finish your code and put it in, the software gets the code and tests it. If it is okay, it will go ahead and integrate it and put it in production without any human intervention. This is excellent.

The tool allows you to connect with many external tools. You can improve the whole process that way. We use a couple of things, however, there is a plethora of things you can put together in your solution.

The initial setup is very easy.

Despite the fact that you can automate most of the things, you still have to produce some scripts. There are things that are not very user-friendly. The tasks are achievable, however, it's not easy. You have a lot of steps until you can get the thing automated.

In the past, Microsoft DevOps was integrated with Microsoft Project. Out of the box. Right now, it's no longer that way. That would be interesting to have.

It would be great if I could integrate with a human resource type of software that could control timesheets.

I've been using the solution for 15 years now. It's been a while. It's well over a decade of experience.

The product is extremely stable. We've used it for 15 years and haven't had any serious issues. There are a few bugs or glitches but nothing tha can comprimses the day to day operation, and they usually fixed in the next release. It doesn't crash or freeze, though sometimes gets a bit slower due to databes overheadd, so maintance has to be done. It's reliable.

We are a small team, and therefore we don't need to scale. However, I've heard both that it grows 10% a year without issue and that it scales very easily and very well. As far as I know, a company can scale it if they need to.

We have between 50 to 70 people using it, including staff and managers, et cetera.

I have used technical support a couple of times. Typically, it's good. It's usually a couple of hours and then, they answer you. Nevertheless, you can go to the online site and most of the time you can solve the problems just by reading. They have a lot of documentation available. 

That said, when we dealt with them directly, they were pretty fast. I'd say we are satisfied with their level of service.

The initials tup is not complex. It's a very easy, very straightforward process. A company shouldn't have any trouble with implementation. It only takes a couple of hours. It's pretty quick to deploy for DevOps purposes.

We are just a customer.

We intend to move from on-premises to the cloud next year.

I'd recommend this solution. It's a worthwhile investment.

I would rate the solution at a nine out of ten. We've been quite satisfied with it overall.

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.

We use it to manage the project. We create the product backlog, and we put our tasks into the DevOps schedule.

Azure DevOps allow you to create a bridge for maintenance and support, directly to the client. We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes. The Timetracker function allows us to put all this together. Before Azure DevOps, we had difficulty predicting how long tasks would take, considering all the parts that must work together.

We have a component server, which is basically a tracker. This is very useful for us to itemise the start and end of tasks to evaluate the resources required, based on price. So it's very valuable. It is important to be able to inspect the items required in a project.

The communication could work better, especially for the development team. The important thing is that the tracker tools provide adequate communication, as do other tools. It seems to be lacking in DevOps and is an area which could be improved. We also need to improve publishing in production. In the future, we would like Azure DevOps to work with automated tasks regarding publishing. Better integration with existing source code is another area, which would benefit from improvement. The search repository could be more comprehensive, and visualisations could be optimised, further.

We have been using Azure DevOps for around two years. We are a Microsoft partner, so we use Azure DevOps as part of that partnership.

Stability is excellent. Initially, we had some problems with performance, but nowadays it's okay. Maybe they improved the server.

It's good scalability, but we need to improve the process by understanding it a lot more.

We never actually contacted support. The best plan is to read through all the documentation, but getting the right documentation for your specific project is not always easy to find, as there is so much to go through.

It's average, because we need to research what we are trying to achieve, and the platform has rich functionality. This is a good thing, but it can also mean setup is very complicated. However, we usually find that after testing more, we find our way around what we are trying to achieve.

Our deployment took about three months, as we tracked it. Following that period, we needed another month to integrate a new component into the setup. We implemented it ourselves, with one of our team. We have about 10 users using Azure DevOps, but we have 2 people to provide the deployment out of those. These are developers. We have a small team for DevOps, including the manager. We need our staff to be flexible and agile in our team to take on various DevOps tasks.

As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month.

We tried other tools, but Azure DevOps has a richer toolset, and it fits in better with our process. To some extent, as we are a Microsoft partner, we didn't seriously consider other options. However, we did look at Jira and Gitlab as potential alternatives.

I would rate Azure DevOps as an 8 out of 10. I would ensure that DevOps' use is planned, in detail, including the implementation before using the software. I would also ensure you have a thorough knowledge of the main components of the system. This will ultimately save hours of work.

My team uses this solution for the CI/CD deployment, and code check-ins.

We are also using Azure Boards for tracking our work, all of the requirements, the backlogs the sprints, and the release planning.

What I like the most is that it is easy to comprehend, and it's easy to use.

The simplicity is very good and the customer experience is also great.

I am not suggesting this solution should be cheaper. I would like to see a bucket of licenses. for example, 10 licenses or 100 licenses that could be monitored to know how many of those licenses have been used. The price would be deducted accordingly.

I should not have to contact Microsoft daily to request a license or two. There should be a mechanism in place where you are able to find out where you are out of 100 licenses, or that you have used 90 licenses in that year.

I should be given a credit line of 10 licenses at the end of the year or at the end of the month.

It should be easier to manage licenses, especially because it's in the cloud. You should know the usage and based on the usage, you should be able to make decisions.

I have been using Microsoft Azure DevOps for one year.

We are using the latest version.

It's a stable product. I have not experienced any issues.

This is an area that has yet to be explored fully. We haven't taken it to this level.

We are a team of 25 to 30 members, which is fine for us. Every time we scale up we need a new license and that takes time, it's not just a click and it's done.

I don't know if it will be scalable for 200 to 300 people.

Previously, I was working with Jira.

I was not involved in the installation. My team completed it.

Price is an area that could be improved. There are products on the market with a fixed price of 50 or 100 people, you are a bucket price. 

With Azure, you have to pay for every user.

It's good to have a bucket such as 50 to 100, or 100 to 200, and flexible pricing.

The issue may be from having more than one license. When you procure one license or two licenses, it becomes difficult.

It should be easier to procure a license, it should not be one by one. We don't know how many members I will have on my team three months from now.

We plan to continue using this solution.

I would recommend this solution, but I would not know their business needs.

Based on the various features, the deployments, licensing, pricing, and the customer experience, I would rate Microsoft Azure DevOps a seven out of ten.

The first time I used the solution was to create a build for an Oracle application called SOA. We generated all the features in Azure DevOps to create the build and then we created a workflow. We are partners of Microsoft and I'm head of technology.

We have the histories, and are able to estimate the efforts of each story. It means that I can measure it from each developer and I have the match from each developer. We can also check it from the lead time to see whether there are any problems in storage that may not be mature. It gives us control. 

We use Gitch as a version control and the integration is very good. We are also using the features for the product backlog that's released every day so we have the user histories. We can track it from the histories to the code. You can see all the steps in the life cycle we use with our clients. We also like to use the estimate integration feature where you have two or three developers that estimate different efforts for each history. I think Azure is easy to integrate with any other type of solution to improve your delivery.

I think the templates could be improved. It's not easy making the jump from one project to another so we're now integrating using a different partner. I believe the price could be improved when scaling. It's a simple calculation, the number of users times $11, which is approximately the cost. But if you have a large number of users you should be able to reduce the per user cost the more you scale. I think it's something Microsoft could do for us. 

I've been using this solution for five years. 

This is a very mature and stable solution. 

We have about 100 users; developers, engineers and admin. The platform doesn't require any maintenance but we have one DevOps engineer to support the DevOps for the applications that we integrate with the platform. There are two types of scalability, the first is scaling my team, moving from 100 to 200 users, which is easy to do. The second is structure but  I haven't yet tested scalability in terms of increased structure.

Actually, we don't have a lot of experience opening tickets with technical support. All tickets that we did open were dealt with quickly. 

I used IBM where I worked previously but didn't have a lot of experience with it. 

We had some initial difficulties, because the solution is not commonly used here. Jira and Microsoft are the most common solutions but it's not usual to use everything inside the platform. It was a cultural change that we implemented here in our team and to convince them was more difficult than to use the platform itself. We used an integrator for deployment but we don't do that in every case. In some of our deployments, hosting the most popular software development languages, like Java or .NET makes it easy to create the deployment mode. But when you have different platforms on development, it's more difficult to configure. We're on an SaaS platform, so deployment was very easy.

We have 100 users and the cost is $11 per user. There's an additional cost if you want to use the integrated test plan. You have the option to just change your license and you can use the automated test integrator.

We looked at Jira Confluence and it was our second option. On Jira, we have our environment in Azure, and it was easier to adopt Azure DevOps instead of Confluence. Because Confluence is specifically for Azure DevOps, we can integrate it with everything that we are already using.

It's very easy to start using this solution because the first five licenses are free. As a result, it's easy to track and compare with other solutions and it's easy to scale. 

I would rate this solution a nine out of 10.