Study guide

13.4 Access Levels, GitHub Roles & Outside Collaborators

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

13.4 Access Levels, GitHub Roles & Outside Collaborators

Key Takeaways Explain This Topic AI

Azure DevOps access levels are Stakeholder, Basic, and Basic plus Test Plans; Stakeholder is free but hides Repos and Pipelines for private projects.

Assign Stakeholder to product owners and business sponsors who work only in Boards and dashboards.

A Basic licence grants hub visibility but grants no permission by itself - authorisation still comes from security group membership.

GitHub repository roles are Read, Triage, Write, Maintain and Admin; Maintain manages settings and branch protection without destructive administrative rights.

Outside collaborators receive access to specific repositories without joining the organisation, so contractors never see the member directory or internal repositories.

Last updated: September 2026

13.4 Access Levels, GitHub Roles & Outside Collaborators

Security groups answer "what may this person do". Access levels answer a different question - "what has this person been licensed to see" - and mixing the two up explains most access-troubleshooting scenarios on the exam.

1. Access Levels vs. Security Groups: Licensing vs. Authorization

A critical distinction tested on the AZ-400 exam is the difference between an Access Level and a Security Group .

Access Level : Determines which features and UI elements are enabled for a user based on their Visual Studio / Azure DevOps license.

Security Group : Determines what actions and operations a user is permitted to perform within those enabled features.

Exam Warning : Adding a user to the Project Administrators security group will NOT allow them to view or edit code if their assigned Access Level is set to Stakeholder !

Azure DevOps Access Levels

Feature / Service Stakeholder (Free / Unlimited) Basic (Standard Developer) Basic + Test Plans Visual Studio Enterprise

Cost / Licensing Free for unlimited users 5 free users, then monthly fee Monthly paid add-on Included with VS Enterprise subscription

Azure Boards Full backlog & work item view/edit Full backlog, board, sprint tracking Full backlog, board, sprint tracking Full backlog, board, sprint tracking

  • Azure Repos No access (cannot view/commit code) Full access (clone, commit, PRs) Full access Full access
  • Azure Pipelines No access (cannot author/run) Full access (author, queue, review) Full access Full access
  • Azure Artifacts View public feeds only Full package management Full package management Full package management

Azure Test Plans No manual test authoring View test runs only Full authoring & execution Full authoring & execution

When to Assign Stakeholder Access

Assign Stakeholder access to product owners, business analysts, executive leadership, and project managers who only need to track work items, update user stories, and monitor kanban boards without interacting with Git repositories or CI/CD pipelines.

2. GitHub Enterprise Repository Roles & Collaborator Governance

When managing source code and workflows in GitHub Enterprise, organizations implement GitHub's five base repository permission tiers. ┌─────────────────────────────────────────────────────────────────────────────┐

  • │ GitHub Base Repository Permission Tiers │
  • ├─────────────────────────────────────────────────────────────────────────────┤
  • │ 1. READ • View code, clone repository, open issues, submit pull reqs │
  • ├─────────────────────────────────────────────────────────────────────────────┤
  • │ 2. TRIAGE • Everything in Read PLUS: Manage issues, apply labels, │
  • │ close issues, manage milestones (No code write access) │
  • ├─────────────────────────────────────────────────────────────────────────────┤
  • │ 3. WRITE • Everything in Triage PLUS: Push code to non-protected │
  • │ branches, create releases, trigger workflows │
  • ├─────────────────────────────────────────────────────────────────────────────┤
  • │ 4. MAINTAIN • Everything in Write PLUS: Manage repository settings, │
  • │ configure branch protection rules (Cannot delete repo) │
  • ├─────────────────────────────────────────────────────────────────────────────┤
  • │ 5. ADMIN • Full control: Delete repo, manage collaborator permissions, │
  • │ configure security & analysis features │
  • └─────────────────────────────────────────────────────────────────────────────┘
  • Deep Dive: Triage and Maintain Roles

Triage : Specifically designed for community managers, technical writers, or issue triagers who need to organize backlogs, label bug reports, and close duplicate issues without the ability to push commits or alter code.

Maintain : Designed for engineering team leads and project managers who must configure repository settings, define branch protection rules, manage webhooks, and oversee releases without possessing destructive administrative powers (such as deleting the repository or transferring ownership).

Managing External Contractors: Outside Collaborators

In enterprise development, organizations frequently engage external vendors, third-party penetration testers, or contractors. Adding external contractors as full members of a GitHub Organization exposes internal organization member directories, public and internal repositories, and teams.

Outside Collaborators : Users who are granted explicit access to one or more specific repositories without being added as members of the GitHub Organization.

Security Best Practices for Contractors :

Enforce Multi-Factor Authentication (MFA) across all Outside Collaborators.

Grant the minimum required repository role (typically Write for software contractors, Read for auditors).

Configure automated expiration of collaborator access.

Restrict fork permissions and prevent outside collaborators from inviting other collaborators.

3. Comprehensive Permission Mapping Matrix

Organizational Persona / Responsibility Recommended Azure DevOps Group Required Azure DevOps Access Level Equivalent GitHub Repository Role

  • Product Owner / Business Analyst Project Readers Stakeholder Read (or Read on Project Board)
  • Quality Assurance / Test Engineer Project Contributors Basic + Test Plans Write
  • Full-Stack Software Engineer Project Contributors Basic Write
  • Engineering Team Lead Project Administrators (or custom lead group) Basic Maintain
  • Scrum Master / Agile Coach Project Contributors Stakeholder (or Basic) Triage
  • DevOps Infrastructure Architect Build & Release Administrators Basic Admin
  • External Security Auditor / Pen Tester Project Readers Basic (or Stakeholder) Read (via Outside Collaborator)
  • 4. Realistic Enterprise Governance Scenario & Common Traps
  • Scenario: Regulated Banking Contractor Onboarding

Company : Woodgrove Bank is contracting an external mobile development agency (Contoso Mobile) to build a new iOS/Android banking interface. The project repository is hosted in Azure Repos and the CI/CD pipeline runs in Azure Pipelines.

Governance Requirements :

Contractors must be able to view work items, branch code, and submit Pull Requests.

Contractors must never be able to bypass branch policies, push directly to main , delete release branches, or view internal core-banking repositories.

Contractors must not have access to production deployment pipelines or production service connections.

Solution Architecture :

Licensing : Provision Basic Access Level licenses for the contractor accounts so they can access Azure Repos and Pipelines.

Security Group : Create a custom project security group named External-Contractors .

Repository Permissions : At the project level, grant External-Contractors Read and Contribute permissions. On the main branch, configure a strict Branch Policy requiring 2 reviewers, linked work items, and successful build validation. Explicitly set Bypass policies when completing pull requests to Deny .

Service Connection Isolation : Ensure production service connections are set to Restricted pipeline permissions. Grant External-Contractors only the User role on development service connections, completely hiding production connections.

Effective State : Even if a contractor is added to a secondary team group that has Allow for policy bypass, the explicit Deny on External-Contractors guarantees they cannot bypass branch safeguards.

Common Exam Traps to Avoid

Trap: Believing an explicit Allow can override a Deny from another group. If a user belongs to Developers (Allow) and Contractors (Deny) for the same permission, the effective permission is ALWAYS Deny . The only way to grant access is to remove the user from the group containing the Deny or change the Deny to Not Set.

Trap: Confusing Access Levels with Security Group Permissions. If a developer in Project Contributors cannot see the Repos menu, checking their Security Group permissions will not solve the issue. The administrator must check Organization Settings → Users and upgrade their Access Level from Stakeholder to Basic .

Trap: Assigning Maintain role when repository deletion is required. The GitHub Maintain role cannot delete a repository, manage billing, or adjust organization-wide security defaults. If an exam scenario requires managing repository deletion or collaborator permissions, the correct answer is Admin .