ServiceNow connector with Microsoft copilot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
User is unable to create a new OIDC (OpenID Connect) configuration in ServiceNow for the Employee Self-Service (ESS) Agent integration.
This is because an existing OIDC configuration is already present in their ServiceNow instance, and it has mismatched redirect URIs and token/claims settings.
These mismatches prevent user from setting up the recommended OAuth 2.0 authentication method required for the Power Platform ServiceNow connector that powers the ESS Agent.
As a result, they cannot properly connect ServiceNow (HRSD/ITSM) to the Microsoft Employee Self-Service AI agent using the secure, Microsoft-recommended Entra ID-based OAuth flow.
What could be the solution to this? can we make changes to the redirect URL on the existing OIDC or can we create a new one?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Buddy,
You can update the redirect URL on an existing OIDC configuration, but its usually not recommended if that configuration is already being used. Changing redirect URIs or token/claims settings can impact any current SSO or integrations tied to it.
The safer approach is to create a new OIDC configuration specifically for the ESS Agent / Power Platform connector. This keeps the existing setup intact and avoids breaking anything that may depend on it.
For OIDC to work, the redirect URI and token settings must match exactly between ServiceNow and the Entra ID app registration. If they dont align the OAuth flow will fail.
So in most cases:
leave the existing OIDC configuration as-is, and
create a new Entra ID app + new OIDC configuration dedicated to the ESS Agent integration.
@amanfaisal9 If help you answer; Please mark Solution Accepted and Thumbs Up
