BrainyBeeBrainyBee
ExploreBlogStart Studying
HomeDesigning and Implementing Microsoft DevOps Solutions (AZ-400)Choosing package management tools
Lesson301 words

Choosing package management tools

Recommend package management tools

Azure Artifacts and GitHub Packages both host packages. Choose by package ecosystem, governance boundary, CI integration, and whether the organisation needs Azure Artifacts to retain dependencies from upstream registries.

Decision signalAzure ArtifactsGitHub Packages
Platform fitAzure DevOps organisation- or project-scoped feedGitHub-native hosting integrated with GitHub Actions, APIs, and webhooks
FormatsNuGet, npm, Maven, Python, Cargo, Universal Packagesnpm, RubyGems, Maven, Gradle, NuGet, and Container registry for Docker/OCI images
PermissionsFeed Reader; Feed and Upstream Reader (Collaborator); Feed Publisher (Contributor); Feed OwnerRead/Write/Admin; package scope depends on the registry and can be user, organisation, or repository based

The discriminator: upstream sources

When upstream sources are enabled, Azure Artifacts automatically saves a package installed from an upstream by a Feed and Upstream Reader (Collaborator) or higher. Once saved, that package version is immutable and remains in the feed even if the upstream is later disabled or removed.

That capability answers several exam scenarios at once:

  • Reliability — a previously saved version remains retrievable during a temporary public-registry outage.
  • Centralised inventory — the feed retains the versions and metadata installed through it.
  • Package integrity — the saved version is immutable, so a later upstream change cannot silently replace it.

If a question mentions retaining public dependencies in an Azure DevOps feed, surviving an upstream outage after those versions were saved, or using one configured feed for internal and external packages, it is pointing at Azure Artifacts upstream sources. If the requirement instead emphasises GitHub-native package hosting and GitHub Actions/API integration, consider GitHub Packages and then check the selected registry's permission model.

Primary sources

  • https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400
  • https://learn.microsoft.com/en-us/azure/devops/artifacts/concepts/feeds
  • https://learn.microsoft.com/en-us/azure/devops/artifacts/concepts/upstream-sources
  • https://learn.microsoft.com/en-us/azure/devops/artifacts/feeds/feed-permissions
  • https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages
  • https://docs.github.com/en/packages/learn-github-packages/about-permissions-for-github-packages
All Designing and Implementing Microsoft DevOps Solutions (AZ-400) Study Resources

Related Notes

  • Agent and runner infrastructure533 words
  • Agent and runner infrastructure — quick notes222 words
  • Alerting on pipeline events255 words
  • Alerting on pipeline events — quick notes94 words
  • Analyzing usage and application performance241 words
  • Analyzing usage and application performance — quick notes73 words
  • Appropriate access levels294 words
  • Appropriate access levels — quick notes180 words
  • Automating container scanning277 words
  • Automating container scanning — quick notes96 words
  • Automating documentation from Git history191 words
  • Automating documentation from Git history — quick notes55 words

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up.

Start Studying

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up needed.

Start Studying — Free
Designing and Implementing Microsoft DevOps Solutions (AZ-400) ResourcesExplore All HivesBlogHome

© 2026 BrainyBee. Free AI-powered exam prep.