Microsoft Azure DevOps Reviews

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.

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.

We are an agile shop. We use it to build our sprints and for our user stories. We have everything aligned in epics and we track all of our requirements and our velocity.

We are still getting used to it and there is a lot that I haven't looked at yet. For me, at this early stage, the most valuable features are the basic functionality. This includes the ability to build and customize sprints.

I like the tracking and that we can monitor our velocity.

It took a bit longer to figure out, but now that we have, it's easy to use.

When converting to DevOps, it was difficult to map.

I have been using Microsoft Azure DevOps since October 2020 when we converted from Jira to DevOps.

It's stable now that it is up and running. It was a steep learning curve, but not the fault of DevOps. We did not put together adequate training.

Others in the company may have scaled this solution. I have not explored this area yet.

I have not contacted technical support.

Previously, we were using Jira. Now that DevOps is running, I find that for what I am doing, does the same things as Jira. The main difference is in naming convention and layout.

I wasn't part of the conversion from Jira to DevOps but it was a painful process. We lost data, things didn't map. My Scrum Master who used it was not happy with the process.

I would rate Microsoft Azure DevOps and eight out of ten.

We primarily use Azure DevOps for the early phase of software development projects. We don't use it for building the software. Rather, it is for development support. It handles management of the features, the composition, the definition of requirements, and checking our requirements against the use cases. 

Since it is a cloud product, it is constantly updated and not the responsibility of the user.

The quality of the user interface is very good.

It is a well-integrated product in terms of the development lifecycle. There are different functional areas from the requirements to finish including test management, product development, and deployment. I do not personally make use of all of these components together, but I understand from my colleagues that make wider use of it that everything integrates nicely.

It lacks integration with Office 365. It would be very useful if it had better integration with Microsoft Word because we would like to be able to define the priority requirement document and add it to different stages of the backlog. Currently, it is difficult to do this. There are some third-party products for this but they are either quite expensive or do not function properly.

I would like to see the requirement management links between work items improved.

An API to develop custom functions would be useful because we work with a large integrator that uses TFS, the on-premises version, and have seen what they do. One of the advantages of it is that you can develop using the XML approach to customization. Essentially, the customizability is more in-depth. This could be done, even without going to the code level, if they provided an API or and SDK. Although the interface currently used for customization is good, we sometimes find it limited. It would be more complex to use but also allow for greater potential.

I have been using Azure DevOps services for two years.

This is a stable service.

I would say that it is scalable. On a recent project, we had a lot of users and did not experience any issues in terms of performance.

I have only been in contact with technical support on one occasion and they gave me a good and prompt answer. From my experience, I can say that I am satisfied.

I do not personally have experience with other products, although the company has some experience with Jira.

In summary, this is a good product but I would like to see better Office integration and API support.

I would rate this solution an eight out of ten.

The Repos, Wikis, and pipelines are all excellent features.

The solution could work to improve their reporting.

The stability of the solution is good.

The scalability of the solution is good. I would give it a four or five-star rating. We have plans to increase usage. Right now we have about 100 users on the solution.

Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support.

We did not previously use a different solution.

The initial setup is straightforward. We just implement it from the cloud. We took it and configured it with our local website infrastructure, so there was nothing much to do.

There is a licensing fee of $6/user per month. That's not too much money for us. There aren't really any additional costs beyond that.

We considered using Jenkins, but we decided to use Azure DevOps because we have an enterprise agreement with Microsoft. It was much easier.

We are using the public cloud deployment model.

Potential users should not hesitate to move to Azure DevOps. It keeps on progressing and keeps on adding new features all of the time, so it's a solution that I would highly recommend people use.

I would rate the solution eight out of ten.

We primarily use the solution for our internal development and we have some clients that require some consulting around some DevOps functionality.

We use the product for the development process for the repository, for the tracking of the tasks in the boards, and for the pipeline for CINCD.

The test plan is one feature that we are exploring more right now. This is a great feature that we want to deeper into.

We have a solid base. We can do everything with DevOps.

It is possible to add third-party extensions to increase the usability of the product.

The initial setup is very simple. 

We have found the solution to be scalable.

The solution, for the most part, is stable. 

Some things, like project management, tasks, progress, and having work progress views, require us to use some external tools or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps. They need to expand the solution's offering.

While I have used the solution for two years, the company has some personnel that have used it for longer. Our development team may have used it for four or five years. 

The product is stable. We had some regional degradations a few months ago, however, it wasn't too much. For the most part, it's reliable and there aren't bugs or glitches. 

The solution is scalable. If we need to expand it we can do so. 

We've never had to contact technical support. I cannot speak to how helpful or responsive they would be, as I've never dealt with them directly. 

The initial setup is very simple and straightforward. It is not difficult or complex. 

We use the online version. We don't have to deploy the tool. We don't have to put in a lot of effort as we already have the pipelines in the TFS. We just move it to Azure DevOps. 

I'm a solution provider. I sell Azure DevOps and I have a client that was looking to analyze some differences between Jira and Azure DevOps. Therefore, I have evaluated Jira a bit for them.

We are both a reseller and a partner of Microsoft.

We always use the latest version of the solution. 

I would recommend this product to other companies and users. If a company or a team doesn't know how to work with Azure DevOps, the advice I would give is to find someone that knows the tool and do a POC first to make sure you understand everything a bit better before diving right in. 

In general, I would rate the solution at an eight out of ten.