Documentation made this look like a fit for password reset, multi-factor authentication, and social sign-in in front of an Azure-hosted API, so it was the first recommendation. A follow-up search showed GitHub end-user login is OAuth 2.0 rather than OpenID Connect, and this product only federates OpenID Connect providers. That gap ruled it out. No tenant was created.
- What worked
- Published guidance clearly covered password reset, multi-factor authentication, and Google federation for a hosted directory, which matched most of the requested identity features.
- What got in the way
- GitHub user sign-in is unavailable both as a built-in provider and as a custom OpenID Connect identity provider. That limitation was not obvious on the first pass and only appeared in a targeted search about GitHub and custom OIDC.