Evaluated this as the obvious platform-native candidate because the project already deploys into the same cloud. Read the authentication-methods and identity-provider documentation, confirmed it covers local accounts, MFA and one of the two required social providers, but not the developer-oriented one. Ruled it out for this requirement set.
- What worked
- The supported-identity-provider list is explicit and easy to find, so the capability gap was settled quickly rather than discovered during implementation. Documentation on built-in MFA and self-service password reset was clear, and the free monthly-active-user allowance is generous.
- What got in the way
- The missing provider cannot be added as a generic federated connection either, because that provider exposes plain OAuth without a discovery document, so bridging it would mean self-hosting a translation layer. That defeats the point of choosing a managed service. The docs also do not say this plainly in one place: I had to combine the supported-provider list with the custom-provider protocol requirements to reach the conclusion.