Multi-tenant Microsoft Entra ID (Azure AD) OIDC SSO for CSM customers – support for /organizations ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
13m ago
Hello community,
We are implementing SSO for our CSM Customer Portal using OpenID Connect (OIDC) with Microsoft Entra ID (Azure AD) through Multi-Provider SSO.
Goal
- One multi-tenant app registration in our Entra tenant (“Accounts in any organizational directory”).
- Each customer’s admin grants admin consent to the app in their own tenant.
- Customer users sign in to our portal with their own corporate credentials (their own tenant, their own MFA).
- ServiceNow should identify which tenant the login comes from and match the user to the correct customer_contact / customer_account.
- No JIT provisioning: contacts are pre-created.
What we tried
Following the multi-tenant guidance from Microsoft, we configured the OIDC Provider Configuration with:
- OIDC Metadata URL: https://login.microsoftonline.com/organizations/v2.0/.well-known/openid-configuration
- Auth URL / Token URL: https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize and /token
- Issuer URI: https://login.microsoftonline.com/{tenantid}/v2.0
Authentication at Microsoft succeeds, but the login fails in ServiceNow with:
Cannot find oauth_oidc_entity for issuer https://login.microsoftonline.com/<actual-tenant-id>/v2.0 with any of the following client_ids: <client-id> OIDC Request - No user found.
Our understanding is that ServiceNow compares the token’s iss claim literally with the issuer from the metadata document, and does not substitute the {tenantid} placeholder that Microsoft publishes for the multi-tenant endpoints.
What works today (workaround)
If we point the Metadata URL, Issuer, Auth URL and Token URL to a specific tenant ID, login works. This means creating one Identity Provider per customer tenant (Provider Configuration + OAuth OIDC Entity + Identity Provider), all sharing the same Client ID and secret, and setting sso_source on each customer account.
This works and isolates tenants well, but it requires manual configuration for every new customer and does not scale for a large number of customers.
Questions
- Does ServiceNow currently support multi-tenant Entra ID OIDC (/organizations or /common) with dynamic issuer validation (for example, accepting https://login.microsoftonline.com/{tenantid}/v2.0 and validating the tid claim against an allow-list)? Is there a property or a newer release that enables this?
- Is it supported and upgrade-safe to customize the OIDC flow through the MultiSSO_OIDC_custom Script Include (which extends MultiSSO_OIDC_internal) to validate the ID token ourselves (signature via JWKS, aud, iss pattern, tid allow-list) and then locate the contact?
- What architecture do you recommend for CSM customers coming from many different Entra tenants? For example:
- one Identity Provider per tenant (with automated onboarding);
- an identity broker (Entra External ID / Azure AD B2C) so ServiceNow sees a single issuer;
- inviting customer users as B2B guests into our tenant;
- another approach?
- If one IdP per tenant is the recommended approach, what is the best way to route users to the correct IdP on the portal login page without one button per customer (identifier-first login based on the email / sso_source)?
- Is this a known limitation, and is it on the roadmap?
Any official guidance, documentation or real-world experience would be greatly appreciated.
Thank you!