Question

An enterprise uses a GitHub Enterprise Cloud with Managed Users (EMU) instance provisioned via SCIM from Azure AD (Entra ID). Two newly hired employees, both named Alex Kim, are being provisioned. The identity provider maps the SCIM userName attribute (derived from each user's email local-part 'alex.kim') to their GitHub handle. The first user provisions successfully as '@alex.kim_acme'. When the second Alex Kim is provisioned, what happens and how should the administrator ensure both users are created correctly?

Accepted Answer

The second provisioning fails or collides because managed usernames must be unique within the enterprise; the admin must ensure the IdP maps a unique SCIM userName (e.g., a distinct email/attribute) so GitHub generates a distinct normalized handle.

Answer

GitHub silently merges both identities into the single '@alex.kim_acme' account since they share the same display name, and no admin action is needed.

Answer

The second user is created automatically as '@alex.kim2_acme' with no configuration change required, because GitHub auto-increments any duplicate managed usernames.

Answer

Provisioning succeeds because managed usernames only need to be unique per organization, not per enterprise, so both can coexist in different orgs.