Share your packages publicly

Azure Artifacts provides an easy way to share packages to users outside your organization using public feeds. Packages that are stored in public feeds can be restored, installed, or consumed by anyone on the Internet.


Public feeds are project-scoped feeds that live inside a public project. You cannot convert an existing organization-scoped feed into a project-scoped feed or a public feed.

To learn more about feeds and their scopes, check out our feeds documentation.


Create a feed

  1. Go to Azure Artifacts in a public project:

    Go to Azure Artifacts

  2. Select + New public feed:

    New feed button

  3. In the dialog box:

    • Give the feed a name.
    • Select Create feed.

    New feed dialog box

Publish your packages

Now that you have a public feed, it's time to populate it with packages!


Public feeds cannot store Universal Packages.

If you're publishing using NuGet or Dotnet and you're using a credential provider to authenticate, public feeds require you to use the new credential provider instead of the older CredentialProvider.VSS.exe. You can learn more about the new credential provider, including install and setup instructions in the artifacts-credprovider GitHub repo.

From the command line

The following articles are quick guides that show you how to set up authentication and publish packages to your public feed from the command line. You can skip the "Create a feed" step in the following guides.

From Azure Pipelines

The following articles cover publishing packages to feeds from builds within Azure Pipelines:

Share your packages


Public feeds aren't intended to be a replacement for registries of record like or, and public feeds cannot have upstream sources.

To start sharing your packages, simply post or send your feed URL wherever you wish:

Sample feed URL:<org_name>/<project_name>/_packaging?_a=feed&feed=<feed_name>

As long as your project is public, anonymous and guest users will be greeted by the feed UX where they can see the available packages and learn how to consume them. Anonymous users will not have access to all features. E.g. Creating new feeds or accessing the recycle bin.

Feed UX from an anonymous or guest user with certain commands greyed out, except Connect to Feed

You can also share individual packages with badges which look like the example below.

Azure DevOps Services Package sharing badge for NuGet, npm, or Maven


Package badges can only be created and shared for released versions of packages; the criteria for what is considered a released version depends on the protocol type. Pre-released versions will not be displayed in badges, instead the badge will show the latest release version.