CORS / XmlHttpRequest issue with embedded Power Automate Flow

(0) Share

Report

Posted on by Lucas001

2,563 Super User 2026 Season 1

Hi everyone,

I really have a strange error.

The error seems persistent when a normal user tries to start the embedded power automate flow.

At first I thought, PowerPages already have the needed CORS Settings as the flow was running fine in our Dev envr. without any issue (UAT was successfull). The flow etc was changed for Prod and embedded the same way. The Flow also runs fine if I use my own user which has no other rights nor priviliges or anything.

I already implemented all CORS Settings and tried different approaches.

Once everything is setup, I still get the error HTTP Status ok not found. What I also found is that the request in my network traces delivers a 404 not found. That entire problem seems weird.

Does anybody know what the issue could be or is there anything what needs to be explicitly enabled for embedded Power Automate Flows inside a PowerPage?

Any help appreciated.

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (2)

Sort by

Fubar 8,499 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Is the url (and id) of the Flow for the correct environment? (in your JS code making the call and also in the Site editor Cloud Flows area)

(there was an issue with moving Power Pages Flows in Solutions that Oliver logged a support ticket for a short while ago)

Was this reply helpful? Yes No
Verified answer

Lucas001 2,563 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @Fubar,

I finally found the issue.

The issue itself is not CORS related as it seem but there is another behaviour which is nowhere documented.

When you want to use a cloud flow the default and provided url is like that:

https://contoso.powerappsportals.com/_api/cloudflow/v1.0/trigger/4d22a1a2-8a67-e681-9985-3f36acfb8ed4

If you now have a custom domain set the url needs to be changed. I really thought Microsoft would have used the default url as it would be intuitive. But the link would need a change to:

https://your.customdomain.com/_api/cloudflow/v1.0/trigger/4d22a1a2-8a67-e681-9985-3f36acfb8ed4

The product team will have a look if that behaviour is intentional and update the docs if needed.

Many thanks anyway.

Was this reply helpful? Yes No
Verified answer

Lucas001 2,563 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

it seems like Microsoft did some changes yesterday and revoked the falsy domain link.

Means it now works without the url. Instead of: https://your.customdomain.com/_api/cloudflow/v1.0/trigger/4d22a1a2-8a67-e681-9985-3f36acfb8ed4 you need to use the usual URL like: /_api/cloudflow/v1.0/trigger/4d22a1a2-8a67-e681-9985-3f36acfb8ed4 which is also mentioned in the sample code on MS learn: https://learn.microsoft.com/en-us/power-pages/configure/cloud-flow-integration#sample-javascript-to-call-a-flow

Hope that helps in case you now get into errors.

Was this reply helpful? Yes No