Study guide
5.1 Selecting Package Tools: Azure Artifacts vs. GitHub Packages
Microsoft Certified: Azure DevOps Engineer Expert AZ-400
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Flow of Work, Traceability & Work Tracking
1.1 Flow of Work, GitHub Flow & Feedback Cycles 1.2 Work Tracking with Azure Boards & GitHub Projects 1.3 End-to-End DevOps Traceability & Quality Tracking
2 Chapter 2: DevOps Metrics, Dashboards & Team Collaboration
2.1 DORA Metrics, Flow Metrics & Dashboard Design 2.2 Lifecycle Metrics Across the Six DevOps Phases 2.3 Work Item Queries, WIQL Charts & Analytics 2.4 Project Documentation: Wikis, Mermaid Diagrams & Release Notes 2.5 Webhooks, Service Hooks & Microsoft Teams ChatOps
3 Chapter 3: Git Branching Strategies & Pull Request Workflows
3.1 Git Branching Models & Strategy Design 3.2 Pull Request Workflows & Merge Strategies 3.3 Branch Policies, Quality Gates & Compliance Restrictions
4 Chapter 4: Repository Management, Optimization & Git Data Operations
4.1 Git LFS Architecture & .gitattributes Tracking 4.2 LFS History Migration, git-fat & File Locking 4.3 Git Repository Scaling, Scalar & Monorepo Governance 4.4 Repository Permissions & Git Tag Governance 4.5 Git Data Recovery & Sensitive-Data Scrubbing
5 Chapter 5: Package Management & Dependency Versioning
5.1 Selecting Package Tools: Azure Artifacts vs. GitHub Packages 5.2 Feed Scoping, Upstream Sources & Pipeline Authentication 5.3 Package Views, Immutability & Quality Promotion 5.4 Dependency Versioning: SemVer, CalVer & Automated Versioning 5.5 Pipeline Artifact Versioning & Artifact Storage Strategy
6 Chapter 6: Pipeline Infrastructure, Agents & Integration
6.1 Selecting a CI/CD Solution: Azure Pipelines vs. GitHub Actions 6.2 GitHub-Azure Pipelines Integration & Hybrid Migration 6.3 Hosted vs. Self-Hosted Agents & Runners 6.4 VMSS Elastic Pools, Container Jobs & Agent Governance 6.5 Pipeline Triggers, Filters & Concurrency Management
7 Chapter 7: YAML Pipeline Architecture & Reusable Elements
7.1 YAML Pipeline Anatomy: Stages, Jobs, Steps & Workspaces 7.2 Job Execution Order: DAG Dependencies, Parallelism & Conditions 7.3 Reusable Elements: Templates, Parameters & Variables 7.4 Variable Groups, Secret Variables & Key Vault Linking 7.5 YAML Environments, Checks & Deployment Approvals
8 Chapter 8: Testing Strategy, Quality Gates & Code Coverage
8.1 Test Strategy Design: Local, Unit & Integration Testing 8.2 Load, Stress & Performance Testing in Pipelines 8.3 Test Execution Tasks, Agents & Results Integration 8.4 Code Coverage Analysis & SonarQube Integration 8.5 Quality Gates, Release Gates & Governance Checks
9 Chapter 9: Modern Deployment Strategies & Zero-Downtime Delivery
9.1 Progressive Delivery: Blue-Green, Canary & Ring Deployments 9.2 Minimizing Downtime: Deployment Slots & Rolling Updates 9.3 Feature Flags with Azure App Configuration & Feature Manager 9.4 Designing the High-Priority Hotfix Path 9.5 Ordered Dependency Deployments, Resiliency & Rollback
10 Chapter 10: Artifact Deployment & Database DevOps
10.1 Containerized Application Delivery: ACR, AKS & Container Apps 10.2 Binary, Web App, Function & Scripted Deployments 10.3 Database DevOps: State-Based & Migration-Based Strategies
11 Chapter 11: Infrastructure as Code (IaC) & Azure Deployment Environments
11.1 Infrastructure as Code Strategy: Bicep, ARM & Terraform 11.2 Desired State Configuration & Azure Machine Configuration 11.3 Azure Deployment Environments (ADE) & Developer Self-Service
12 Chapter 12: Pipeline Maintenance, Health & Modernization
12.1 Pipeline Health, Flaky Tests & Reliability Engineering 12.2 Pipeline Optimization: Caching, Slicing & Concurrency 12.3 Artifact & Build Retention Governance 12.4 Modernizing CI/CD: Classic to YAML Migration
13 Chapter 13: Authentication, Authorization & Identity Governance
13.1 Microsoft Entra Service Principals & Managed Identities 13.2 Service Connections, Workload Identity & Personal Access Tokens 13.3 Azure DevOps Projects, Teams & Permission Evaluation 13.4 Access Levels, GitHub Roles & Outside Collaborators
14 Chapter 14: Secrets Management, Sensitive Data & DevSecOps Scanning
14.1 Azure Key Vault, Secret Variables & Secretless CI/CD 14.2 Security Scanning Strategy, GHAS & Secret Scanning 14.3 CodeQL SAST in Pipelines and Containers 14.4 Software Supply Chain, Container Scanning & Cloud Defender
15 Chapter 15: Telemetry Collection, Azure Monitor & Alerting
15.1 Azure Monitor Architecture, AMA & Data Collection Rules 15.2 Application Insights & Specialized Azure Monitor Insights 15.3 Alerting Rules, Action Groups & GitHub Repository Insights
16 Chapter 16: Telemetry Analysis, Distributed Tracing & SRE Practices
16.1 Distributed Tracing, Application Map & Exception Triage 16.2 KQL Log Analytics, SRE Observability & Error Budgets
5.1 Selecting Package Tools: Azure Artifacts vs. GitHub Packages
Key Takeaways Explain This Topic AI
Azure Artifacts supports NuGet, npm, Maven, Python, Cargo and Universal Packages, but never hosts Docker or OCI container images.
GitHub Packages covers npm, NuGet, Maven, RubyGems and the GitHub Container Registry, authenticating with the repository-scoped GITHUB_TOKEN.
Azure Artifacts caps standard packages at 500 MiB per file while Universal Packages accept up to 4 TiB, making them the answer for multi-gigabyte models and toolchains.
Azure Artifacts includes 2 GiB of free storage per organisation and enforces 5,000 versions per package ID and 20 upstreams per package type per feed.
Retention policies that keep the most recent n versions, while protecting anything promoted to a view, are the sanctioned way to control Azure Artifacts storage cost.
Last updated: September 2026
5.1 Selecting Package Tools: Azure Artifacts vs. GitHub Packages
Quick Summary: Modern DevOps pipelines must eliminate ad-hoc network file shares and unversioned binary dependencies. Azure Artifacts and GitHub Packages provide immutable, centralized package feeds supporting multiple language ecosystems. This section covers the selection decision itself: ecosystem coverage, size ceilings (500 MiB per package versus 4 TiB Universal Packages), storage and retention economics, and which identity plane the pipeline will authenticate against. Feed scoping, upstream sources and pipeline authentication follow in Section 5.2.
The Strategic Role of Package Management in CI/CD & DevSecOps
In early software development workflows, compiled libraries, shared utilities, and third-party binaries were frequently distributed via shared network folders ( \\fileshare\builds ), FTP servers, or even committed directly into Git source repositories. In enterprise cloud engineering, these practices represent critical anti-patterns:
Repository Bloat & History Pollution: Committing binary files ( .dll , .jar , .tgz , .nupkg ) directly into Git permanently expands repository size. Because Git is designed for tracking incremental text diffs, binary commits cause cloned repository sizes to balloon, drastically slowing clone, fetch, and checkout times across CI/CD agents and developer workstations.
Lack of Immutability and Traceability: Files stored on shared file shares can be overwritten, renamed, or deleted without cryptographic checksum verification or audit logging. This breaks build reproducibility—a build compiled on Tuesday may produce different runtime behavior than a build compiled on Friday using the same source code because an underlying binary on the network share changed.
Compilation Variance Across Environments: Recompiling shared libraries from raw source code inside every consuming application's pipeline introduces non-deterministic compilation variance (e.g., compiler minor version differences, differing environment flags, fluctuating compilation times).
Supply Chain Vulnerability: Consuming unverified third-party libraries directly from public internet endpoints without intermediary caching exposes the delivery lifecycle to public registry downtime, package unpublishing (such as the infamous left-pad incident), and upstream supply chain attacks.
Modern package management treats compiled binary artifacts as first-class versioned deliverables . A package encapsulates compiled binaries, transitive dependency declarations, licensing metadata, and cryptographic hashes into an immutable archive. Consuming projects declare explicit semantic dependencies on package feeds, ensuring reproducible, deterministic builds across every stage of the software delivery lifecycle (SDLC).
Azure Artifacts vs. GitHub Packages: Architectural Comparison
Both Azure DevOps and GitHub provide integrated package management solutions, but their supported package ecosystems, feed architectures, and enterprise capabilities differ significantly. Package Ecosystem Support Overview:
- [Azure Artifacts] [GitHub Packages]
- ├── NuGet (.NET) ├── NuGet (.NET)
- ├── npm (Node.js / JavaScript) ├── npm (Node.js / JavaScript)
- ├── Maven / Gradle (Java) ├── Maven / Gradle (Java)
- ├── Python (PyPI / pip / twine) ├── RubyGems (Ruby)
- └── Universal Packages (Arbitrary files up to 4 TiB) └── Docker / OCI Containers (via ghcr.io)
- Detailed Ecosystem Support
Azure Artifacts:
NuGet: Supports .nupkg packages for .NET Core, .NET 5+, and .NET Framework libraries.
npm: Supports .tgz archives for Node.js, Angular, React, and JavaScript/TypeScript ecosystems.
Maven: Supports Java packages ( .jar , .war , .pom ) managed through Maven and Gradle.
Python (PyPI): Supports .whl (wheels) and .tar.gz (source distributions) managed via pip , twine , and poetry .
Universal Packages: A unique capability of Azure Artifacts. Universal Packages allow teams to package, version, and distribute arbitrary collections of files (e.g., pre-trained machine learning models, compiled C++ native binaries, testing data sets, hardware drivers, mobile runtime runtimes) up to 4 TiB in size . Universal Packages are managed natively via the Azure CLI ( az artifacts universal ).
GitHub Packages:
Supports npm , NuGet , Maven , and RubyGems .
Docker & OCI Container Registry: GitHub Packages integrates container image management directly via the GitHub Container Registry ( ghcr.io ) , supporting Open Container Initiative (OCI) image specifications and Docker images. In contrast, Azure DevOps does not host container images inside Azure Artifacts; container images in Azure are hosted in Azure Container Registry (ACR) .
Platform Feature Matrix
- Architectural Feature Azure Artifacts GitHub Packages
- Primary Host Platform Azure DevOps Services / Azure DevOps Server GitHub.com / GitHub Enterprise Server
Supported Package Types NuGet, npm, Maven, PyPI, Universal Packages npm, NuGet, Maven, RubyGems, Docker/OCI ( ghcr.io )
- Container Image Hosting No (Delegated to Azure Container Registry) Yes (GitHub Container Registry ghcr.io )
- Arbitrary Binary Blobs Universal Packages (Up to 4 TiB) No native equivalent (relies on Git LFS or Releases)
Feed Scoping Levels Project-scoped and Organization-scoped feeds Repository-scoped and Organization-scoped packages
Public Registry Upstreams nuget.org, npmjs.com, PyPI, Maven Central npmjs, nuget.org, RubyGems, Maven Central
Quality Promotion Gates Feed Views ( @local , @prerelease , @release ) Semantic tagging, release branches, or pre-release tags
Pipeline Integration Dedicated Azure Pipeline tasks with $(System.AccessToken) GitHub Actions with secrets.GITHUB_TOKEN
Maximum Package Size 500 MiB (NuGet/npm/PyPI/Maven); 4 TiB (Universal) 5 GB (npm/NuGet/Maven); 10 GB (Docker layers)
Important
AZ-400 Exam Distinction: Azure Artifacts does not host Docker container images. When an exam question involves storing Docker container images with geo-replication, vulnerability scanning, and webhook triggers in Azure, the correct service is Azure Container Registry (ACR) , not Azure Artifacts. If the question requires storing arbitrary 50 GB binary files or ML models, the correct answer is Universal Packages in Azure Artifacts .
Selection Criteria: Cost, Retention and Operational Fit
Exam questions about "which package platform" are rarely about features alone. Weigh four axes:
Criterion Azure Artifacts GitHub Packages
Included storage 2 GiB free per organization, then billed per GiB Included in GitHub plan storage/transfer allowances; overage billed
Size ceiling 500 MiB per package file (NuGet, npm, Maven, Python, Cargo); 4 TiB for Universal Packages 5 GB per package; 10 GB per container layer
Count limits 5,000 versions per package ID; unlimited package IDs per feed; 20 upstreams per package type per feed No published per-package version cap
Where identity lives Azure DevOps org, project and feed roles GitHub org, repository and team permissions
Two decision rules cover most scenarios:
Follow the source control and the pipeline. If the repositories and the CI already live in GitHub, GitHub Packages removes a second identity plane and lets secrets.GITHUB_TOKEN do the publishing. If the CI is Azure Pipelines, Azure Artifacts lets $(System.AccessToken) and the built-in NuGetAuthenticate / npmAuthenticate tasks do the same without a stored credential.
Follow the payload. Anything above 500 MiB, or any non-package payload (ML model weights, driver bundles, simulation images, test corpora) belongs in Universal Packages ; container images belong in a container registry (ACR or GHCR), never in an Azure Artifacts feed.
Retention is the third, frequently forgotten axis. Azure Artifacts retention policies delete older versions automatically (keep the most recent n versions per package, protecting anything promoted to a view), which is the sanctioned way to stay under the free tier. GitHub Packages relies on manual deletion or a scheduled workflow calling the packages REST API.