Microsoft Certified: GitHub Administration (GH-100)

When GitHub becomes shared infrastructure for development, DevOps, and security teams, early access decisions are hard to undo. The course gives one example: an enterprise built on personal accounts cannot later switch to Enterprise Managed Users, or the reverse, once users have been added. This GH-100 training gives GitHub administrators, platform engineers, and DevOps Team Leads one consistent approach to identity, roles, policies, audit logging, secret protection, and Actions governance.

Role fit and time investment: The course has 18 skills and about 14 hours of instruction. Most teams do best with focused weekly blocks over several weeks rather than a single sprint. It assumes intermediate, hands-on GitHub experience. It is not a Git fundamentals course.

Risk and audit framing: Your team works through least-privilege access, enterprise-wide base permissions, access audits, and audit logging. These are the controls that come up in audit reviews.

Change-management notes: Learners follow along in a GitHub Enterprise trial environment and connect an Okta account for SAML SSO. Give them sandbox accounts rather than having them experiment in production. Before rolling changes out, confirm identity, access, and self-hosted runner decisions with your identity and CI/CD owners.

Training Managers can assign the course through Playlists and track progress with Team Reporting. Practice Exams help gauge GH-100 readiness before your team schedules exams.

IT teams complete this training to turn GitHub from a loosely managed developer tool into a governed enterprise platform. The course works through realistic admin scenarios: choosing the right deployment and account model before users are added, since an enterprise cannot switch between personal accounts and Enterprise Managed Users afterward. It also covers planning seat and usage requirements for a heavy CI/CD organization, and tracing how a single base-role setting can quietly grant read access without a direct access record.

• Fewer access surprises during audits: Administrators learn how enterprise, organization, and repo roles interact, how to set base permissions once across every organization, and how to apply least privilege with SAML SSO through an external identity provider.
• Lower risk of leaked credentials: Your team sees why secret leaks are so damaging and configures secret scanning and push protection. They also learn to keep sensitive values such as API keys and database passwords out of workflow logs, where people without that access could read them.
• Security checks built into delivery: Engineers connect security analysis to pull requests, rulesets, and policies, and work through dependency-related supply chain controls in a project repository.
• Governed automation: Platform engineers control which Actions code repositories can run, scope secrets by environment (dev, QA, production), and run workflows on self-hosted runners while understanding the security trade-offs.

The result is a GitHub environment where access, security settings, and automation follow organizational policy instead of individual habit.

Knowledge

• How the four GitHub deployment and account combinations differ (github.com with personal accounts or EMU, GHE.com with EMU, GHES), and why the personal-vs-EMU choice can't be reversed after users are added
• How enterprise, organization, and repository roles, base permissions, and team access combine, and why a single "yes" from any path grants access
• How identity providers, SAML SSO, 2FA, and SCIM provisioning shape the user sign-in experience and lifecycle
• How accidental secret leaks, code vulnerabilities, and malicious dependencies create risk, and how GitHub alerts, remediation guidance, and push protection settings help admins respond
• How least-privilege design, member privileges, repository policies, and Actions governance affect the enterprise attack surface
• When to use GitHub Support, and how rate limiting affects automation

Ability

• Estimate licensing and Actions costs for realistic scenarios, and set billing alerts and budgets
• Integrate an IdP such as Okta for SAML SSO, then audit roles and access using least-privilege principles
• Apply enterprise-wide policies, rulesets, and base permissions so standards hold across many organizations
• Review security findings for leaked secrets, code vulnerabilities, and malicious dependencies, then act on remediation guidance
• Govern Actions usage and workflow standards across organizations
• Audit member privileges and repository access to reduce exposure of sensitive or proprietary code