You host NuGet packages in Azure Artifacts and need to make a package available to anonymous users outside your organization while minimizing publication points. What should you do?

Creating a new public feed in Azure Artifacts is the most effective solution. Azure Artifacts allows you to configure feeds as public, making their packages accessible to anonymous users without requiring authentication. This minimizes publication points as the package remains within Azure Artifacts, just in a different feed configuration. Changing the feed URL of the package is not a valid action; the URL is determined by the feed itself. Promoting the package to a release view only changes its visibility within the existing feed for authenticated users and does not make it anonymous or public. Publishing the package to a public NuGet repository like nuget.org would make it publicly available, but it introduces an additional publication point outside of Azure Artifacts, which goes against the requirement of minimizing publication points.