| title | Set up upstream sources for your feed |
|---|---|
| description | Learn how to set up external feeds and public registries as upstream sources for your Azure Artifacts feed. |
| ms.service | azure-devops-artifacts |
| ms.topic | how-to |
| ms.date | 02/06/2026 |
| monikerRange | <=azure-devops |
[!INCLUDE version-lt-eq-azure-devops]
With Azure Artifacts upstream sources, you can simplify package management by using a single feed for both the packages you publish and those you consume from external feeds and public registries like npmjs.com and NuGet.org. When upstream sources are enabled, Azure Artifacts automatically saves a copy of any package installed to your feed. However, you must be a collaborator or higher to install packages from upstream sources.
Note
Maven snapshots are not supported in upstream sources.
| Product | Requirements |
|---|---|
| Azure DevOps | - An Azure DevOps organization. - An Azure DevOps project. - An Azure Artifacts feed. |
If you don't have a feed yet, follow these steps to create a new feed and enable upstream sources:
-
Sign in to Azure DevOps, then navigate to your project.
-
Select Artifacts, then select Create Feed.
-
Provide a Name for your feed and choose its Visibility and Scope settings. Make sure to select the Include packages from common public sources checkbox to enable upstream sources.
-
Select Create when you're done.
:::image type="content" source="../media/new-feed-with-enabled-upstreams.png" alt-text="A screenshot showing how to create a new feed with upstream sources enabled in Azure Artifacts.":::
If you've created a feed without enabling upstream sources, you can enable it later to consume packages from common public sources. Follow these steps to enable upstream sources for an existing feed:
-
Sign in to Azure DevOps, then navigate to your project.
-
Select the gear icon button
to open Feed settings. -
Select Upstream sources > Add Upstream.
-
Select Public source, choose a Public source from the dropdown, then select Add.
-
Select Save in the top-right corner to apply the changes.
Note
You must be a feed owner or feed administrator to add or remove upstream sources.
Follow these steps to add a feed from the same organization as an upstream source:
-
Sign in to Azure DevOps, then navigate to your project.
-
Select the gear icon button
to navigate to Feed settings. -
Select Upstream sources, then select Add Upstream.
-
Select Azure Artifacts feed in this organization.
-
From the dropdown menu, select the feed you want to add as an upstream source. Select the desired View, then choose the Package type(s) to include. Optionally, you can also modify the upstream source name.
-
Select Add when you're done.
:::image type="content" source="../media/add-upstream-same-org.png" alt-text="A screenshot displaying how to add a feed from your organization as an upstream source.":::
Follow these steps to add a feed from a different organization as an upstream source:
-
Sign in to Azure DevOps, then navigate to your project.
-
Select the gear icon button
to access Feed settings. -
Select Upstream sources, then select Add Upstream.
-
Select Azure Artifacts feed in another organization.
-
Enter your Azure Artifacts feed locator using one of the following formats:
-
Organization scoped feed:
azure-feed://ORGANIZATION_NAME/FEED_NAME@VIEW -
Project scoped feed:
azure-feed://ORGANIZATION_NAME/PROJECT_NAME/FEED_NAME@VIEW
-
-
Select the Package type(s) you want to use and provide a name for your upstream source.
-
Select Add when you're done.
:::image type="content" source="../media/add-upstream-diff-org.png" alt-text="A screenshot displaying how to add a feed from a different organization as an upstream source.":::
Important
To add a feed from a different organization as an upstream source, the target feed owner must share the target view with All feeds and people in organizations associated with my Microsoft Entra tenant by navigating to Feed Settings > Views > Select the ellipsis button for the specified view > Edit.
Note
To install packages from upstream sources, you must be a Feed and Upstream Reader (Collaborator), Feed Publisher (Contributor), or a Feed Owner. The first time a package is installed from an upstream source, a copy is automatically saved to the feed. Any packages already saved to the feed can then be used by Feed Readers.
A: Packages from upstream sources become available in the feed soon after they're published, but they aren’t visible to readers until they’re saved to the feed.
A package is saved when a user with Feed and Upstream Reader (Collaborator) or higher permissions installs it. Azure Artifacts then automatically saves a copy of the package to the feed, making it permanently available to all readers and visible in the web UI.
A: If the feed is in a different organization, make sure that the target feed owner has shared a view with All feeds and people in organizations associated with my Microsoft Entra tenant. See Add a feed in a different organization as an upstream source for more details.
A: Feed views let you share a subset of package versions that have been tested and validated, excluding those still in development or not meeting quality criteria. See What are feed views for more details.
A: No. Feed Reader can only download packages that are already saved to the feed. Packages are saved when a Feed and Upstream Reader (Collaborator), Feed Publisher (Contributor), or Feed Owner installs them from an upstream source.
A: The package becomes unavailable for download, and the version number is permanently reserved. That version will no longer sync from upstream, but earlier and later versions remain unaffected.
A: A warning message is added to the package metadata. This warning appears whenever the package is viewed or installed from the feed.