Azure Learning

azure-artifacts

Properties2
tagsaz-400, dependency, packages, azure-devops, artifacts
aliasesArtifacts, Azure DevOps Artifacts

2 min read

Azure Artifacts

What it is

Azure Artifacts is the package management service in Azure DevOps. It lets teams create, host, and share packages from public or private feeds — supporting NuGet, npm, Maven, Python (PyPI), Cargo, Go, and Universal packages. It’s the AZ-400 tool for implementing a centralized dependency-management strategy.

Why it exists

Without a private package host, internal libraries have to be copied around or fetched from public registries, leading to version drift, broken builds, and supply-chain risk. Azure Artifacts gives a governed, permission-controlled place to store packages and cache upstream dependencies, so builds are reproducible and consumption is auditable.

Key ideas

  • Feeds — the core container. A feed is project- or organization-scoped and holds packages plus their versions, views, and permissions.
  • Upstream sources — feeds can proxy public sources (nuget.org, npmjs.com, PyPI, Maven Central) and cache downloaded packages, so pipelines don’t hit the internet directly.
  • Permissions — granular controls: readers, contributors (publish), owners; configurable per feed or per identity.
  • Views — immutable, filtered views (e.g. @Release) for promoting packages to consumers.
  • Package types — NuGet, npm, Maven, Python, Cargo, Go, and Universal packages.
  • Retention & cleanup — retention policies and “unlist/delete” rules keep feeds from growing unbounded; versions are immutable once published.

How it fits

azure-artifacts - Microsoft diagram

Diagrams courtesy of Microsoft Learn / Azure docs: azure/devops/artifacts/start-using-azure-artifacts

Exam notes

  • Azure Artifacts supports NuGet, npm, Maven, Python, Cargo, Go, and Universal packages.
  • Feeds are scoped to a project or the whole organization; org feeds are shareable across projects.
  • Enabling upstream sources is a key governance feature — it caches public packages and keeps builds reproducible.
  • The CLI is integrated into pipelines via tasks (NuGet, npm, pip, Maven) and credentials are supplied by the Azure Artifacts service connection.

dependency-management · package-feed · upstream-sources · dependency-graph · pipeline-integration · build-artifact

📘 Source: Microsoft Learn — Azure Artifacts

Graph View

Backlinks