Microsoft GitHub Administration

Sign-in is the front door of the enterprise. You connect GitHub to an identity provider with SAML single sign-on, enforce two-factor authentication, and use Enterprise Managed Users where full control is needed.

• SAML SSO for organizations and enterprises
• Enterprise Managed Users and what they change
• Enforcing two-factor authentication
• Recovery and break-glass access
• Troubleshooting sign-in problems

You build A sign-in design for an enterprise, with SSO, two-factor enforcement and a recovery plan.

People join, move and leave, and access must follow. You provision and deprovision users with SCIM, synchronize teams from the identity provider, and keep a clean record of who has access to what.

• What SCIM provisioning does
• Mapping identity groups to teams
• Team sync and its limits
• Deprovisioning leavers
• Auditing access after a reorganization

You build A provisioning flow that maps identity provider groups to teams, with a leaver process.

Who can do what decides both speed and risk. You use organization and repository roles, custom roles, teams and enterprise teams to give each person the least access they need.

• Organization roles and owners
• Repository roles and permissions
• Custom repository roles
• Teams, nested teams and enterprise teams
• Reviewing and trimming permissions

You build A permissions model for three departments, using teams and custom roles.

Administrators answer for seats, bills and outages. You track licenses, read billing information, support users and stakeholders, and gather support bundles when GitHub Support needs them.

• License types and consumption
• Billing, budgets and cost centers
• Supporting users and stakeholders
• Opening a case with GitHub Support
• Generating a support bundle

You build A licensing and billing overview for a sample enterprise, with a support-request template.

Consistency across thousands of repositories needs rules that apply themselves. You set enterprise policies, write rulesets for branches and tags, and define what repository owners may and may not change.

• Enterprise and organization policies
• Rulesets for branches and tags
• Required reviews, status checks and signed commits
• Repository creation and visibility policies
• Code owners and review responsibilities

You build A ruleset that protects default branches across an organization, tested with a violating push.

Administrators decide which protections exist and who must use them. You enable repository security features at scale, set the policies that govern them, and connect them to compliance requirements.

• Security features available to administrators
• Enabling features across an organization
• Security policies and defaults
• Mapping controls to compliance requirements
• Reporting security posture to stakeholders

You build A security configuration for an organization, mapped to the compliance requirements it supports.

Tools and people call GitHub through tokens and apps, and each is a way in. You compare personal access tokens, GitHub Apps and OAuth apps, set policies over them, and manage SSH keys and deploy keys.

• Fine-grained and classic personal access tokens
• GitHub Apps compared with OAuth apps
• Token policies and approval for organizations
• SSH keys and deploy keys
• Reviewing and revoking integrations

You build A token and integration policy for an organization, with a review of what is currently installed.

Actions runs code with the company’s credentials, so it needs governance. You set which actions and workflows may run, organize runners into groups, restrict network access and manage secrets for the enterprise.

• Policies for allowed actions and reusable workflows
• Runner groups and access to them
• IP allow lists and network restrictions
• Organization and environment secrets
• Reviewing Actions use across the enterprise

You build An Actions governance setup with runner groups, allowed-action policy and secret scopes.

You cannot govern what you cannot see, and metered products can grow quietly. You search and stream audit logs, read usage reports, and tune the settings that drive cost and performance.

• What the audit log records
• Searching, exporting and streaming logs
• Usage reports for metered products
• Finding the settings that drive cost
• Setting alerts and review routines

You build An audit and usage review for a sample enterprise, with three cost or risk findings and the fixes.

One enterprise joins the course. You design its identity, access, policy and security, govern Actions, set up auditing and cost control, and present the operating model to its stakeholders.

• Reading the company’s requirements
• Designing identity, access and policy
• Governing security and Actions
• Setting up audit, usage and support routines
• Presenting the operating model

You build A GitHub Enterprise administration plan for a sample company, from sign-in to audit.