Azure API Powerapps connection suddenly not working anymore - Invalid CORS request

(0) Share

Report

Posted on by hermans25

Hello.,

Without any change to the API connector, my Powerapp is not working anymore:

It comes back with a 403 message

Status: Forbidden (403)

Body: Invalid CORS request

Does anybody have a possible solution?

Is this a Powerapps or Azure API management problem?

(the API itself works fine, outside Powerapps..)

thanks

Erik

Categories:

Building Power Apps

All responses (5)

Answers (1)

Sort by

Verified answer

v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @hermans25 ,

Could you please share a bit more the error message within your app?

Do you create a custom connector based on your Azure API within your PowerApps?

Based on the error message that you provided, I think you have faced a 403 forbidden error within the request you sent from your app.

Please check if you have sent a proper/valid request from your app (check if you have specified a valid request within your custom connector action). In addition, also please check if you have enough permission to access the URL request you sent from your app.

Please consider take a try to re-create a new custom connector based on your Azure API within your PowerApps, then specify a valid requst within the custom connector action, then check if the issue is solved.

More details about customizing a connector within PowerApps, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/register-custom-api

Best regards,
hermans25 22 on at

Like
a
(0)

Report
Copy link

Link copied!

Dear support team,

Indeed I create a custom connector as described in https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/register-custom-api .

Already at testing the connector I get the error message "Invalid CORS request".
Althoug we did not change anything on the API side (Spring) , as well in Azure API management, this error suddenly occurred.
Re-creating the custom connector and connections (several times) did not solve the problem.
Since I can test the API with a request directly from the web-browser and since my Powerapps request was formerly also working, I am quite sure it is a "valid request".

Hereby the screen shots of the error message.

Hopefully, you can help ? did something change in Powerapps itself?

thanks
Erik

I have all permission rights (key) to access the API, and in a webbrowser, all direct links with the API are working fine.
hermans25 22 on at

Like
a
(0)

Report
Copy link

Link copied!

PS. strange is that the published version of the Powerapp (in Production) is still working fine.
So it seems something changed on Friday February 22....
hermans25 22 on at

Like
a
(0)

Report
Copy link

Link copied!

Problem has been solved. It seemed an authorization issue on the API side.
Bino 2 on at

Like
a
(0)

Report
Copy link

Link copied!

What authorization issues?