keith.jenneke
08/31/2026, 7:05 AMkapa.ai
08/31/2026, 7:05 AMuser@tenant-a.com → Azure Entra ID Tenant A
• user@tenant-b.com → Azure Entra ID Tenant B
Each identity provider must have at least one identifier (email domain) registered, and users are routed accordingly at login time. [MOIDC Setup]
Azure-specific configuration When using Azure Entra ID as your OIDC provider, note that Azure uses oid instead of sub for user identification. You'll need to configure customClaimMapping accordingly when registering the provider:
"customClaimMapping": {
"sub": "oid"
}
[MOIDC Configuration]
Setting it up 1. Contact GoodData support to enable the MOIDC feature and provide your current IdP identifiers.
2. Once enabled, use the /api/v1/entities/identityProviders API to register each Azure Entra ID tenant as a separate OIDC provider with its own identifiers (email domains), oauthClientId, oauthClientSecret, and oauthIssuerLocation.
Key limitation Routing is based on email domain, not workspace. Users from a specific email domain will always be authenticated by the same provider regardless of which workspace they access. If you need strict per-workspace isolation at the authentication level, that is not supported by the current design. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups.
👀 Our Support team monitors all messages and will jump in if needed., with interactive elementskeith.jenneke
09/07/2026, 12:41 AMkapa.ai
09/07/2026, 12:41 AM