Microsoft Azure DevOps Reviews

A common use case of Microsoft Azure DevOps is the use of work items and then connecting them to Git repositories and their updates. It is primarily used for item and code management.

The work items option is incredibly flexible.

There are multiple add-ons available.

It is easy to use.

The entry point is adequate.

When you compare with Jira, there is a lack of progress features.

I would like to be able to customize the product using add-ons or a similar mechanism.

Scalability is an area where they could advance and make changes.

Unfortunately, managing users in Azure is a very complicated issue. We also have a problem with one of their other tools, which is Teams. The Team messaging has caused us some trouble because they have what is called organization, in addition to the users, but it doesn't work very well.

Technical support needs improvement.

I would like to see scalability, dashboards, KPIs, measurements, and some visual management assistance improved in the next release.

I have been working with Microsoft Azure DevOps for one year.

We are using the latest version.

Microsoft Azure DevOps is a stable product.

This solution is used by 20 people in our organization.

It appears to be simple, but based on the work items and project management aspects, I believe there are few options for scaling it up in terms of dashboards and KPIs.

I contacted technical support about managing users in Azure. Unfortunately, they were able to resolve this issue for us.

We tried several times and we did not get the answer we expected to get.

I use Jira as well as TFS.

The initial setup is straightforward. It is simple to install.

Other than the initial setup, it does not require any maintenance.

It was implemented internally.

The majority of the components are reasonably priced. Testing is one of the more expensive components. When you compare it, it is approximately $3 per month for the other components and $45 or $50 for the Testing component. It costs ten times as much as the other components.

I would recommend this solution to others who may be interested in using it.

I would rate Microsoft Azure DevOps a seven out of ten.

The plugins are the biggest thing. I like how Visual Studio is designed as a shell application, and then the plugins make it do what you want it to do.

Microsoft could improve Visual Studio by making it easier to find the plugins you need to get your job done. Maybe they could implement an AI search instead of a simple tech search. Sometimes, people come up with a catchy name for something, and you don't know how it's spelled. For example, a developer might come up with a packet wizard and spell weird, like P-A-K-I-T.

I've been working with Microsoft Visual Studio since it first came out in 1997, so about 24 years.

Visual Studio is very stable.

I don't think scale applies to Visual Studio because it's a developer tool. And I haven't had a lot of experience with massive projects where multiple teams are working on the same source code. I've only worked on a team of a few people.

I think support is probably pretty decent, but I've never had to use it. I just look at Visual Studio's source code to troubleshoot it. 

The setup is pretty straightforward. Visual Studio runs pretty fast.

I'd say Visual Studio is a nine out of 10. If you're thinking about adopting Visual Studio, research the kind of functionality you need. The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in.

We use the solution for performance testing in general.

One of the main features is the user interface is very good.

The user management in the solution could improve.

I have been using it for four years.

The support for this solution has been fine.

The price is reasonable for the solution.

I rate Microsoft Azure DevOps a nine out of ten.

We are using Azure DevOps for continuous integration and continuous deployment.

Microsoft Azure DevOps has helped the developers a lot and we are deploying process changes very frequently and simultaneously. A lot of my team members that are developers are updating the code in parallel using Git. Additionally, Microsoft Azure DevOps is providing a very good approval mechanism. Overall it is benefiting by creating efficiency in production deployment and applications, our new releases are running well. The security of secured is good.

We are facing a lot of issues in the development of containerized solutions. We are facing a lot of challenges in this area. They could make the process simpler.

I have been using Microsoft Azure DevOps for approximately four years.

The technical support from Microsoft Azure DevOps is good. Whenever we have raised a ticket with priority, we had a very good response from the technical team. My experience with Microsoft support is very good.

The integrations of Microsoft Azure DevOps are good and the implementation is not difficult. The testing of the solution went well.

I have seen a return on investment from using Microsoft Azure DevOps.

We have spread the knowledge about Microsoft Azure DevOps to a lot of our customers. We have organized a lot of training sessions because we are Microsoft's gold partner. That is why we promote all the tools and technologies which are part of Microsoft and we're also using them.

I rate Microsoft Azure DevOps a nine out of ten.

I have been working with it for different projects and purposes. I'm basically the main architect for such solutions.

It is stable. I like Azure a lot. All our guys are Microsoft certified. 

It is fairly new, so there are a lot of changes, and because it keeps on changing, you need to adapt to those changes.

Its setup is quite complex.

It is stable.

We never used Microsoft's technical support. We always get it right.

Its initial setup is quite complex. There are a lot of caveats. Even if I can call a setup out of the box, it is not really out of the box.

We managed everything on our own. It involved fitting other products with the existing product. If you don't encounter problems, you're not going to learn.

We are 100% satisfied with it. I would rate it a nine out of 10.

We are using the tools in this solution mostly for planning our software projects by implementing Scrum. We use repositories, and create timelines for continuous deployments and integrations.

The reports have been most valuable. We have created some dashboards allowing us to be able to check our teams, their progress, and mission plans.

Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult.

I have been using this solution within the past 12 months.

Microsoft Azure DevOps is highly stable.

The support from Microsoft is great, if we need to solve some problems with Azure they are ready to help us. The support has been excellent.

Previously we used Visual Studio but then we changed some of our repositories for our projects to the cloud and now we use Microsoft Azure DevOps.

The solution is easy to install and it took us three months to implement. This includes the support for our teams and for them to come up with their strategy to manage our projects.

My advice to others wanting to implement this solution is they need to think about their inter-process before moving to this kind of solution. In many cases, we start to configure some projects using the tools, but if we do not have our roadmap and do not define our goals, we cannot take full advantage of the tools. There should be a lot of planning before moving to the projects.

I rate Microsoft Azure DevOps a nine 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.

We are currently involved in a financing exchange project, and we use this solution to keep track of the exchange activities within the backlog. We are not taking advantage of the repository and the code stuff at this stage. 

The most valuable feature for us at this stage is the Azure Boards.

I really like the user interface. For comparison, I have been using JIRA for several years now, and I am rather skilled at using that tool. The reason for my using Azure DevOps is because my client uses it. My first impression of DevOps, after using JIRA, is that it has a much better, more intuitive, and more user-friendly interface. That first impression is still valid, today.

There is a lack of integration and portability with other tools and products.

I would like to see better interoperability with the agile scaling frameworks.

When I first started using Azure it was impossible to figure out how to do the configuration correctly. Perhaps there should be a configuration environment that hides some features and is not open for everyone.

I find it difficult to find some of the features, although it may be that they are not enabled, or perhaps I have to take some time to better understand the tool.

I cannot really comment on the scalability of this solution. We are running in a microenvironment with only a few users and a few integrations. It is enough for us at the moment, but if we want to go forward and continue to work with it then that will be a discussion for later.

We have approximately fifty users right now. There are three or four administrators, and the remainder of them are end-users.

I have not contacted technical support. Coincidentally, I needed support today, so I went online to find the answer. The toolkit for helping yourself is there, but perhaps it should be more integrated into the solution.

I have used JIRA for several years, and although I am impressed with the interface in Azure DevOps, JIRA still has better integration with other tools.

The initial setup for this solution is much easier than for that of JIRA.

My advice for anyone implementing this solution is to have an expert for every fifty users of the solution. This person is responsible for configurations and so forth.

If you have a Microsoft environment then this is an easy choice for you, but if you don't then I think that JIRA would be a better choice.

I would rate this solution a seven out of ten.