Microsoft Azure DevOps Reviews

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.

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

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.

We use Microsoft Azure DevOps as a code repository, for task and work management, software tests, and documentation.

The most valuable feature of the solution is task management.

The solution could be made faster because it can be a little unnerving to browse through too many pages and press too many buttons.

I have been using Microsoft Azure DevOps for six years.

Microsoft Azure DevOps is a stable solution.

I rate the solution ten out of ten for stability.

Microsoft Azure DevOps is a scalable solution. In my current company, around 30 users are using the solution. In my previous organization, more than 100 users were using Microsoft Azure DevOps.

The solution makes you faster. You can organize your work in an easy and shared way. You can configure different types of access to allow some people just to read and to be able to modify some things. Since the solution gives you all the benefits of Git, you have a commit history.

We have an MPN subscription for Microsoft Azure DevOps, and it's all included.

Microsoft Azure DevOps is deployed on the cloud in our organization. The product supports our agile project management practices very well. We can configure a process, and it would give you some different types of tasks, like the epics feature, user stories, and tasks. We need very little staff for the solution's deployment and maintenance.

For source control, we use Git repositories that are perfectly integrated into our IDE, Visual Studio 2022. Everything is available, and we can create or pull requests from Microsoft Azure DevOps. We can also manage, reject, and accept the requests. I would recommend the solution to other users.

Using Azure Boards for tracking work items and bugs is clear and visually appealing. It's easy to add tasks. In our current configuration, every time I go inside the tasks and go back using the browser, it doesn't redirect me to Azure Boards, even if I am coming from there.

Since the solution is available as Software as a Service (SaaS), you won't need to do any setup, installation management, etc. It's very straightforward, and there is no particular study required. To a certain degree, the solution is configurable and can suit different use cases. It is working very well in terms of Git repositories. Microsoft Azure DevOps is also very accessible.

You can define tasks using Microsoft Azure DevOps and then reference them when you write a commit message or push code. You can open a previous commit in the browser from Visual Studio, and you can use DevOps to compare some files or to check commits done by Visual Studio. So, the solution is perfectly integrated.

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

As an architect, I use Azure DevOps for our projects, primarily focusing on setting up CI/CD workflows. We track tasks and maintain timesheets on Azure DevOps. I collaborate with project managers to define deployment pipelines and ensure smooth deployment processes. While Azure DevOps serves as our project management tool, my main role involves architecting deployment strategies and working closely with the project management team to implement them effectively.

Switching to Azure DevOps initially posed challenges, but as our team became familiar with it, we found it greatly improved our daily operations and productivity. Its streamlined processes made our development workflow more efficient.

What I like most about Azure DevOps is how easy it is to manage projects and control deployments. Once configured, team members can manage deployments if they have permissions. Additionally, the reports feature helps generate itemized invoices for the services provided to clients, which is valuable for billing purposes.

One potential enhancement in Azure DevOps could be integrating more customizable reporting features, particularly for Power BI integration, to provide better insights into project data.

I have been working with Azure DevOps for five years.

Azure DevOps is quite stable.

Azure DevOps is scalable and can be used in distributed environments and for different tenants.

Before Azure DevOps, we used various tools like Jira. We decided to switch to Azure DevOps to have all services unified in one place, simplifying management. The main advantage is having everything centralized.

The initial setup process for Azure DevOps was somewhat complex, requiring documentation and technical support. Migration from previous tools and configuring project guidelines were involved. The deployment strategy involved creating directories, and repositories, setting up environments, and assigning access rights, following a predefined plan. Initially, deployment took about three to four hours, but now, for regular deployments, it typically takes 30 minutes to an hour, depending on project stability. 

For the initial deployment of Azure DevOps, gathering information from various resources is essential, but typically, only one person is needed to handle deployment through the web interface. Maintenance involves regular tasks like backups and occasional updates, requiring minimal effort.

The pricing for Azure DevOps may be higher compared to other tools, but overall, I find it reasonable.

In my experience, integrating reporting and analytics into Azure DevOps enhances project visibility and decision-making processes. We can easily generate reports online to track project status and task progress. Additionally, I have integrated Azure DevOps with other tools like SQL Server, enabling us to gather data for generating Power BI reports.

The most beneficial integrations with Azure DevOps are integration with other project management tools for seamless collaboration and APIs for importing data into applications. Additionally, integrating with personal models allows for enhanced analytics and reporting on resource performance and other project metrics.

The source control management features of Azure DevOps, particularly Azure Repos, are highly effective. We can easily track and manage code changes, commit updates, and maintain a complete history of changes for our applications.

I would recommend Azure DevOps to others. Before choosing Azure DevOps, I would advise considering the need for better project management, consolidation of management tools, and streamlining deployment processes.

Overall, I would rate Azure DevOps as an eight out of ten.

We integrate the report pipelines with Azure pipelines, automating the creation of pipelines and initiating deployments automatically. Our process includes continuous integration, deployment, and branching strategies.

The tool's most efficient feature is the integration of its services in one place. It is an easy-to-use product that improves productivity. Microsoft Azure DevOps is also user-friendly. Its documentation is clear and can be found on Google. 

Microsoft Azure DevOps should create some training materials. 

I have been using the product for more than four years. 

Microsoft Azure DevOps is a stable solution. 

The product is scalable. 

I haven't contacted the technical support team yet. 

I rate Microsoft Azure DevOps a nine out of ten.