You use Azure Artifacts to host NuGet packages that you create. You need tomake one of the packages available to anonymous users outside your…

To make a package available to anonymous users, you must host it in a public feed within a public Azure DevOps project. Public feeds allow anyone on the internet to view and restore packages without authentication. Creating a new, dedicated public feed for the package and then publishing it there is the correct procedure. This approach centralizes package management within your Azure DevOps organization and adheres to the principle of minimizing publication points, as the package is only published to this single, publicly accessible feed.

B. Publish the package to a public NuGet repository.

This would create a second publication point (the external repository in addition to your internal Azure Artifacts feed), violating the requirement to minimize publication points.

C. Promote the package to a release view.

Views (@release, @prerelease) are used to control the quality and visibility of package versions for consumers who already have access to the feed; they do not change the feed's fundamental access permissions from private to public.

D. Change the feed URL of the package.

A package does not have its own distinct feed URL. It is accessed via the URL of the feed that contains it. This is not a valid or possible action.

---

1. Microsoft Docs

"Share packages publicly": This document explicitly states

"Public feeds are project-scoped feeds that are stored in public projects. The main advantage of public feeds is that they can be shared with anyone on the internet... Users don't need to be a member of your organization or your project." This directly supports creating a new public feed (Option A) for anonymous access.

Source: Microsoft Corporation. (2023). Share packages publicly. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/devops/artifacts/public-feeds?view=azure-devops (Refer to the "Public feeds" and "Create a public feed" sections).

2. Microsoft Docs

"Feeds overview": This document clarifies the different scopes and visibility of feeds. It distinguishes between project-scoped and organization-scoped feeds and explains that only feeds within public projects can be made accessible to anonymous users.

Source: Microsoft Corporation. (2023). Feeds overview. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/devops/artifacts/feeds/feeds-overview?view=azure-devops (Refer to the "Feed visibility" section).

3. Microsoft Docs

"Views on Azure Artifacts feeds": This source details the purpose of feed views

confirming they are for managing package promotion through quality rings. It clarifies that views are subsets of a feed for existing consumers

not a mechanism for granting public access.

Source: Microsoft Corporation. (2023). Views on Azure Artifacts feeds. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/devops/artifacts/feeds/views?view=azure-devops (Refer to the "What are feed views?" section).