Manage package feeds with Azure Artifacts
Learning objectives: create, scope, secure, and maintain feeds in Azure Artifacts, and manage packages, views, and retention across supported ecosystems.
Overview
Hands-on feed administration: creating feeds, choosing project vs. organization scope, setting permissions, managing views and retention, and publishing/consuming NuGet, npm, Maven, Python, Cargo, Go, and Universal packages.
Concepts introduced (link to term notes)
Units
- Create and configure a feed (scope, name, retention)
- Set feed permissions (Owners / Contributors / Readers)
- Publish packages (NuGet, npm, Maven, Python, Cargo, Go, Universal)
- Consume packages from a feed
- Use views for promotion (@Local, @Prerelease, @Release)
- Retention policies and cleaning up old versions
Key terms & commands
az artifacts feed · nuget push · npm publish · twine upload · views · retention · feed scope · contributors/readers
Hands-on
Create an org-scoped feed, publish a sample package with npm publish/nuget push, and consume it from another project with the appropriate service connection.
Exam focus
- Feeds are project- or org-scoped; org feeds are shareable across projects.
- Views are the supported promotion mechanism — e.g. promote a package to
@Release. - Package versions are immutable once published — manage via unlist/deprecate/delete + retention, never overwrite.
- Feed permissions control read vs. publish access per identity.
Related
Path MOC · intro-dependency-management · upstream-and-versioning · packaging-in-pipelines