Try our new research platform with insights from 80,000+ expert users

Microsoft Azure DevOps vs UrbanCode Deploy comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Microsoft Azure DevOps
Ranking in Release Automation
1st
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
132
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Enterprise Agile Planning Tools (1st)
UrbanCode Deploy
Ranking in Release Automation
10th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
27
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Release Automation category, the mindshare of Microsoft Azure DevOps is 36.4%, down from 38.7% compared to the previous year. The mindshare of UrbanCode Deploy is 5.0%, up from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation
 

Featured Reviews

Ivan Angelov - PeerSpot reviewer
Facilitates agile transformation with potential for enhanced intuitiveness
What I liked about the solution is that it offers numerous features that are not available by default unless you are agile. Transitioning from the traditional Waterfall model to an agile methodology was challenging for us. Until 2020, our team predominantly worked with the Waterfall approach, using local tools like ServiceNow. We had a few team members who were familiar with Agile ISO, but none had experience with Azure. Therefore, we pursued Azure certification at the AZ-900 level. Our company organized a training session with a certified Azure expert, which was extremely beneficial for adopting best practices during the initial three months. This preparation helped us get accustomed to the new tool, as transitioning to a new system invariably requires time. Managing a pipeline of deliverables became significantly easier with this solution. We utilized it for stories and integrated change management with Azure DevOps. Eventually, everything related to the environment was organized there, enabling us to follow up and track progress with our technical engineers on an hourly, daily, or weekly basis. Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap.
it_user587571 - PeerSpot reviewer
It offers OOTB plugins for middleware.
By standardizing the automated deployment application process, reducing the amount of errors due to manual steps and by providing visibility into the release cycles of various teams/applications, we've improved our global efficiency by at least 25% and still counting, since we've only used the product for a short period of time.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Microsoft Azure DevOps integrates well with other components, such as Synapse, which is a data warehouse tool of Azure. It is a framework platform for BI and integrated with other tools, such as Power BI."
"We use all the DevOps features and services, like reports, Boards, Pipelines, Artifactory, etc. The interface is interactive and intuitive. The platform visuals and workflow are straightforward in Azure DevOps."
"Most of the features are very valuable for us, especially the source code control and task management."
"This platform provides a large span of tools and technologies."
"Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team."
"You get a complete solution with Azure DevOps. You can do everything in one place, starting from requirement gathering until you release the product. It is a reliable, scalable, and handy product."
"There are great automation tools."
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
"The solution handles complex deployments very efficiently."
"Stable solution that's good for automating the CI/CD pipeline: from development to production."
"The stability is good. I haven't experienced any issues."
"It is very easy to make a software release. It used to take us at least a couple of hours to make a release, now we went to production with a new one last night. This new release took me five minutes."
"The most valuable feature is the snapshot functionality, which allows us to access previous versions of the artifacts."
"The most valuable functionality is the ability to define the deployment process, schedule the deployment and automatically execute the deployments to different environments."
 

Cons

"Definitely, there should be more integration between GitHub and Azure DevOps."
"The tool has a logical link between epic feature, user story, and task, but when you try to generate a report to show the delivery progress against a feature, it is not easy. To see the percentage completion for a feature or progress of any delivery, it is not easy to draw a report."
"They have to add more features such as schedules and more flexibility in the platform."
"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."
"Not all companies use the same methodology which could limit the use of this solution."
"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."
"The solution could be made faster because it can be a little unnerving to browse through too many pages and press too many buttons."
"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."
"The scalability of this application needs improvement. Changes and variations in the application become bottlenecks as they need to be more seamless and comfortable."
"I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline."
"I would like to see more reporting for container architecture."
"The interface allows access in a number of ways but that can be confusing."
"The technical support of the solution could definitely be improved as PMRs take long to resolve."
"I certainly would like to have a better way to pass information between deployment steps using UrbanCode Deploy because that's really difficult to do."
 

Pricing and Cost Advice

"We purchase the solution on an annual basis."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"The majority of the components are reasonably priced."
"The licensing structure is good."
"It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware."
"I don't have a problem with the pricing."
"It is a subscription model and I only pay for what I use."
"Considering COVID-19, the price is too high."
"The licensing fees for this solution are based on the number of servers that are being deployed and the number of agents that you have."
"The cost of the solution is high but it offers great ROI."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
847,862 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Computer Software Company
13%
Financial Services Firm
12%
Government
9%
Educational Organization
60%
Financial Services Firm
19%
Insurance Company
6%
Computer Software Company
3%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
Ask a question
Earn 20 points
 

Also Known As

Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
uDeploy
 

Overview

 

Sample Customers

Alaska Airlines, Iberia Airlines, Columbia, Skype
As policy, IBM does not release customer names on non-IBM web sites.  However, public DevOps and UrbanCode Deploy case studies can be found here. IBM's UrbanCode Deploy customers span Small-Medium Businesses to Fortune 500 companies across all industries worldwide.
Find out what your peers are saying about Microsoft Azure DevOps vs. UrbanCode Deploy and other solutions. Updated: April 2025.
847,862 professionals have used our research since 2012.