Azure Artifacts
Ranked #12 of 13 for artifact repository managers: Package feeds in Azure DevOps, billed per GiB beyond 2 GiB.
Commercial relationships can affect which products appear and how prominently. The Azure Artifacts link is marked as every vendor link is, see disclosure.
Visit Azure Artifacts See it in the artifact repository managers ranking
Azure Artifacts at a glance
| Headquarters | United States |
|---|---|
| Free plan | No free tier on record |
| Best for | Teams on Azure DevOps wanting packages beside pipelines with storage-only billing |
| Pricing model | Per-GiB monthly storage billing with a small allowance per organisation; no per-user price for Artifacts |
| API | The vendor material we read does not say |
| Deployment | No deployment model stated for Azure Artifacts |
What is Azure Artifacts?
Azure Artifacts is the package management service inside Azure DevOps, run by Microsoft Corporation, which lists One Microsoft Way, Redmond, Washington as its address. It hosts NuGet, npm, Python, Maven, Cargo and Universal Packages in feeds, and a feed can optionally bring in packages from upstream sources such as nuget.org, npmjs.com and Maven Central.
Each organisation gets 2 GiB of free storage, which Microsoft describes as a tier to evaluate the service, and beyond that the pricing page lists storage at 2 US dollars per GiB, falling in steps. There is no per-user price for Artifacts. That model suits teams already on Azure DevOps, and it has a sharp edge: once the free 2 GiB is full, an organisation cannot publish new artifacts until it deletes packages or sets up billing.
Azure Artifacts key features
- Feeds with visibility and scope. A feed has a name, a visibility setting and a scope, and acts as the container for the packages a team publishes and consumes.
- Upstream sources. An optional checkbox lets a feed pull packages from public sources such as nuget.org, npmjs.com and Maven Central.
- Six package types. NuGet, npm, Python, Maven, Cargo and Universal Packages are listed, with Gradle covered as a Maven publishing route.
- Universal Packages. Universal Packages allow files up to 4 TiB, though the feature table marks them unavailable on Azure DevOps Server 2022.
- Version and size limits. The storage page lists 500 MiB per file for NuGet, npm, Maven, Python and Cargo, and 5,000 versions per package ID.
- Storage tracking. Usage can be tracked at project and organisation level with a breakdown by artifact type, and the organisation can raise its storage limit.
- Recycle bin. Deleted packages sit in a recycle bin for 30 days before automatic removal, though they still count toward storage meanwhile.
Who Azure Artifacts suits
- Azure DevOps pipeline teams. Teams that build in Azure Pipelines can publish NuGet or npm packages to a feed in the same organisation and project.
- .NET and Java shops. Groups releasing NuGet or Maven libraries internally can share them across projects while proxying public packages through upstream sources.
- Small teams evaluating. The 2 GiB free allowance per organisation gives a small group room to test feeds before any billing is set up.
Getting started with Azure Artifacts
The Learn article walks through creating a feed: choose a name, a visibility setting and a scope, and tick the upstream sources box if packages from nuget.org, npmjs.com or Maven Central should be available. Publishing guides are listed for dotnet, NuGet.exe, Maven and Gradle.
Each organisation starts with 2 GiB of free storage, and the article says this is meant for evaluation. Once that is used, the organisation cannot publish until packages are deleted or billing is set up with the pay-for-what-you-use usage limit selected. The pages we read do not describe a migration path from another registry.
Where Azure Artifacts wins and where it does not
- Azure Artifacts, from Microsoft, provides feeds for NuGet, npm, Python, Maven, Cargo and Universal Packages inside Azure DevOps.
- Catalogue tag: Azure DevOps feeds.
- Storage-metered is among the traits we single out for it.
- Catalogue tag: Upstream sources.
- Where it fits: Teams on Azure DevOps wanting packages beside pipelines with storage-only billing.
- Recycled packages count toward storage for 30 days and upstream-saved packages count toward billed storage, so the bill exceeds what developers think they stored.
- Not for: Teams needing Docker images or on-premise Universal Packages.
- Once an organisation reaches 2 GiB it cannot publish until it deletes packages or sets up billing, which can halt a release.
Our verdict on Azure Artifacts
Azure Artifacts, from Microsoft, provides feeds for NuGet, npm, Python, Maven, Cargo and Universal Packages inside Azure DevOps. Each organisation gets 2 GiB of free storage, then pays per GiB in tiers.
When the allowance is reached publishing stops until packages are deleted or billing is set up. Upstream sources pull in nuget.org, npmjs.com and Maven Central. Universal Packages are listed as unavailable on Azure DevOps Server 2022.
Azure Artifacts is entry #12 of 13 in the artifact repository managers list: it follows GitHub Packages and comes before AWS CodeArtifact. After the challenger places, Azure Artifacts is one of the established names, ranked in order and without a score.
By headquarters, 4 of the 13 are established in North America, as Azure Artifacts is in the United States.
Azure Artifacts pros and cons in practice
- 2 GiB of storage is included per organisation.
- No per-user price applies to Artifacts.
- Upstream sources bring public packages into the same feed.
- Storage can be tracked by project, organisation and artifact type.
- Reaching 2 GiB blocks new publishing until packages are deleted or billing is set up.
- Recycle bin and upstream-saved packages still count toward billed storage.
- Universal Packages are marked unavailable on Azure DevOps Server 2022.
- Docker is not among the listed package types in the Learn article.
Azure Artifacts pricing
Charging model: Per-GiB monthly storage billing with a small allowance per organisation; no per-user price for Artifacts.
Each organisation includes 2 GiB of free storage. Beyond that the pricing page lists storage starting at 2 US dollars per GiB, with tiers of 2, 1, 0.5 and 0.25 US dollars per extra GiB depending on total usage. Prices are calculated in US dollars, storage is charged per GiB per month, and there is no per-user price for Artifacts. Packages in the recycle bin still count toward storage for 30 days, and packages saved from upstream sources also count toward billed storage. Without billing, reaching the 2 GiB allowance blocks new publishing.
We took this from azure.microsoft.com, the vendor’s own site, when we reviewed Best Artifact Repository Managers in 2026; that review is dated 15 November 2026.
Azure Artifacts: data and security
Microsoft Corporation lists One Microsoft Way, Redmond, Washington, USA as its address. For individuals in the EEA, the UK and Switzerland, the privacy statement names Microsoft Ireland Operations Limited as controller.
Feeds carry visibility and scope settings, and storage is tracked by project and organisation. The pages we read do not list certifications or per-feed data location choices for Azure Artifacts, so those should be checked with Microsoft before a regulated deployment.
What Azure Artifacts connects to
Integrations the vendor names (9):
- Azure DevOps
- Azure Pipelines
- NuGet
- npm
- Maven
- Gradle
- Python
- Cargo
- nuget.org
Azure Artifacts in numbers and labels
| Product | Azure Artifacts |
|---|---|
| Vendor website | azure.microsoft.com |
| Head-to-head pages | No comparison written |
| Rank there | #12 of 13 |
| Alternatives page | Not part of the alternatives set |
| Price visibility | Model recorded, no figure |
| Primary guide | Best Artifact Repository Managers in 2026 |
| Catalogue tags | Storage-metered, Upstream sources, Azure DevOps feeds |
| What we do not hold | funding rounds and staff numbers |
| Headquarters | United States (North America) |
Close alternatives to Azure Artifacts
3 products in this guide come closest to Azure Artifacts on tags, pricing and region.
- Bytesafe (#7 of 13): Not for: teams looking for a first place to store internal packages. Dependency firewall that screens package requests before they install. (Sweden)
- GitHub Packages (#11 of 13): Aimed at: Teams whose code and CI already live in GitHub.
- AWS CodeArtifact (#13 of 13): Not for: teams that publish public packages or work outside AWS. Managed package repositories on AWS, billed by storage, requests and transfer. (United States)
Where else Azure Artifacts is ranked
| Guide | Position |
|---|---|
| Best Artifact Repository Managers in 2026 | #12 of 13 |
Questions about Azure Artifacts
9 answersWhere is Azure Artifacts based?
The vendor is based in the United States (North America). Check hosting separately: the data centre need not be in that country.
Who should choose Azure Artifacts?
Teams on Azure DevOps wanting packages beside pipelines with storage-only billing. Think twice if you are in this group: teams needing Docker images or on-premise Universal Packages.
Which tools compete with Azure Artifacts?
Start with Bytesafe, GitHub Packages and AWS CodeArtifact. All of them are reviewed in the same ranking.
Where does Azure Artifacts stand among artifact repository managers?
The artifact repository managers ranking has Azure Artifacts at position 12 out of 13.
Is Azure Artifacts free, or what does it charge?
Our catalogue records Azure Artifacts’s pricing as: Per-GiB monthly storage billing with a small allowance per organisation; no per-user price for Artifacts. On free access, nothing is free to use, as far as we recorded.
How much free storage is there?
2 GiB per organisation, described by Microsoft as a tier to evaluate the service.
What does extra storage cost?
Starting at 2 US dollars per GiB, with tiers of 2, 1, 0.5 and 0.25 US dollars depending on total usage.
Is there a per-user charge?
The pricing page states there is no per-user price for Artifacts.
What is the per-file limit?
500 MiB for NuGet, npm, Maven, Python and Cargo packages, and 4 TiB for Universal Packages.
Azure Artifacts: sources
Read from the vendor’s own pages on 14 November 2026.
- learn.microsoft.com/en-us/azure/devops/artifacts/start-using-azure-artifacts?view=azure-devops: Package types, feeds, upstream sources and free allowance
- azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services: Storage prices and absence of per-user price
- learn.microsoft.com/en-us/azure/devops/artifacts/artifact-storage?view=azure-devops: File limits, versions, recycle bin and publishing block
- microsoft.com/en-us/privacy/privacystatement: Address and EEA controller
How we rank
We rank on what separates products after the demo: time to useful, the real price, the exit and who the product is for. That puts Azure Artifacts at #12 of 13. The editorial process sets out how facts are gathered and how commercial links are handled.