What did GitHub actually announce?
A new authentication capability, in preview, with Microsoft Entra ID as the only supported identity provider at launch. That’s the confirmed core of it. I’ll be blunt: the source material on this is thin, and I’m not going to pad it with a mechanism GitHub hasn’t described. If someone tells you it’s definitely OIDC, or definitely SAML, or definitely a passkey play, ask them where GitHub said so. The interesting fact isn’t the protocol. It’s the guest list, one IdP, everyone else waits.
Why is Entra ID the only IdP that works?
Because that’s how previews go, and because Microsoft and GitHub share a corporate parent, so the integration path is short and the incentives point the same direction. Nothing sinister. Vendors ship to the platform they can test fastest, and a preview with one IdP is a preview with one support matrix. The honest read: Entra-first signals partnership priority, not a permanent exclusion.
Does this apply to GitHub Enterprise Cloud, Server, or both?
Unconfirmed from what’s been published, and I won’t guess. This matters more than it sounds. Cloud and Server have historically diverged on authentication features by months or longer, and Server admins get burned every time they assume parity. Until GitHub states the scope explicitly, treat it as Cloud-only in your planning and be pleasantly surprised if Server shows up. Verify against GitHub’s own changelog before you promise anyone a date.
Where do I configure this in the Entra admin center?
If your GitHub Enterprise integration already lives in Entra, you’ll find it where it always has: Entra admin center → Identity → Applications → Enterprise applications, then your GitHub app, under Single sign-on and Provisioning. Any new preview toggle will surface there or in GitHub’s enterprise settings, not in some novel blade. Don’t go hunting for a new menu that the marketing implies exists. Before you touch anything, take inventory of what’s currently wired up:
Export that, review it, and only then decide what changes. Nobody flips SSO settings straight off a live query into production, a preview least of all.
When do Okta, Google Workspace, and the others get support?
Not disclosed. I have no timeline and I’m not inventing one, and neither should the account rep who’s pitching you a migration. “Coming soon” is not a roadmap. If your shop runs Okta or Google as the primary IdP, this feature does not exist for you today, full stop. Plan as if the wait is long.
Should I turn it on right now?
In production? No. Previews carry no SLA, features get reworked or pulled, and configuration you build today can break on GA. In a test tenant against a non-critical GitHub org, absolutely, that’s the whole point of being first, and Entra shops genuinely do get a head start here. Kick the tyres, document what breaks, keep your existing SSO path intact as the fallback.
What’s the thing that bites in six months?
Configuration drift between the preview and GA. Whatever you stand up now may need re-doing when GitHub finalises the design, and if you’ve quietly made this the only login path for a team, GA day becomes an outage. The multi-IdP problem bites sooner: build any process assuming Entra-only auth and you’ve just made your GitHub estate impossible to migrate off Entra without a rebuild. First-mover advantage is real. So is first-mover cleanup. Enjoy the preview, just don’t marry it.
