What are feeds?

Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 | TFS 2017

Artifacts Feeds are organizational constructs that allow you to store, manage, and group your packages and control who to share it with. Feeds are not package-type dependent. You can store all the following package types in a single feed: npm, NuGet, Maven, Python, and Universal packages.

Project-scoped vs Organization-scoped feeds

Previously, all feeds were scoped to an organization, they could be viewed and accessed in the Azure Artifacts hub from any project within an organization. With the introduction of public feeds, we also introduced project-scoped feeds. This type of feed can only be accessed from within the hosting project.

Only project-scoped feeds can be made public. You can learn more about public feeds later in this article. See Feeds visibility to understand the differences between project-scoped and organization-scoped feeds.


To access a feed in a different organization, a user must be given access to the project hosting that feed.

Public feeds

Public feeds are used to share your packages publicly with anyone on the Internet. Users won't have to be a member of your organization or your enterprise. They can access the packages even if they don't have an Azure DevOps account.

Public feeds are project-scoped feeds and it will inherit the visibility settings of the hosting project.

There some important things to note regarding public feeds:

  • Public feeds can only be created inside of public projects.
  • Public feeds aren't intended as a replacement for existing package management platforms (NuGet.org, npmjs.com, etc.).
  • Public feeds cannot have upstream sources.
  • Public users cannot currently download universal packages. All other package types are supported for public access.

Create a feed

With Azure Artifacts, you can create two types of feeds: project-scoped and organization-scoped feeds. All public feeds are project-scoped and they inherit the hosting project's visibility settings. By default, any feed that's created by using the web UI is a project-scoped feed, as follows.

  1. From within your project, navigate to Azure Artifacts.

    Go to Azure Artifacts

  2. Select Create Feed.

    New feed button

  3. Give your feed a Name and choose its visibility, upstream sources, and scope settings.

    New feed dialog box

  4. Select Create when you are done.

Azure Artifacts is installed by default for TFS 2017 customers. You must upgrade to TFS 2017 in order to use Azure Artifacts. If this is the first time using your feed, you might be asked to assign a license

  1. Go to Build & Release and select Packages.

    Go to Azure Artifacts TFS

  2. Select + New feed.

    New feed button TFS

  3. Give your feed a Name, a Description, and set up who can read, who can contribute and if you want to Include external packages.

    New feed dialog box TFS

  4. Select Create when you are done.

Restoring a deleted feed

If you accidentally delete a feed, Azure Artifacts provides a 30 days window to recover your feed to its original state. After the 30 days, the feed will be deleted permanently. During the recovery window, the feed name will be reserved, package download unavailable, and write access suspended for that feed.

You can view the feeds pending permanent deletion in your Feeds dropdown list under the Deleted Feeds tab.

  1. Under Deleted feeds select your feed.

    Deleted feeds dropdown

  2. Select Feed Settings.

    Feed settings button

  3. Select Restore Feed.

    Restore feed

Permanently deleting a feed

A feed pending deletion will still use storage space. If you want to permanently delete your feed before the 30 days period is up, you can do this from the deleted feeds settings.

  1. Under Deleted feeds select your feed.

    Deleted feeds list

  2. Select Permanently delete and confirm the deletion

    Permanently delete feed

Once the feed is permanently deleted, users won't be able to view or restore its packages. The feed name will be available for reuse 15 minutes after the deletion.