BrainyBeeBrainyBee
ExploreBlogStart Studying
HomeDesigning and Implementing Microsoft DevOps Solutions (AZ-400)Integrating GitHub repositories with Azure Pipelines
Lesson314 words

Integrating GitHub repositories with Azure Pipelines

Design and implement integration between GitHub repositories and Azure Pipelines

Three authentication types, and one is recommended

TypeRuns asGuidance
GitHub AppThe Azure Pipelines identityRecommended for CI; supports GitHub Checks
OAuthYour personal GitHub identitySupported; your repository access must remain active; no GitHub Checks
PATYour personal GitHub identitySupported through a GitHub service connection, but discouraged; if necessary, use a narrowly scoped fine-grained PAT

The GitHub App is the recommended type for CI. Once installed, builds and status updates use the Azure Pipelines identity rather than a personal GitHub identity. It also integrates with GitHub Checks to surface build, test, and coverage results in the pull request. OAuth and PAT integrations depend on the personal identity retaining the required repository access.

Scope it deliberately. Installing the app for all repositories in an organisation gives its token access to all of them, including private ones. Microsoft's guidance is to separate public and private repositories at the organisation level, or to explicitly select the repositories the app may access.

Forks are a policy-controlled security boundary

Organization or project controls under Pipelines → Settings → Triggers can disable fork-PR builds, securely build them, or customize the rules. New Azure DevOps projects and organizations default to disabling builds from forked GitHub repositories.

When Securely build pull requests from forked repositories is selected, a team member must comment before the pipeline runs, and the build receives neither pipeline secrets nor the same permissions as a normal build. This protects against untrusted fork code exfiltrating credentials. A pipeline's Triggers → Build pull requests from forks of this repository checkbox is an additional choice only where the central policy permits it.

Primary sources

  • https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/github
  • https://learn.microsoft.com/en-us/azure/devops/pipelines/security/secure-access-to-repos
  • https://learn.microsoft.com/en-us/azure/devops/release-notes/2023/pipelines/sprint-229-update
  • https://docs.github.com/en/apps/using-github-apps/installing-a-github-app-from-a-third-party
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.