When comparing Group SCIM to Team Sync for identity management in GitHub Enterprise, which statement is Correct?

Question

Options

• AGroup SCIM requires less initial configuration than Team Sync.
• BTeam Sync supports more identity providers than Group SCIM.
• CTeam Sync provides more automated user deprovisioning than Group SCIM.
• DGroup SCIM enables centralized user and group management through the IdP.

• A
  4% (1)
• C
  8% (2)
• D
  88% (22)

Explanation

Option D is correct because Group SCIM uses the SCIM protocol (System for Cross-domain Identity Management) to give your Identity Provider (IdP) full control over both user provisioning and group membership in GitHub Enterprise - creating, updating, and deprovisioning accounts directly from one central source.

Why the distractors are wrong:

• A is backwards - Group SCIM requires more initial setup (SCIM endpoint configuration, attribute mapping, IdP integration), not less.
• B is also backwards - SCIM is an open standard supported by a wide range of IdPs, whereas Team Sync historically has more limited IdP support (primarily Azure AD and Okta).
• C is wrong because deprovisioning is actually a strength of Group SCIM, not Team Sync. SCIM handles the full user lifecycle including automatic removal; Team Sync focuses narrowly on keeping team membership in sync with IdP groups.

Memory tip: Associate SCIM with the word "centralized" - its full name literally contains "Cross-domain Identity Management," signaling it's the protocol built for managing identities holistically from the IdP. Team Sync = team membership only; Group SCIM = everything (users + groups, end-to-end).

No community discussion yet for this question.