Skip to main content

Chapter 1: Enterprise Subscription & Environment Setup

Part I: Foundation & Identity Prerequisites: None GH-100 Exam Mapping: Domain 1 (Support GitHub Enterprise for users and stakeholders — 9%), Domain 3 (Describe how GitHub is deployed, distributed, and licensed — 9%) Verified: 2026-02-01 against official documentation

1. Introduction​

Learning Objectives​

After completing this chapter, you will be able to:

  • Explain the differences between GitHub Enterprise Cloud (GHEC), GitHub Enterprise Server (GHES), and GHE.com
  • Describe GitHub licensing models and how they apply to enterprise organizations
  • Set up a GitHub Enterprise Cloud trial environment
  • Navigate the enterprise account hierarchy: enterprise, organizations, teams, and repositories

Exam Domain Coverage​

DomainTopics in This Chapter
D1: Support GitHub Enterprise (9%)Enterprise account creation, support tiers, environment overview
D3: Deployment, distribution, licensing (9%)GHEC vs GHES vs GHE.com, licensing models, trial setup

Chapter Overview​

GitHub Enterprise is the foundation of any organization's journey toward modern, AI-assisted development. Before configuring identity providers, enabling Copilot, or deploying coding agents, administrators must first understand the GitHub Enterprise landscape and establish their cloud environment.

This chapter introduces the three GitHub Enterprise deployment options — GitHub Enterprise Cloud (GHEC), GitHub Enterprise Server (GHES), and the newer GHE.com — and explains when each is appropriate. You will learn how GitHub's licensing models work at the enterprise, organization, and individual levels, and how the enterprise account hierarchy organizes your teams and repositories.

By the end of this chapter, you will have a working GitHub Enterprise Cloud trial with an enterprise account and your first organization — the foundation on which every subsequent chapter builds.


2. Theory & Deep Dive​

GitHub Enterprise Deployment Options​

GitHub offers three enterprise deployment models, each designed for different organizational needs:

GitHub Enterprise Cloud (GHEC) is GitHub's fully managed cloud offering. GitHub hosts all infrastructure, handles updates, and provides 99.9% uptime SLA (Service Level Agreement). GHEC is the recommended choice for most enterprises because it eliminates infrastructure management overhead and provides immediate access to the latest features, including GitHub Copilot and coding agents.

GitHub Enterprise Server (GHES) is a self-hosted option where organizations deploy GitHub on their own infrastructure — on-premises or in a private cloud. GHES gives organizations full control over their data residency and network configuration, but requires dedicated infrastructure teams for maintenance, upgrades, and patching. Feature availability on GHES lags behind GHEC by one or more release cycles.

GHE.com is a newer offering that provides data residency guarantees within specific geographic regions while remaining GitHub-managed. Think of GHE.com as a middle ground: cloud-hosted by GitHub (like GHEC) but with data residency controls (like GHES). GHE.com uses a subdomain model (e.g., yourcompany.ghe.com) rather than the shared github.com namespace.

FeatureGHECGHESGHE.com
Hosted byGitHubSelf-hostedGitHub
Data residencyGitHub-managed (US/EU)Full controlRegion-specific
Feature availabilityImmediateDelayed (release cycles)Immediate
Infrastructure managementNoneFull responsibilityNone
URL namespacegithub.comCustom domainyourcompany.ghe.com
Copilot supportFullLimitedFull
Coding agent supportFullNot availableFull

Enterprise Scenario: A 500-developer financial services company needs GitHub Enterprise but has strict data residency requirements for European Union (EU) regulations. They evaluate GHES (self-hosted in EU data centers) versus GHE.com (GitHub-hosted with EU residency). GHE.com reduces their infrastructure burden while meeting compliance requirements, and provides immediate access to Copilot features that GHES cannot offer.

Licensing Models​

GitHub Enterprise licensing operates at multiple levels:

Enterprise License: The top-level license that covers the enterprise account itself. This includes GitHub Enterprise Cloud access for all members, GitHub Advanced Security features, and enterprise-level support. Enterprises are billed per user per month.

GitHub Copilot Plans: Copilot licensing is separate from the base Enterprise license:

  • Copilot Individual: For personal accounts (not available in managed enterprise environments)
  • Copilot Business: Organization-level Copilot access with policy controls and audit logging
  • Copilot Enterprise: Enterprise-level Copilot with knowledge bases, Bing integration, and advanced features

Seat Management: Enterprise owners can assign seats at the enterprise level (covering all organizations) or delegate seat assignment to organization owners. Unused seats can be reclaimed. GitHub provides usage reports and billing dashboards to optimize costs.

Enterprise Account Hierarchy​

The GitHub enterprise hierarchy has four levels:

  1. Enterprise Account — The top-level container. Enterprise owners manage policies, billing, identity, and audit logs that apply across all organizations.
  2. Organizations — Logical groupings within the enterprise. Each organization has its own members, teams, repositories, and settings. An enterprise typically has one organization per business unit, product line, or department.
  3. Teams — Groups of organization members used to manage repository access and mentions. Teams can be nested (parent → child) to mirror organizational structure.
  4. Repositories — The fundamental unit of code and content storage. Repositories belong to organizations and have visibility levels: public, internal (visible to all enterprise members), or private.

Enterprise Scenario: A technology company with 200 developers structures their enterprise as follows: one enterprise account (acme-corp), three organizations (acme-platform, acme-mobile, acme-data), and teams within each organization matching their department structure. Internal repositories allow cross-organization code sharing, while private repositories protect sensitive projects.

Setting Up a GitHub Enterprise Cloud Trial​

GitHub offers a 30-day free trial of GitHub Enterprise Cloud. The trial provides full feature access, including:

  • Enterprise account with unlimited organizations
  • GitHub Advanced Security (code scanning, secret scanning, Dependabot)
  • Audit log streaming
  • SAML Single Sign-On (SSO) configuration
  • Enterprise Managed Users (EMU) setup

To start a trial, you need a GitHub account (personal or existing organization owner account). The trial converts your account into an enterprise account with your first organization.


3. Diagrams​

Enterprise Account Hierarchy​

graph TD
EA[Enterprise Account<br/>acme-corp] --> ORG1[Organization<br/>acme-platform]
EA --> ORG2[Organization<br/>acme-mobile]
EA --> ORG3[Organization<br/>acme-data]

ORG1 --> T1[Team: Backend]
ORG1 --> T2[Team: Frontend]
ORG1 --> T3[Team: DevOps]

T1 --> R1[Repo: api-service]
T1 --> R2[Repo: auth-service]
T2 --> R3[Repo: web-app]
T3 --> R4[Repo: infra-config]

ORG2 --> T4[Team: iOS]
ORG2 --> T5[Team: Android]

T4 --> R5[Repo: ios-app]
T5 --> R6[Repo: android-app]

ORG3 --> T6[Team: Data Engineering]
T6 --> R7[Repo: data-pipeline]
T6 --> R8[Repo: ml-models]

style EA fill:#2d333b,stroke:#539bf5,color:#adbac7
style ORG1 fill:#2d333b,stroke:#57ab5a,color:#adbac7
style ORG2 fill:#2d333b,stroke:#57ab5a,color:#adbac7
style ORG3 fill:#2d333b,stroke:#57ab5a,color:#adbac7

Figure 1: Enterprise account hierarchy showing the enterprise → organization → team → repository structure. Each organization can contain multiple teams, and teams manage access to repositories.


4. Summary​

Key Takeaways:

  • GitHub Enterprise Cloud (GHEC) is the recommended deployment option for most enterprises, offering full Copilot and coding agent support with zero infrastructure management
  • GitHub Enterprise Server (GHES) provides self-hosted control but lags on features; GHE.com offers a middle ground with data residency guarantees
  • Enterprise licensing is per-user per-month, with Copilot plans (Business or Enterprise) billed separately
  • The enterprise hierarchy flows from enterprise account → organizations → teams → repositories, enabling granular policy and access control
  • A 30-day GHEC trial provides full feature access — sufficient to follow all hands-on labs in this book

What's Next: See Chapter 2: Identity & Single Sign-On for configuring SAML SSO and Enterprise Managed Users with Microsoft Entra ID.


5. Hands-On Assignment​

Prerequisites Check: This is the first lab in the book. You need:

  • A GitHub account (free tier is sufficient to start)
  • A web browser and internet access

Lab: Set Up GitHub Enterprise Cloud​

Objective: Create a GitHub Enterprise Cloud trial, establish your enterprise account, and create your first organization.

Prerequisites:

  • A GitHub account (free tier is sufficient to start the trial)
  • A web browser
  • GitHub CLI (gh) installed (version 2.40 or later)

Assignment:

  1. Sign up for a GitHub Enterprise Cloud 30-day trial
  2. Create your enterprise account with a descriptive name
  3. Create your first organization within the enterprise
  4. Invite at least one additional member to the organization
  5. Verify enterprise-level settings are accessible

Expected Outcome: A working GitHub Enterprise Cloud environment with an enterprise account, one organization, and at least two members.

Validation: You can access the enterprise settings page at https://github.com/enterprises/YOUR-ENTERPRISE/settings and see billing, policies, and identity tabs.


6. Step-by-Step Walkthrough​

This section provides a guided solution for the hands-on assignment above. If you completed the assignment independently, you can skip this section or use it to verify your approach.

Step 1: Start the Enterprise Cloud Trial​

Navigate to github.com/enterprise and click Start a free trial. Select Enterprise Cloud as your deployment option.

Follow the trial signup wizard:

  1. Enter your enterprise name (e.g., my-learning-enterprise)
  2. Accept the terms of service
  3. Complete the setup process

Step 2: Verify Enterprise Account Access​

After the trial is created, verify you can access the enterprise dashboard.

# Authenticate GitHub CLI with your enterprise account
gh auth login --hostname github.com

# Verify your authentication status
gh auth status

Expected output:

github.com
✓ Logged in to github.com account YOUR-USERNAME
✓ Git operations protocol: https
✓ Token: gho_****
✓ Token scopes: admin:enterprise, admin:org, repo, workflow

Step 3: Create Your First Organization​

# Create a new organization within your enterprise
# Note: Organization creation via CLI requires the browser flow
gh api --method POST /admin/organizations \
-f login="my-first-org" \
-f admin="YOUR-USERNAME" \
-f profile_name="My First Organization"

Alternatively, navigate to your enterprise settings in the browser:

  1. Go to https://github.com/enterprises/YOUR-ENTERPRISE
  2. Click Organizations in the sidebar
  3. Click New organization
  4. Enter the organization name and complete the setup

Step 4: Invite a Member​

# Invite a user to your organization
gh api --method POST /orgs/my-first-org/invitations \
-f email="colleague@example.com" \
-f role="direct_member"

Expected output:

{
"id": 12345678,
"role": "direct_member",
"email": "colleague@example.com",
"invitation_teams_url": "..."
}

Step 5: Explore Enterprise Settings​

# List organizations in your enterprise
gh api /enterprises/YOUR-ENTERPRISE/organizations --jq '.[].login'

Expected output:

my-first-org

Verification​

Confirm your setup is complete by running:

# Check enterprise billing information
gh api /enterprises/YOUR-ENTERPRISE -q '.billing_email'

# List organization members
gh api /orgs/my-first-org/members --jq '.[].login'

You should see your enterprise billing email and at least your own username in the members list.


7. Q&A — Chapter Review​

Instructions: Select the best answer for each question. Answers and explanations follow after all questions.

Question 1​

Which GitHub Enterprise deployment option provides data residency guarantees while remaining fully managed by GitHub?

  • A) GitHub Enterprise Cloud (GHEC)
  • B) GitHub Enterprise Server (GHES)
  • C) GHE.com
  • D) GitHub Team plan

Question 2​

What is the top-level container in GitHub's enterprise hierarchy?

  • A) Organization
  • B) Enterprise account
  • C) Team
  • D) Repository

Question 3​

Which Copilot plan provides enterprise-level policy controls and audit logging?

  • A) Copilot Individual
  • B) Copilot Free
  • C) Copilot Business
  • D) Copilot Team

Question 4​

A company needs full control over their GitHub data and hosts it on their own servers. Which deployment option should they choose?

  • A) GitHub Enterprise Cloud
  • B) GHE.com
  • C) GitHub Enterprise Server
  • D) GitHub Team

Question 5​

What is the maximum duration of a GitHub Enterprise Cloud free trial?

  • A) 7 days
  • B) 14 days
  • C) 30 days
  • D) 90 days

Question 6​

In the enterprise hierarchy, which entity directly contains teams?

  • A) Enterprise account
  • B) Organization
  • C) Repository
  • D) Project

Question 7​

Which repository visibility level allows all members across all organizations in an enterprise to access the repository?

  • A) Public
  • B) Private
  • C) Internal
  • D) Restricted

Question 8​

What is a key disadvantage of GitHub Enterprise Server compared to GitHub Enterprise Cloud?

  • A) Higher per-seat cost
  • B) No support for private repositories
  • C) Feature availability lags behind cloud releases
  • D) Cannot use with Microsoft Entra ID

Question 9​

An enterprise with three organizations wants a unified billing and policy management experience. What entity provides this?

  • A) The first organization created
  • B) The enterprise account
  • C) A billing-specific organization
  • D) GitHub Support

Question 10​

Which GitHub Enterprise Cloud feature is NOT available on GitHub Enterprise Server?

  • A) Repository creation
  • B) Branch protection rules
  • C) Copilot coding agent
  • D) Pull request reviews

Answer Key​

QAnswerExplanation
1CGHE.com provides GitHub-managed hosting with data residency guarantees for specific geographic regions, unlike GHEC which uses GitHub's standard data centers.
2BThe enterprise account is the top-level container that holds organizations, which in turn hold teams and repositories.
3CCopilot Business provides organization-level policy controls and audit logging. Copilot Enterprise adds additional features like knowledge bases.
4CGitHub Enterprise Server is the self-hosted option where organizations deploy GitHub on their own infrastructure.
5CGitHub Enterprise Cloud offers a 30-day free trial with full feature access.
6BOrganizations directly contain teams. Teams are groups of organization members used to manage repository access.
7CInternal visibility allows all members of all organizations within the same enterprise to access the repository.
8CGHES feature releases lag behind GHEC by one or more release cycles, as updates must be packaged and deployed by the organization.
9BThe enterprise account provides unified billing, policy management, identity configuration, and audit logging across all organizations.
10CThe Copilot coding agent requires GitHub-managed infrastructure and is only available on GHEC and GHE.com, not on self-hosted GHES.