Unable to Invoke User Data Function From Power Automate - 403 Forbidden

[JeffreyGonzalez]

I am trying to invoke a UDF from a power automate cloud flow. 

I have generated/registered an application in entra with the proper permissions indicated in the following documentation: https://learn.microsoft.com/en-us/fabric/data-engineering/user-data-functions/tutorial-invoke-from-p...

Namely, the application has been granted GraphQLApi.Execute.All permissions. 

I have tested this with the UDF that I plan to use as well as a simpler UDF that just returns text. 

The Registered application has contributor access in the workspace and also has execute permissions on the specific UDFs that I have tested. 

I generate a token with the client id and client secret against the https://login.microsoftonline.com/<removed>/oauth2/v2.0/token endpoint sucessfully with a scope of "https://analysis.windows.net/powerbi/api/.default"

Upon using the token generated from the above post request, I make a post request to the endpoint provided by the UDF invokation code with my bearer token and receive a '403 Forbidden' error. 

Is there anything that I am missing in terms of permissions, scopes, etc that is inhibiting me from making this function call? 

I have been able to recreate the error in Postman with the same steps listed above. 

[v-nmadadi-msft]

Hi @JeffreyGonzalez 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @JeffreyGonzalez 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[nielsvdc]

Hi @JeffreyGonzalez,

First you might want to check the UDF error codes list. A "403 Forbidden" error might not what you think and is according to the list that the response was too large and the invocation failed. So authentication might be correct, but your response output might be over 30MB. Check the UDF service limits list for the response size limit.

If this does not help, you can try to add the Item.Execute.All permission to the service principal.

Hope this helps. If so, please give a Kudos 👍 and mark as Accepted Solution ✔️.

Niels