Azure Artifacts vs. Azure DevOps Services

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure Artifacts
Score 9.8 out of 10
N/A
Microsoft's Azure Artifacts is a software package management solution.N/A
Azure DevOps Services
Score 7.8 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Azure ArtifactsAzure DevOps Services
Editions & Modules
No answers on this topic
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
Azure ArtifactsAzure DevOps Services
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Azure ArtifactsAzure DevOps Services
Best Alternatives
Azure ArtifactsAzure DevOps Services
Small Businesses
Git
Git
Score 10.0 out of 10
GitHub
GitHub
Score 9.0 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
GitHub
GitHub
Score 9.0 out of 10
Enterprises
Git
Git
Score 10.0 out of 10
Perforce P4
Perforce P4
Score 7.6 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure ArtifactsAzure DevOps Services
Likelihood to Recommend
10.0
(0 ratings)
8.1
(0 ratings)
Likelihood to Renew
-
(0 ratings)
10.0
(0 ratings)
Usability
-
(0 ratings)
6.6
(0 ratings)
Support Rating
-
(0 ratings)
8.1
(0 ratings)
Implementation Rating
-
(0 ratings)
10.0
(0 ratings)
User Testimonials
Azure ArtifactsAzure DevOps Services
Likelihood to Recommend
Share codes and packages across the whole organization. We have developers most of the time work from home or overseas like in India. We can test and deploy the package when they deploy the new changes into the Azure Artifacts. Azure Artifact can promote our package to the correct system like DEV, UAT, or Production. It also provides retention policies to automatically clean up expired packages.
Read full review
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
Read full review
Pros
  • Security feature on share code efficiently.
  • The built in CI/CD for the software pipeline.
  • Support for most famous build tool like maven and npm.
Read full review
  • Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
  • Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
  • Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Read full review
Cons
  • Native artifact format support like docker image
  • Support for APL
  • Support IAM permission
Read full review
  • Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
  • Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
  • Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
  • With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
  • If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
Read full review
Likelihood to Renew
No answers on this topic
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Read full review
Usability
No answers on this topic
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Read full review
Support Rating
No answers on this topic
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Read full review
Implementation Rating
No answers on this topic
Was not part of the process.
Read full review
Alternatives Considered
Azure Artifact is based on GitHub which is the best artifact at all times. Helm is open source and we may have security concerns. Crucible is a good tool but does not of a lot of support. I prefer that Azure Artifact is a solid product and with a good gene from the GitHub codebase.
Read full review
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.
Read full review
Return on Investment
  • The artifact provide best practice to our software development.
  • Provide a standard way to release the software.
  • The package is immutability which means no one can update it after release.
Read full review
  • Increased dev team efficiency through more streamlined development processes and task automation.
  • Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
  • Better collaboration between the dev team, business analysts, and agile project managers.
Read full review
ScreenShots