Answered

HTTP 403 (forbidden) if using a custom connector

(0) Share

Report

Posted on by Nolock

Hello folks,

I've created a custom connector which uses the Power BI REST API via OAuth2 (https://www.mssqltips.com/sqlservertip/5976/refresh-power-bi-dataset-from-azure-data-factory--part-1/). I'm able to test the connector in the UI successfully. The response comes in 1-2 seconds.

But if I create a flow using this connector, it takes about 30 seconds to run and ends with HTTP 403 Forbidden.

I created the connector a week ago and I also used it successfully. Then our Power Platform admin created environments for our projects and the custom connector stopped working in my flow. It doesn't matter which environment I use - it doesn't work in any of them. If I recreate the custom connector and the flow with Logic Apps, it works. It means the problem came with the introduction of environments.

I use the Power Apps Plan 2 license.

Do you have any idea what I should try?

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (1)

Sort by

v-litu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Nolock,

What's the license of Power Automate? If they are a free trial, they could not use the custom connector:

https://asia.flow.microsoft.com/en-us/pricing/

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Nolock 8 on at

Like (0)

Report
Copy link

Link copied!

Hi @v-litu-msft,
I have the license Microsoft Power Automate Plan 1. Should I remove the Trial licenses?

Was this reply helpful? Yes No
Verified answer

v-litu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Nolock,

It seems like your license has no problem. There's no need to remove the Trial licenses.

I assume the problem is caused by the environment when you create the custom connector, because of DLP (Data loss prevention), there are some limitations between different environments. The fact that environments are an isolation boundary means that you can never have resources that reference resources across environments. For example, you may not create a custom connector in one environment and then create a flow that uses that custom connector in a different environment.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No