What is the GitHub Enterprise 'Managed Accounts and Directory Sync' approach for SAML enterprises that don't use EMU?
Select an answer to reveal the explanation.
Short Explanation and Infographic
In non-EMU SAML enterprises, users link their existing personal GitHub accounts to the enterprise via SSO. The personal account stays theirs — it can still be used outside the enterprise. The IdP just gates access to org resources.
Full explanation below image
Full Explanation
In a GitHub Enterprise Cloud organization with SAML SSO that is NOT using Enterprise Managed Users (EMU), members use their personal GitHub accounts linked to the enterprise's IdP identity. The model: (1) Users have personal GitHub accounts they created themselves (or joined GitHub.com with). (2) When they first access the organization, they authenticate via SAML and their GitHub account becomes linked to their IdP identity. (3) The personal account can still be used for personal projects, open source contributions, and other organizations. (4) Organization resources are protected by SAML: without a valid SAML session, the user cannot access private org repos. This contrasts with EMU where accounts are entirely controlled by the IdP and cannot interact with GitHub outside the enterprise. SCIM can still be used for provisioning/deprovisioning in non-EMU enterprises.