Microsoft Azure DevOps Reviews

We manage the full scope of all our projects on Azure DevOps, including all of our kits, bags, and user storage. DevOps encompasses the CI/CD process of every build as well as the customer requirements, QA, and deployment.

Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy.

I've been using DevOps for approximately four years.

Azure DevOps is mostly stable.

We've used Microsoft support but for .NET Core or Azure DevOps.

Installing Azure DevOps is pretty straightforward at the installation or admin stage. Deployment time depends on the service on my side, so it's mostly very fast.

It's a great product for the CI/CD process, but DevOps lacks some features for project management, guide, user story, etc., so it's far from perfect. Compared to monday.com, JIRA, or others, they have some work to do.

I do not recall which version we are using. 

The solution is good for everything, including end-to-end planning and its deployment and testing. 

I like that the solution is stable and that all ends of the process are integrated seamlessly into the tool. These are the solution's greatest strengths. 

The solution should have fewer updates. We need the updates for July. Microsoft tools are sometimes too feature heavy and offer more features than the person actually needs to use. This is why I did not rate it as a ten out ten. 

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We initially found ourselves struggling with this process.

I have been using Microsoft Azure DevOps for around two years. 

The solution is very stable. 

The solution is very scalable. 

I feel the technical support to be fine. We have not encountered any issues in this regard. 

Prior to Microsoft Azure DevOps, we were using Jira and, before this, KFS. 

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We struggled with this initially.

The installation was undertaken by a consultant. 

There was a team of, perhaps, five engineers involved. 

I am not aware of any licensing subscriptions for the solution. 

I would very much recommend the solution to others. 

I don't see the need for more integration with other platforms, as the solution is already pretty well integrated, at least, that is, for our needs. 

I rate Microsoft Azure DevOps as a nine or ten out of ten. 

With the query feature, we have to group items, so it becomes difficult for everyone to understand it. It's easier in JIRA, which has filters and other query options. So, I think this query option should be there in the DevOps also. Also, I don't like the DevOps' boards at all. It's more complicated than JIRA, I think. So, DevOps can improve in terms of its boards, work items, and filters. 

Then there is also an issue with user access. We have about 10 to 15 users that we can add to DevOps. But only the first five users have basic level access, and the rest have stakeholder access. That means they can change the task status but not add or do anything. I think Microsoft should remove this restriction from DevOps. With the access restrictions, it's tough for us to add any status for our users or filter anything on the boards. So, Microsoft should add this functionality for the other roles as well.

DevOps is a stable solution.

It's average. It's not better than JIRA. It's average because many things need to be improved by Microsoft in all their products.

Setting up DevOps is easy. 

We pay for DevOps when we use it for our clients. But for personal and internal projects, we can use the free version. But there are restrictions on the trial plan. It should also be available for free use. However, the trial version of DevOps is free for only five basic users. So, I think it should be free for others also. And other extensions like test plan creation should also be available for the basic users, at least. We have to purchase the license for this.

We use both JIRA and DevOps. The main difference between DevOps and JIRA is the test cases. You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases. You can develop releases from DevOps but not from JIRA. At the same time, JIRA's jQuery is the best. I don't like the grouping and filtering in DevOps. 

I rate Microsoft Azure DevOps seven out of 10. I would recommend it to others. It's a nice and helpful tool.

In the first years, we had the solution, we did not use it for all of its models - not for the full life cycle. Now, within the past year or year and a half, we wanted to make the best out of it. We now use all the models and all the development lifecycle.

The product has integrated all the relevant models of task management requirements, source control, back management, test management, et cetera. You have a full ALM suite.

The connection to Git, which was bought by Microsoft, is also good. We use Git as a version control tool. 

Microsoft has good integration with its other products, such as Office, Teams, et cetera. 

The solution has proven itself to be very mature and robust. It's quite stable.

The scalability potential is very good. 

I'm not sure if "missing" is the right phrase, however, I am interested in, with all of these tools, if the connection to requirements management tools like DCRM, DOORS, et cetera, would be possible. That's a weak spot in most of the vendors.

We would like some bidirectional synchronization. It's the requirement if you want to analyze it to software requirements, et cetera. That's something that most of the tools aren't that good at.

I've been using the solution for around three or four years at this point. It's been a while.

The product is mature and robust and quite stable. I haven't experienced any problems at all with it. It doesn't crash or freeze. It doesn't seem to have bugs or glitches that affect it. We have the support in-house on servers and we haven't had any problems with defining collections for example.

It is my understanding that the solution is very stable. As an example, our organization has many teams and many departments and we use it across them all the time with no problem. We started using it originally when we had several teams, and now we have tens of teams, and it scaled up to meet our needs and we haven't had any issue with doing so.

We also use Jira. I myself do not use Jira, however, it is used by other teams and colleagues within our organization.

I can't speak to the implementation process, as our IT handled it. I was not a part of the initial setup. I can't speak to if it was complex or straightforward, or how long it took to set up.

We are currently evaluating both Jira and DevOps against each other. We use both in several development units. Lately, I've been looking for some comparisons and reviews, and material regarding those platforms and the comparison between them. I'm wondering to myself whether it's good for our company to have both, or to choose one of them to be the standard platform of our company. That's the main subject that I'm interested in.

We are customers and end-users. We don't have a business relationship with Microsoft.

I'm a manager, and therefore I don't personally use it on a daily basis anymore, however, I manage teams that work directly with the product.

I'd rate the solution at an eight out of ten. If I compare it against other products, it holds its own. It's quite a good solution overall and we've been happy with its capabilities.

I would recommend it to other organizations or companies. I'd advise them, however, to use the source control and to wisely choose which kind of collection they want to set up and configure. It's something very important that will set a company up for success. 

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

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.

With Azure DevOps, I plan and track my project using Azure Boards, manage my code with Azure Repos, and automate build, test, and deployment processes using Azure Pipelines. This streamlines my development workflow and ensures efficient collaboration and project management.

The most valuable feature in automating our build and release processes with Azure DevOps is the scheduling capability. At the end of each sprint, we schedule automatic releases to QA and development environments, ensuring our latest code gets deployed without manual intervention. Additionally, triggering pipelines upon code upload to the main repository adds significant value to our development workflow.

Azure DevOps could be improved with more security plugins, especially for SaaS scanning and vulnerability scans.

I have been working with Azure DevOps for two years.

I would rate the stability of Azure DevOps as a ten out of ten.

I would rate the scalability of Azure DevOps as a ten out of ten. At our company, it is used daily.

Technical support from Microsoft is very helpful, especially when I need assistance with tasks like migrating work items between Azure DevOps and other platforms. I would rate the support as a ten out of ten.

Positive

The initial setup is easy. Deployment typically takes around ten minutes at most. We have set up an automated process that recreates everything, so even if there is damage to the VM or target machine, we can quickly retrieve and redeploy everything ourselves.

We require about two DevOps engineers to maintain Azure DevOps for our company, which has around 400 users in total.

I would rate the costliness of Azure DevOps at a seven out of ten.

We ensure the security of our company's source code uploaded to Azure Repos by using a SonarQube Plugin and then automate its deployment to various environments like development and QA. Once approved by QA, we deploy to the production environment, passing through our firewall for protection. This streamlined process ensures efficient and secure CI/CD pipelines with Azure DevOps.

Azure Boards has significantly improved our project tracking and adjustability. It is a powerful tool where we can easily trace work items and monitor the progress of our projects.

Azure Boards is a powerful tool for tracing work items and project progress. It simplifies uploading and versioning of project assets and tools, enabling easy refreshes or benchmarks.

Overall, I would rate Azure DevOps as a nine out of ten. I would recommend it to others.