Question

Your team maintains an Azure Artifacts feed named 'Contoso-NuGet' for internal .NET packages. Developers currently restore both your internal packages and public packages from nuget.org, but you want a single feed URL in the NuGet.config that resolves internal packages while also caching and vetting public packages so the same versions are always available even if nuget.org is unavailable. You also need to promote only tested internal package versions to a 'Release' view consumed by production build pipelines. Which combination of Azure Artifacts capabilities should you configure?

Accepted Answer

Enable nuget.org as an upstream source on the feed, and publish tested packages to a 'Release' view via promotion, pointing production pipelines at the '@Release' view URL.

Answer

Create a separate feed for public packages and reference both feed URLs in NuGet.config, using retention policies to keep only release-quality versions.

Answer

Set the feed's default view to '@Local' and disable upstream sources, then manually mirror required nuget.org packages by uploading .nupkg files.

Answer

Enable nuget.org as an upstream source and use branch policies to gate which package versions appear in the '@Prerelease' view for production pipelines.