Microsoft Azure DevOps Reviews

Being a project manager, it is necessary to create sprint, and kanban boards for management decision-making and our product life cycle. We use the solution for sprint backlog creation and bug reporting for IT department fixation. The dashboard is an interesting feature with visibility on the pending due dates. 

Since using this software, we have revoked the usage of MS Office tools and prefer to instead use Azure.

Azure is one of the few project management software solutions that provide a clear view of project standing, and sprint of product backlog as well. 

As far as my organization is concerned, we use this software for managing the project life cycle where we raise change request forms here and the IT developer provides the solution and from there we can conduct the UAT and sign off for closure. 

The entire product life cycle is being managed with task assignments so broader and a clear understanding of scope is provided by this software and the organization can better understand its current progress.

The available Kanban board is the best feature for management decisions. The sprint capabilities of the product break down the feature and characteristics of the product into steps and if any step is pending we may forward it to the backlog. 

Microsoft Azure is an Agile methodology, so multiple steps can be performed by different user segments in order to achieve the scope smoothly. 

More features can be included. We'd like to see better Kanban templates and an audio-video chat facility. 

The bug reporting facility can be enriched; there is nothing to mark "passed" "failed" the test cases. 

The dashboard can be enriched. 

Related links must be visible on the dashboard for integration purposes. 

I've used the solution for the last two years.

The stability is good.

The scalability is good.

Customer service and support are good. 

We did not use a different solution previously.

The initial setup is a little bit complex.

We worked with the vendor.

We have witnessed a good return on investment. 

This is good software for a reasonable price.

We did not evaluate other options. 

Azure DevOps is primarily used as a DevOps tool rather than an AI tool. It is used for source code management, setting up repositories and pipelines, and it can handle a range of workflows from the DevOps stack.

The tool helps by being an all-in-one solution where I can store secrets, code, and pipelines. This comprehensive nature has made it valuable and helpful by improving customer productivity and allowing me to perform multiple tasks without needing additional solutions.

Azure DevOps is highly valued for being an all-in-one solution. It offers capabilities like source code management, secret storage, pipeline management, and more, making it comparable to a multitool that does not require integration with other solutions. I appreciate it for its scalability and ability to handle different workflows effectively.

A notable improvement would be adding more notifications. It would benefit from more seminars or events where Microsoft encourages other users to transition to Azure DevOps.

I have been working with Microsoft Azure DevOps for around two years.

The stability of Azure DevOps is rated as stable and simple, with no complexity involved. I have not experienced any outages or downtimes in Azure DevOps.

Azure DevOps is highly scalable and receives a rating of ten out of ten. It can handle various volumes of workflows, which makes it effective for different use cases.

I have not communicated with technical support for Azure DevOps.

Neutral

Azure DevOps does not have a complex setup process. It requires Microsoft Azure for the services used, and the product itself is simple to set up.

The pricing of Azure DevOps is rated at five out of ten. It is mid-range pricing. It is considered to offer good value for money even if setting up an agent separately is required.

Our discussion mentioned Jenkins as a popular CI/CD product.

Azure DevOps is a very powerful tool with almost every feature necessary for DevOps, so it is recommended to other users.

I'd rate the solution eight out of ten.

We are mostly using Microsoft Azure DevOps for the development dashboard and for CI/CD pipelines. We also use it mainly for Git repository management.

We are primarily using Microsoft Azure DevOps for its Git repository management and CI/CD pipelines.

Service monitoring should be improved. This feature is available for Azure DevOps in the cloud but not on-premise. It can be enhanced to be used with on-premise solutions.

I have almost three years of experience working with Microsoft Azure DevOps.

This solution is stable. Its stability rating is eight out of ten.

I have not contacted Microsoft technical support; I rely on the documentation.

Positive

I did not use a different solution before using Microsoft Azure DevOps.

For me, the initial setup experience would be rated a seven out of ten.

The deployment takes only a few minutes. That said, it depends on the size of the artifact. If the artifact size is large, it will take a bit more time. We did not use any third-party services; we handled it in-house.

I have no idea about the pricing of Microsoft Azure DevOps.

I did not evaluate other options. We had to listen, as we were already using the solution.

I recommend Microsoft Azure DevOps. It is user-friendly.

I'd rate the solution eight out of ten.

We build CI/CD pipelines. It's the Azure DevOps phase. Everything is in one place, like version control. CI/CD Pipelines, Release Pipelines. Everything is in there. 

So we have everything in one place basically. We use it as a complete end product.

The first thing is that everything is in one place. Azure DevOps integrates Secrets management, release pipelines, and build pipelines. 

The CI/CD pipeline setup is more user-friendly. You can manage various stages, and there are over 400+ plugins available for each stage. It's more user-friendly overall, which simplifies setting up pipelines and managing the workflows.

There is room for improvement on the UI side, especially with merge requests. If we compare Azure DevOps to GitLab when it comes to branches and PRs (pull requests), GitLab has a better interface.

Regarding CI/CD pipelines, Azure DevOps is improving. They're adding new plugins and making overall upgrades. For instance, they used to have only one type of pipeline, but now they have YAML-based release pipelines. Build pipelines are still under development, I believe, but their roadmap is in good shape.

They're also integrating IAM enablement directly into the UI. So, if you want to use the Azure portal to produce roles or make similar changes, you can now do that within Azure DevOps. It's a positive development. Overall, the roadmap for Azure DevOps is very strong.

I have been using it for six years. 

The stability is improving and looks very promising. Moreover, it's free. Initially, a subscription was required, but now Azure DevOps is provided for free if you are using the Microsoft Azure cloud and have that option enabled. 

So, it's a very stable product.

It's agent-based. You must manually configure a pool of agents to run all your pipelines and deployments anytime. There have been some disturbances with the agent pools, but they are improving. 

Initially, there were many issues with agent pool stability, but now, as you increase and update your agent pool, it becomes more robust. There isn't automatic scalability; you must ensure the agent pools are properly configured initially.

Myentire organization uses it because many projects under this organization use Azure DevOps. There are more than a thousand end users. 

The customer service and support are pretty good. There is a bunch of documentation out there. 

It is not to complicated to use. If there is something required, the support is accessible. 

I used Kitlabs, GitLab, GitOps, Jenkins, and Central Station, among others.

We looked at the features, and for one, Azure DevOps integrates all development and operations for continuous deployment in one place, which none of the other products offer in the market.

For Git, we needed repositories. 

The initial setup is of medium complexity compared to others. It's not too complex, nor is it too easy. It's a medium setup, and it includes all the key features. You can create departments, projects, and programs—everything is taken care of with Azure DevOps. 

It's like ServiceNow for continuous improvements and deployments in the DevOps world. Every project and support request I handle for clients has its challenges, but Azure DevOps manages these effectively.

Deploying code to your endpoint is a one-person job. You can configure your system, integrate your CI/CD pipeline, and set up authentication on your own. 

However, at an organizational level, where roles need managing and permissions must be assigned—for example, some can only handle releases while others manage builds—you need a robust access control system. 

In such cases, you would need two to three administrators to handle everything.

People involved in the process would be Azure DevOps admins, who control everything related to permissions and Azure DevOps operations, such as setting up pipelines, running deployments, etcetera. While our application teams handle some tasks, issues like access problems or agent failures are taken care of by the admins.

I would recommend using it.  Overall, I would rate the solution an eight out of ten.

We use the product end-to-end, from project management to CI/CD. We use the tool to create sprints and iterations, track bugs and issues, close down sprints, and have complete CI/CD pipelines end-to-end for all our branch's build releases.

The solution works smoothly. We have been using the tool for our projects since day one. It's easy to move around in the tool. All our projects are 100% on the cloud. Azure DevOps is an end-to-end solution. From project management to CI/CD, everything is connected. It speeds up our development and tracking.

The CI/CD feature is the most valuable for my team's productivity. All the features are helpful. The tool is helpful even in the test cases. We use Azure DevOps because it gives us everything in one product. Source control is useful. The tool enables us to track the projects end-to-end. We can track everything from the requirements stage to the production stage.

Azure Artifacts must be improved. When we do containerization or imaging, it is not friendly with Docker images. It might be because we are using open-source tools. There is no document that explains how to connect to Azure Artifacts when we're building a Docker container. 

The documentation must be straightforward. If we look online, it is very difficult to find or understand. The only way to connect to Azure Artifacts is to create a personal access token. Something doesn’t feel right with having the personal access token in the NuGet.config of our projects. However, it works fine.

I have been using the solution for 10 years.

The product’s stability is good enough.

The product is scalable. We have more than 40 users in our organization.

The setup is straightforward. Using the task and building the pipeline is not an issue. We spent a week trying to find out how to connect to Azure Artifacts. We need a normal .NET Core API and have the Docker file built. We must use a personal access token and keep it in the config files. It is not smooth enough.

The ROI is good enough. Once the system is set, we can focus on the core products.

We pay yearly licenses. The tool could be cheaper.

Microsoft Azure DevOps is the best choice because it is an end-to-end solution. Everything is integrated and trackable from every point. Right from my operations team to developers, everyone gets a clearer picture of everything. Overall, I rate the product a 9 out of 10.

We are using Microsoft Azure DevOps for project management using Azure Boards, CI/CD pipeline, repository, and test plans.

The most valuable feature of the solution is the pipeline. The solution integrates well with other Azure services and third-party tools.

The solution's roadmap and Gantt charts could be improved. We recently started using Azure Test Plans, and we're not seeing a lot of good dashboards in it.

I have been using Microsoft Azure DevOps for five years.

I rate the solution an eight out of ten for stability.

It is easy to scale the solution by increasing the number of agents. Our clients for Microsoft Azure DevOps are enterprise businesses.

I rate the solution a nine out of ten for scalability.

It took a few weeks for us to do the solution's initial setup.

Compared to other tools, Microsoft Azure DevOps is a cheap solution.

Microsoft Azure DevOps gives us an end-to-end solution. We could write the epics feature and user stories. From there, we could create the batches in the repository and create a pipeline to deploy. We can also use test plans to test different application scenarios. We are using Microsoft Azure DevOps as an enterprise-level solution.

Azure Boards have been good at improving our project tracking and agility. We are using the Azure repository, and it's working well for us. Microsoft Azure DevOps is deployed on the cloud, and we are using a Software as a Service (SaaS) version.

I would recommend the solution to other users because of its pricing and because it is an end-to-end platform for everything, including project management.

Overall, I rate the solution a seven out of ten.

It's part of my new role as a DevOps engineer and the cloud engineer. We're migrating our on-premises applications to the cloud-based M365 platform, built on Microsoft Azure. That's the primary use case.

Azure DevOps supported our agile project's sprint planning and management. It introduced automation, which is still a little bit immature. But our previously manual tasks are now automated, and we've transitioned from deploying ITFAX applications to containerized deployments using images. These are just a few examples.

Moreover, Azure DevOps facilitated our team collaboration and tracking of work items in our projects. We've got the backlog, the boards, the item backlog items, you know, you can see what's approved by the product owner, what's on hold, what's in progress, what's developed and deployed to whichever environment, nine product or product and stuff like that. 

So, it's been visible for all to see, from my manager to product owners, technical product owners, developers, and testers; every stakeholder has visibility.

Ever since we adopted Azure pipelines, we saw faster releases. Something that would take us two or three weeks to deploy; we can do it in a couple of hours now. So, the primary benefit is definitely faster development and deployment cycles.

It boils down to - increased customer satisfaction. Quicker releases to testing and production environments - that's the benefit, that's the impact.

After each commit, the code automatically goes to Azure DevOps. We can then manually trigger the pipeline if needed. Once the pipeline successfully passes all tests, it deploys the new container image to production, replacing the previous one.

While I'm just gonna stick to Docker, it has really helped developers to confidently commit whenever they feel the analytics are okay to work. On their machines, it records any environment, unlike the old way where we had to click on our machines and then involve the operational team, which sometimes didn't work. With containerization, we already know all the application dependencies needed on the image. It's just one, OS or environment independent.

Moreover, we've experienced the general benefits of Azure Test Plans. One major improvement is the automation of tests. Once automated tests pass, the code progresses to the next stage, minimizing human error inherent in manual testing. This automation extends to reporting as well, providing clear and readily available results. In terms of reducing human error and streamlining reporting, I'd rate Azure Test Plans a ten out of ten. 

Additionally, detailed logs allow us to pinpoint the exact cause of any issues, making troubleshooting efficient and accurate. So, for both error reduction and insightful reporting, I highly recommend Microsoft Azure DevOps.

There is only one key area of improvement for me. The new imaging thing is that there is DevOps, where security is important because it is always lasting. So, to integrate security in our DevOps, that would be nice.

I have been using it for more than a year.

It is a stable solution. However, there is always room for improvement. I would rate the stability a nine out of ten.

It is a scalable solution. There are over a hundred end users in my company. Every IT hub uses it. 

The customer service and support were quick to support. Usually, we don't need the support. We google our query and easily find the solution on official Microsoft page. So, we hardly need any support. 

In my previous jobs, yes, we did use different tools. We had a separate team for DevOps team. There was even a "deployment specialist" who dictated deployment times and windows, which could be quite restrictive. So, switching to Azure DevOps has been a massive improvement.

The initial setup is easy. Once the code is committed and the developers sign off, we just go to Azure DevOps, click on "Pipelines," and run the pipeline. That's all, pretty straightforward.

The deployment can be done in-house. However, I was not involved in the deployment process. I'm utilizing it, and so far, it's easy for me.

The pipeline itself can be managed by one person. But when it comes to the entire Software Development Lifecycle (SDLC), from data requirements gathered by the business analyst, system analysts, solution architects, and so on. That part is still manual, it's not automated, and you can't just throw technology at it and expect a one-person team to handle it. 

However, for running the pipeline end-to-end, from CI to CD, Azure DevOps allows a single person to manage it. However, developing the application from concept to reality still involves a lot of stakeholders across Azure.

Overall, I would rate the solution an eight out of ten. I would strongly recommend using this solution. 

Previously, our DevOps operations relied on TFS and Visual Studio systems. However, with the rise of cloud computing, Microsoft introduced Azure DevOps, a comprehensive solution encompassing version control, reporting, requirements management, project management, and automation tools, including testing and release management capabilities. It integrates seamlessly with Azure services, facilitating the development and deployment of applications on the cloud platform. It supports the entire software development lifecycle, from development to deployment. For instance, when developing a project, it assists in the build, test, and release processes, ensuring smooth progression to higher-level environments. 

Additionally, it supports project management activities such as user story management. Its features include repositories for storing code, pipelines for automating processes, and environments for managing deployment configurations. 

The platform has improved our team's productivity in the versioning system within the release management functionality. Each application deployment is assigned its version. When certain features are unavailable or require enhancement in a deployment, Microsoft incorporates these improvements into the subsequent version of the release pipeline. 

They could provide clearer guidance on deployment practices for the product. Currently, two main deployment methods are available: YAML server deployment and release management using pipelines or Terraform. They should offer recommendations on which approach is the best practice for deployment.

We have been using Microsoft Azure DevOps for 5 years.

It is a stable platform. Being a cloud-based solution, it benefits from zone redundancy policies, ensuring continuity even if one server experiences downtime.

We have more than 35 Microsoft Azure DevOps users in our organization.

The initial setup process is easy.

The costs are moderate and justify the value provided. With Azure DevOps, we can easily track your projects, monitor statistics and reports, manage backlogs, and plan deliveries. We can manage larger teams under one platform.

The product documentation contains all the necessary information to get started with the platform and understand its evolving features. Additionally, numerous resources are available on platforms like YouTube, where various vloggers share valuable insights and tutorials on using Azure DevOps effectively.

I rate it an eight.

As a software development team, we use Microsoft Azure DevOps extensively across various functions. We rely on its capabilities for source control, enabling us to efficiently manage our codebase and facilitate collaboration. Additionally, we leverage Azure DevOps for test management, including the creation and execution of test cases and test plans. Furthermore, we utilize its features for project planning, tracking work items, and generating weekly documents to ensure smooth progress tracking.

Azure DevOps has been instrumental in facilitating agile project management and collaboration within our team. We extensively utilize all the features offered by Azure DevOps, enabling us to seamlessly handle tasks such as test management, project management, software defect resolution, and source code management throughout the software development cycle.

We are leveraging the capabilities of Azure Repos for our source code management needs, finding them highly advantageous for our workflow.

Azure Pipelines have significantly improved our deployment process by enhancing automation. We utilize Azure Pipelines to standardize our build process, ensuring consistency in our artifacts and maintaining high-quality outputs. Additionally, it has enabled us to enhance our testing procedures, leading to more efficient issue detection and resolution.

Azure Test Plans have significantly influenced the quality of our releases. Acting as our test engine, they have played a crucial role in ensuring the quality of our software. Post-release, all identified defects are thoroughly addressed, and developers are requested to provide corresponding test cases to prevent recurrence of issues.

Azure Port is considered the most valuable feature.

When comparing with Jira, I find that the task management capabilities in Azure DevOps are not yet fully comprehensive and should be enhanced.

We have been using it for three years.

It provides good stability. I would rate it eight out of ten.

I would rate its scalability capabilities seven out of ten. Currently, approximately ten individuals utilize the platform. However, we plan to expand its usage in the future.

The initial setup was fairly complex and time-consuming. I would rate it four out of ten. During the initial setup, we encountered the most difficulty with Microsoft's documentation. It proved to be quite lengthy and lacked clear guidance, which made the setup process challenging. Consequently, we had to explore various additional resources to ensure a smoother setup of Azure DevOps.

For our initial deployment, we allocated one DevOps engineer who dedicated approximately one and a half months to complete the setup.

The cost is quite affordable.

The initialization process may pose some challenges, but I find that the investigation aspect is handled quite effectively. Overall, I believe it's well-suited for both general and specialized DevOps use cases. I would rate it seven out of ten.

We use it for automating our code builds, significantly enhancing collaboration, and accelerating our release cycles. By reducing release times, we're able to ship our product faster, thereby increasing productivity and efficiency.

We use continuous integration and continuous deployment through Azure DevOps. With CI, we gain the advantage of fully approved code merges, as demonstrated in your demo. This ensures clarity on which releases are destined for production. With continuous delivery, we seamlessly deploy to both our test and production servers.

Azure DevOps supports our agile project management and sprint planning processes. This enables us to release sets of features more efficiently and quickly within the Agile framework. Additionally, DevOps facilitates the approval of features, further streamlining our release process.

When using the Agile template, we have visibility into what tasks are available, in progress, upcoming, and completed. This comprehensive view allows higher management to easily track the current status of tasks, including which ones are being worked on and which are finished.

It significantly enhances the testing phase of our software development lifecycle. Previously, after development, we deployed our software to a common QA environment for testing. However, now with Azure Test Plans, we can create isolated environments for each solution using virtual machines. This isolation helps us identify and address issues specific to our product, without being hindered by environment-related issues. With continuous integration through CI/CD pipelines, once our build is completed and approved, it automatically deploys without manual intervention, streamlining the process further.

Since adopting Azure Pipelines, we have observed significant improvements in our release management process. Previously, the process involved various stages and multiple approval steps, leading to fragmentation. However, with Azure DevOps, the entire process is streamlined, allowing for seamless transitions from board check-in to release approval within the same solution.

Before using Azure DevOps, we couldn't release as swiftly as we can now. With Azure DevOps, our ability to release has significantly improved. This increased efficiency means we can release more versions of our product, leading to higher productivity and the shipment of more artifacts than before.

The features that have a significant impact on us include CI/CD, where we have full integration with the source code repository and Azure Pipelines. This enables us to efficiently review and approve source code for deployment and testing. Utilizing Azure Test Plans, we can deploy to virtual machines, facilitating streamlined processes in a dedicated environment.

At times, our development work encounters issues, particularly when executing numerous CI/CD processes. Occasionally, these processes may experience delays or errors, often stemming from unavailable features or functionality in the cloud environment. Improvement in this area is necessary for smoother and more reliable operations.

We have been using it for two years.

This solution is stable. However, as mentioned earlier, configuring multiple CI/CD pipelines, with numerous processes running concurrently, can occasionally lead to issues.

Being cloud-based, this product is highly scalable, offering the flexibility to scale horizontally or vertically as needed. With a relatively small team of ten to twenty users, the scalability of the product aligns well with our requirements. It is widely utilized by both developers and the QA team.

The initial setup varies depending on the complexity of the workload. Some cases are intricate and require significant time to develop the end product or work item. Conversely, there are simpler, smaller cases that can be completed quickly.

For deployment, assistance from Microsoft or a system integrator is essential. Customizing templates and processes requires their full support to tailor them to our specific requirements. Since it's a cloud-based solution, the need for managers is minimized as management becomes simpler. A team of two to three individuals is sufficient for configuring it effortlessly.

The licensing for this product is on a monthly basis. It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware.

 Overall It offers a comprehensive array of features with accessibility and support for customizations and performance enhancements. Its extensive feature set covers various aspects, making it highly versatile. I strongly recommend Azure's demo for exploring CI/CD pipelines, boards, and customization options. It will undoubtedly streamline development activities, reducing effort and boosting productivity significantly. Overall, I would rate it eight out of ten.