Azure Artifacts overview
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018
Azure Artifacts enables developers to share their code efficiently and manage all their packages from one place. With Azure Artifacts, developers can publish packages to their feeds and share it within the same team, across organizations, and even publicly. Developers can also consume packages from different feeds and public registries such as NuGet.org or npmjs.com. Azure Artifacts supports multiple package types such as NuGet, npm, Python, Maven, and Universal Packages.
- Allow domain URLs and IP addresses if your organization is using a firewall or a proxy server.
- Set up billing if you plan to use more than the free 2-GiB storage.
Install Azure Artifacts
Azure Artifacts comes pre-installed in TFS 2018. If the extension is removed, you can install it from the Visual Studio Marketplace.
Assign licenses in TFS
From any collection in TFS, hover over the settings menu and select the Users page. Then, select Azure Artifacts.
Select Assign, enter the user to assign licenses, and then select Ok
- Users with Visual Studio Enterprise subscriptions get Azure Artifacts automatically.
- Ensure that your Visual Studio Enterprise subscribers are assigned VS Enterprise Access level.
Get started with Azure Artifacts
With Azure Artifacts, you can publish and consume different types of packages. Select your package type to get started:
|Package type||Azure DevOps Services||Azure DevOps Server||TFS-2018|
|Python packages||Server 2019 Update 1 and newer, Server 2020, and Server 2022.|
Artifacts free tier and upgrade
Azure Artifacts is free for every organization up to 2 GiB of storage. Once you reach the maximum storage limit, you can no longer upload new artifacts and need to delete some of your existing artifacts or set up billing to increase your storage limit. See the Pricing Calculator to learn more about Azure DevOps billing.
Organization billing settings
Follow the steps outlined below to view your billing settings for your organization:
Sign in to your Azure DevOps organization.
Select Organization settings.
View your Artifacts tier and usage limit.
View Artifacts storage consumption
Q: Which artifacts count toward my total billed storage?
A: You get billed for all package types (npm, NuGet, Python, Maven, and Universal Packages) including packages stored from upstream sources. However, you don't get billed for Pipeline Artifacts, and Pipeline Caching.
Packages in the recycle bin still count as part of your storage consumption. Those packages get deleted permanently after 30 days. If you want to delete them sooner, navigate to your recycle bin and delete them manually.
Q: I'm storing Artifacts but my storage consumption shows 0 GiB?
A: 1 GiB is currently our lowest granularity, so you most likely haven't reached 1 GiB yet.
Q: How can I control how many days Artifacts are kept?
A: You can set up the retention policies to delete packages automatically. For more information, see How to use retention policies to delete old packages.
Q: How can I delete specific packages?
A: See Delete and recover packages for details.
Q: How long does it take for deleted Artifacts to reflect in the amount of billed storage?
A: Deletion of artifacts doesn't register immediately. Storage consumption should be updated within 24 hours, but in some cases it may take up to 48 hours. If you're blocked from uploading Artifacts, as a workaround you can temporarily increase your usage level, then reduce the level back once the storage metrics are updated.
The used column on the Billing page of your Organization gets updated once a day. When you delete an Artifact, it may not reflect immediately on your billing page. The Artifact Storage page however gets updated more frequently, so you may see a small discrepancy between the two pages.
Q: What happens if I remove my Azure Subscription from my Azure DevOps organization?
A: When you remove your Azure Subscription from your Azure DevOps organization, you only have access to the free tier. If you used more than 2 GiB of storage, you can only read packages. You can't publish new packages until you lower your storage below 2 GiB. Or, you can reconnect an Azure subscription to your organization and set up billing to increase your storage tier.