Answered

ServiceNow Connector: Works in Flow, Fails in Canvas App (Error 502)

(0) Share

Report

Posted on by AD-11060731-0

Hi everyone,

I am encountering a critical issue with the standard ServiceNow (Premium) connector. The connection is successfully established and works perfectly in Power Automate flows, but it fails immediately when used in a Canvas App.

The Setup:

Connector: ServiceNow (Microsoft Standard/Premium)

Authentication: Basic Authentication

Instance URL: dnbtest.service-now.com (Example)

Context: Canvas App inside a Solution

The Issue: When I call ServiceNow.GetRecords(...) inside the Canvas App, it fails with Error 502.

Crucially, the error message shows that the connector is trying to resolve the wrong hostname. Instead of my configured instance URL, it is trying to reach a default Microsoft placeholder. Error Message: "The remote name could not be resolved: 'powerapps.integration.user.service-now.com'"

(See attached screenshot of the error details)

Troubleshooting: Verified that the exact same Connection Reference works in a Power Automate flow (it retrieves data correctly). Deleted and re-added the datasource in the Canvas App. Verified the Instance URL is the full FQDN. It seems like the Canvas App runtime is failing to pass the configured Instance URL to the gateway, defaulting to powerapps.integration... instead.

Has anyone seen this discrepancy between Flow and Apps before? Is there a way to force the App to respect the Instance URL?

Thanks!

Categories:

Building Power Apps

Connector development

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

MarkRahn 1,351 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @AD-11060731-0

I have not integrated Power Apps with ServiceNow but I thought I would take a look.

If a Flow is working, you might want to look at this article though it is rather old:

https://www.servicenow.com/community/developer-articles/servicenow-integration-with-microsoft-powerapps-and-flow/ta-p/2320111

They use a flow to retrieve the data back to the app. I know it is not ideal.

I did find this post on ServiceNow.com that seems to be the exact issue you are having:

https://www.servicenow.com/community/developer-forum/servicenow-connector-powerapps/td-p/1835110?utm_source=chatgpt.com

The answer from User Ashish was:

All ServiceNow integration should use the local account with required role only.
Local Account or Service Account or Local User all are referring the same.
Please ensure you are following some naming pattern for service accounts [ we are using "svc_" prefix ] and grant only minimum required role [ no admin role ]
you can create svc_powerapp and grant itil role for testing.
Check, what data/table the PowerApp is looking for based on that, grant access [ role ].

This community is supported by individuals freely devoting their time to answer questions and provide support. They do it to let you know you are not alone. This is a community.

If someone has been able to answer your questions or solve your problem, please click Does this answer your question. This will help others who have the same question find a solution quickly via the forum search.

If someone was able to provide you with more information that moved you closer to a solution, throw them a Like. It might make their day. 😊

Thanks
-Mark

Was this reply helpful? Yes No
trice602 16,016 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Helpful! Thanks for the response here Mark! Many thanks! 💯💯💯💯💯

Was this reply helpful? Yes No