Design and implement a dependency management strategy
Learning objectives: plan a dependency-management strategy that centralizes packages, controls versions, and secures the supply chain — then implement it with Azure Artifacts.
Overview
The strategic layer of packaging: what packages your org consumes and produces, where they live, how they’re versioned and governed, and how they flow through CI/CD. This module sets up everything the rest of the path operationalizes.
Concepts introduced (link to term notes)
- dependency-management
- azure-artifacts
- package-feed
- upstream-sources
- semantic-versioning
- dependency-graph
Units
- Understand dependency-management goals (reproducibility, governance, security)
- Choose a package ecosystem strategy (NuGet/npm/Maven/Python/Cargo/Go/Universal)
- Decide feed topology: project vs. organization scope, upstreams
- Set up versioning and promotion conventions (SemVer, views)
- Plan supply-chain security (vulnerability scanning, dependency vulnerabilities)
Key terms & commands
feed · upstream · SemVer · project vs. org scope · views (@Release) · dependency graph · lock files · retention
Hands-on
Map your app’s dependency graph, choose a feed scope, and enable upstream sources in a new Azure Artifacts feed.
Exam focus
- Azure Artifacts is the canonical answer for centralized package management.
- Org-scoped feeds are shareable across projects; project feeds are isolated.
- Feed package versions are immutable — plan versioning and retention up front.
- Lock files + upstreams + immutable versions = reproducible builds.
Related
Path MOC · azure-artifacts-feeds · upstream-and-versioning · packaging-in-pipelines