Prompt
What should I use to support Azure AD and Google Workspace login?
Latest observation
Oct 6, 2026
OpenAI APIWeb search: off
If you want to support both Azure AD (Microsoft Entra ID) and Google Workspace login, the usual choice is:
Use OpenID Connect (OIDC) for authentication
- It’s the modern standard for “Sign in with Microsoft” and “Sign in with Google.”
- Both Azure AD and Google Workspace support it well.
- Best choice if your app is a web app, SPA, or mobile app and you want user login.
Use SAML only if you need enterprise SSO for older/legacy setups
- Many companies still use SAML with Azure AD and Google Workspace.
- Good for B2B enterprise integrations, but more complex than OIDC.
If you want one auth layer that handles both
Consider an identity platform such as:
- Auth0
- Okta
- Microsoft Entra External ID / Azure AD B2C
- Firebase Authentication (for simpler consumer-style login)
- Keycloak (self-hosted)
These can broker login to both Azure AD and Google Workspace via OIDC/SAML and simplify user management.
Recommendation
- For new applications: use OIDC
- For enterprise SSO compatibility: support OIDC + SAML
- If you want to avoid integrating each provider directly: use an identity broker like Auth0 or Keycloak
If you tell me your app type (SPA, mobile, backend web app, B2B SaaS), I can suggest the best exact setup.