You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[🔄 GitHub Organization Rename Impact](docs/18-github-rename-org-impact.md) - Impact analysis of renaming a GitHub organization on Copilot, EMU authentication, and post-rename actions
-[� Azure Pipelines with GitHub Repos Integration](docs/15-azure-pipelines-github-repos-integration.md) - Impact analysis of using Azure Pipelines with GitHub repositories after migration
49
51
-[🔍 Azure DevOps to GitHub Migration Analysis](docs/16-azure-devops-to-github-migration-analysis.md) - Detailed technical analysis of the migration process
50
52
-[🔑 ADO REST API Authentication Without PATs](docs/ado-rest-api-auth-without-pat.md) - Alternatives to Personal Access Tokens for Azure DevOps REST API authentication in CI/CD pipelines
53
+
-[🧹 ADO Tenant & Org Cleanup](docs/ADO-Tenant-Org-Cleanup.md) - Post-migration cleanup of Azure DevOps tenant connections, PAT policies, orphaned orgs
51
54
-[❓ ADO to GitHub Migration Q&A Guide](docs/ADO-to-GitHub-Migration-QA.md) - Detailed questions and answers about migrating from Azure DevOps to GitHub using GEI
52
55
-[💬 Workshop FAQ](docs/FAQ-workshop.md) - Frequently asked questions from GitHub Enterprise Admin workshops, including migration-related topics
-[Roles in an organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)
96
+
-[Roles in an organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#about-predefined-organization-roles)
94
97
-[Configuring SCIM provisioning for Enterprise Managed Users](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)
-[Managing a branch protection rule](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)
-[admin Archives | The GitHub Blog](https://github.blog/changelog/label/admin/)
104
107
105
108
### Videos
109
+
> Note: The videos below are from GitHub Universe 2021 and may show superseded UI. For current sessions see https://www.youtube.com/githubtraining .
106
110
-[What's new for GitHub Enterprise - GitHub Universe 2021 - YouTube](https://www.youtube-nocookie.com/embed/ZZviWZgrqhM)
107
111
-[GitHub in the Enterprise - GitHub Universe 2021 - YouTube](https://www.youtube.com/watch?v=1-i39RqaxRs)
108
112
-[Enforcing information security policy through GitHub Enterprise - GitHub Universe 2021 - YouTube](https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI)
109
113
-[GitHub Universe](https://githubuniverse.com/)
110
114
111
115
### Articles & Guides
112
116
-[Best practices for organizations and teams using GitHub Enterprise Cloud](https://github.blog/2023-08-02-best-practices-for-organizations-and-teams-using-github-enterprise-cloud/)
113
-
-[Everything new from GitHub Universe 2022](https://github.blog/2022-11-09-everything-new-from-github-universe-2022/)
117
+
-[Everything new from GitHub Universe 2022](https://github.blog/2022-11-09-everything-new-from-github-universe-2022/) (2022 — refer to GitHub's blog for more recent announcements)
114
118
-[Improved management for GitHub Enterprise owners | The GitHub Blog](https://github.blog/2022-03-10-improved-management-github-enterprise-owners/)
115
119
-[How to secure your GitHub organization and enterprise account | The GitHub Blog](https://github.blog/2020-07-23-how-to-secure-your-github-organization-and-enterprise-account/)
116
-
-[Connect GitHub Enterprise Cloud to Defender for Cloud Apps | Microsoft Docs](https://docs.microsoft.com/en-us/defender-cloud-apps/connect-github-ec)
117
-
-[How Defender for Cloud Apps helps protect your GitHub Enterprise environment | Microsoft Docs](https://docs.microsoft.com/en-us/defender-cloud-apps/protect-github)
-[Connect GitHub Enterprise Cloud to Defender for Cloud Apps | Microsoft Docs](https://learn.microsoft.com/en-us/defender-cloud-apps/connect-github-ec)
121
+
-[How Defender for Cloud Apps helps protect your GitHub Enterprise environment | Microsoft Docs](https://learn.microsoft.com/en-us/defender-cloud-apps/protect-github)
-[Removing sensitive data from a repository - GitHub Docs](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)
Copy file name to clipboardExpand all lines: docs/01-enterprise-hierarchy.md
+27-4Lines changed: 27 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,28 @@
1
1
# GitHub Enterprise Cloud Hierarchy
2
2
3
+
> **Document status**
4
+
>
5
+
> -**Last reviewed:** 2026-05-19
6
+
> -**Authorship:** Drafted with AI assistance (GitHub Copilot, multi-model review) and reviewed by a human maintainer before publication.
7
+
> -**Sources:** Based on public documentation — primarily [docs.github.com](https://docs.github.com), [learn.microsoft.com](https://learn.microsoft.com), and official vendor blogs cited inline.
8
+
> -**Verify before acting:** GitHub and Microsoft update product documentation continuously. Re-confirm against the live source pages before relying on this content for production decisions.
-[Enterprise Audit Log and Compliance Features](#enterprise-audit-log-and-compliance-features)
20
+
-[Best Practices for Enterprise Administration](#best-practices-for-enterprise-administration)
21
+
-[Advanced Topics](#advanced-topics)
22
+
-[Migration and Onboarding Strategies](#migration-and-onboarding-strategies)
23
+
-[Troubleshooting Common Issues](#troubleshooting-common-issues)
24
+
-[References](#references)
25
+
3
26
## Overview
4
27
5
28
GitHub Enterprise Cloud (GHEC) provides a multi-tiered organizational structure that enables large organizations to manage multiple teams, projects, and repositories under a unified enterprise account. This hierarchical model facilitates centralized governance, billing, and policy enforcement while maintaining organizational autonomy and flexibility.
@@ -15,7 +38,7 @@ An enterprise account on GitHub Enterprise Cloud delivers advanced administrativ
15
38
**Centralized Management**
16
39
- Unified dashboard providing real-time visibility across all organizations
17
40
- Consolidated user management with enterprise-level identity provisioning
18
-
- Single sign-on (SSO) enforcement via SAML 2.0 or OIDC
41
+
- Single sign-on (SSO) enforcement via SAML 2.0 (all enterprises); OIDC available for Enterprise Managed Users (EMU) enterprises only
19
42
- Centralized billing with cost allocation and usage analytics
20
43
21
44
**Security and Compliance**
@@ -27,7 +50,7 @@ An enterprise account on GitHub Enterprise Cloud delivers advanced administrativ
27
50
28
51
**Policy Enforcement**
29
52
- Repository policy management across organizations
30
-
-Branch protection rules inheritance
53
+
-Repository Rulesets (applicable at enterprise → organization → repository scope)
31
54
- Required workflows for GitHub Actions
32
55
- Custom repository roles and permissions
33
56
- Dependency management and security advisories
@@ -302,7 +325,7 @@ The Settings area provides access to critical configuration options:
302
325
- Runner group management and registration
303
326
304
327
**Audit Log**
305
-
- Searchable event log with 180+ day retention
328
+
- Searchable event log with 180-day retention (extendable via log streaming to external SIEM)
306
329
- Export capabilities (JSON, CSV)
307
330
- Real-time event streaming to SIEM platforms
308
331
- Compliance reporting and anomaly detection
@@ -626,7 +649,7 @@ For long-term retention and advanced analytics, configure audit log streaming:
626
649
EMU provides complete lifecycle management of user identities through your Identity Provider:
627
650
628
651
**Key Characteristics**
629
-
-GitHub manages user accounts on your behalf
652
+
-User accounts are provisioned and managed by your identity provider (IdP) via SCIM
Copy file name to clipboardExpand all lines: docs/02-organization-strategies.md
+21-2Lines changed: 21 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,24 @@
1
1
# Organization Design Patterns and Strategies
2
2
3
+
> **Document status**
4
+
>
5
+
> -**Last reviewed:** 2026-05-19
6
+
> -**Authorship:** Drafted with AI assistance (GitHub Copilot, multi-model review) and reviewed by a human maintainer before publication.
7
+
> -**Sources:** Based on public documentation — primarily [docs.github.com](https://docs.github.com), [learn.microsoft.com](https://learn.microsoft.com), and official vendor blogs cited inline.
8
+
> -**Verify before acting:** GitHub and Microsoft update product documentation continuously. Re-confirm against the live source pages before relying on this content for production decisions.
Organization architecture represents one of the most critical design decisions in GitHub Enterprise Cloud (GHEC) deployment. The organizational structure directly impacts security boundaries, policy enforcement, cost allocation, compliance posture, and operational efficiency. This document provides expert-level guidance on selecting, implementing, and evolving organization design patterns for enterprise-scale GitHub deployments.
@@ -159,7 +178,7 @@ graph TD
159
178
160
179
### Red-Green-Sandbox-Archive Pattern
161
180
162
-
The Red-Green-Sandbox-Archive pattern is GitHub's **recommended multi-organization model** for enterprises that need more than a single organization. This pattern is based on **visibility and access control levels**, not deployment environments.
181
+
The Red-Green-Sandbox-Archive pattern is a well-established multi-organization model widely used in GitHub Enterprise Cloud deployments. This pattern is based on **visibility and access control levels**, not deployment environments.
163
182
164
183
> **Reference:** This pattern is officially documented in [Strategies for using organizations in GitHub Enterprise Cloud](https://resources.github.com/learn/pathways/administration-governance/essentials/strategies-for-using-organizations-github-enterprise-cloud/).
165
184
@@ -269,7 +288,7 @@ The Sandbox organization provides a **shared space where any user can create and
269
288
- Abandoned experiments are periodically cleaned up or archived
270
289
- No expectation of long-term maintenance
271
290
272
-
> **Note:** A Sandbox organization is especially important if you configure GHEC to prevent developers from creating personal repositories.
291
+
> **Note:** A Sandbox organization is especially important if you use Enterprise Managed Users (EMU) and configure the enterprise policy to block user-namespace repository creation. Note: This policy is EMU-only; in personal-account enterprises, GitHub cannot prevent personal repository creation.
0 commit comments