ServiceNow connector in Copilot Studio/ Power Automate flows

(0) Share

Report

Posted on by AG-23090640-0 Microsoft Employee

I'm trying to connect the ServiceNow Connector tool in my copilot studio agent using the app URI which already has the table API access to ServiceNow but it is giving me this error:
Failure passed to redirect url. error=access_denied error_description=AADSTS650057: Invalid resource. The client has requested access to a resource which is not listed in the requested permissions in the client's application registration. Client app ID: c26b24aa-7874-4e06-ad55-7d06b1f79b63(PowerPlatform-service-now-Connector). Resource value from request: api://432acbe3-dfea-45c2-93b1-504ce19b5320. Resource app ID: 432acbe3-dfea-45c2-93b1-504ce19b5320. List of valid resources from app registration: . Trace ID: 2fa17b8a-033c-42a8-ac6d-9ed080482c00 Correlation ID: 23659a92-34ea-418b-8d62-d963638eb837 Timestamp: 2026-03-09 10:16:17Z

We want to use the instance name and App ID for authentication and making connection and don't want to use anything else like certificate or ID password. Has anyone used this ServiceNow connector in their studio agent or even any power automate flows before?

Categories:

Copilot Studio skills development

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Karan_Shewale_MSFT Microsoft Employee on at

Like (2)

Report
Copy link

Link copied!
This error indicates a resource/audience mismatch, not a ServiceNow table permission issue.

AADSTS650057 means the built-in Microsoft connector app
PowerPlatform-service-now-Connector (c26b24aa-...) is requesting a token for your custom resource URI api://432acbe3-..., but that resource is not allowed for that client app.

So with the out-of-box ServiceNow connector, using Microsoft Entra ID User Login + custom api://... Resource URI is typically not supported.

What to do:

Use a supported auth path for the built-in ServiceNow connector (native connector configuration, no custom api:// audience).

If you must use your own Entra app/resource URI and OAuth design, create a Custom Connector (full control of OAuth settings/scopes/audience).

If needed, raise a Microsoft support ticket and share the trace/correlation IDs to confirm tenant-specific support status.

References:
ServiceNow - Connectors | Microsoft Learn

Microsoft Entra authentication & authorization error codes - Microsoft identity platform | Microsoft Learn

Custom connectors overview | Microsoft Learn

Create a custom connector for a web API | Microsoft Learn

Use connectors in Copilot Studio agents - Microsoft Copilot Studio | Microsoft Learn

If the provided answer helped resolve your issue, please consider marking it as Accepted. This helps others in the community find the solution more easily.

Thank you!

Karan Shewale

Was this reply helpful? Yes No
Karan_Shewale_MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi, just checking in — has your issue been resolved, or are you still facing any problems?

Was this reply helpful? Yes No