GitHub Enterprise Managed Users (EMU): fix "Could not get verified email for GitHub user"

GitHub Enterprise Managed Users (EMU): fix “Could not get verified email for GitHub user”

If users start seeing this error after a GitHub Enterprise Managed Users (EMU) migration, Sourcegraph was able to authenticate with GitHub but GitHub did not return a verified email address that Sourcegraph could match to the user's account.

Could not get verified email for GitHub user. Check that your GitHub account has a verified email that matches one of your Sourcegraph verified emails.

Why this happens

• Sourcegraph uses verified email addresses to match GitHub identities to Sourcegraph accounts.

• After an EMU rollout, the managed GitHub email may exist but not yet be marked Verified, or it may not match any verified email on the Sourcegraph side.

Fix it

1. In GitHub, open Settings > Emails for the affected user.

2. Confirm the managed email address is present and marked Verified.

3. Make sure that same address matches one of the user's verified email addresses in Sourcegraph.

4. Try signing in to Sourcegraph again.

For GitHub admins

• In EMU environments, email verification is often handled through directory sync or enterprise identity settings rather than by the end user.

• If users cannot change or verify the address themselves, have your GitHub admins confirm the managed email is being provisioned as verified.

If it still fails

• Sign out of both Sourcegraph and GitHub, then retry the login flow.

• Confirm the user is signing in with the expected GitHub identity after the EMU migration.

• If the verified email on GitHub changed, update the Sourcegraph account so the verified addresses match.

For background on how Sourcegraph uses verified emails, see authentication in Sourcegraph and email verification.