Custom Connector Redirect Url not generated

(1) Share

Report

Posted on by Community Power Pla...

Greetings all,

i'm hoping it is something that I'm doing incorrect and not a problem with Power Apps.

I have created a custom connector and have set up a service principal for OAuth 2.0 usage.

When applying the security details to the Security tab, I enter all the relevant information, clientId, secret, resource url and scope then I Create the Connector.

At this stage the Redirect URL should get generated, something like: https://global.consent.azure-apim.net/redirect ,

This however does not happen. The Redirect URL is not being updated. I have tried performing this a number of times yet get same results.

Any Ideas anyone ?

Categories:

Governance & administering

I have the same question (0)

All responses (8)

Answers (1)

v-xida-msft on at

Like (0)

Report

Hi @Anonymous ,

The "Redirect Url" would be generated only when you typed the required Authentication Info and click "Create connector" button to save your custom connector.

Based on the issue that you mentioned, I have made a test, and the issue is confirmed on my side. I think this issue is related to PowerApps Custom Connector. Thanks for your feedback.

I would post this issue to my Product Team, if this issue is solved, I would reply here.

Best regards,

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Same here. I cannot create a custom connector even though I followed the exact same instruction listed in this link - https://community.powerbi.com/t5/Community-Blog/Refresh-Power-BI-dataset-with-Microsoft-Flow-by-Konstantinos/ba-p/622941

Was this reply helpful? Yes No
anujdmehta 4 on at

Like (1)

Report

Hi @Anonymous @Anonymous @v-xida-msft ,

I have been seeing this issue for the last few days and was frustrating to know what was working isnt working anymore. Anyways, i referred to global redirect uri below and it helped me complete the connection. Not an ideal way but works when you add the below url to your redirect uri in AAD.

https://global.consent.azure-apim.net/redirect.

Try this and let me know.

thanks,
AD

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Yes, that worked. Thank you.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Hi all,

unfortunately this solution is not for my problem.

The issue we are facing here as confirmed by @v-xida-msft is that the Redirect Url is not being generated by the platform when we press Create Connector.

As there is no redirect url registered on the connector, when you attempt to use it in a workflow you can not sign in as the service principal, it only allows you to sign in as a user.

I was wondering if we could use the Azure Resource Explorer to view the Custom Connector and update its Redirect Url value.
Does anyone know if this is possible?

Was this reply helpful? Yes No
Jaguke 14 on at

Like (0)

Report

I'm, having the same issue.

Also this is causing issues within my flow when trying to subscribe to a webhook. Within the creation of the connector I can run a test and subscribe succesfully, But when I work the connector in to my flow I get the following response:
"Invalid: Callback URL endpoint domain, expected azure-apim.net." I think it's because the CallbackURL must have the same domain as the RedirectURI.

does anyone know a workaround?

Was this reply helpful? Yes No
Verified answer

v-xida-msft on at

Like (0)

Report

Hi @Anonymous ,

Update -- The "Redirect Url" not generate issue has been fixed. Please consider edit your custom connector, check if the issue is solved.

Also please consider re-create a new custom connector, check if the "Redirect Url" could be generated automatically.

If you have solved you problem, please consider go ahead to click "Accept as Solution" to identify this thread has been solved.

Best regards,

Was this reply helpful? Yes No
hjaf 486 on at

Like (0)

Report

This issue has apparently returned.
Note: the suggestion about creating a new connector is not an option as it would break stuff.

Was this reply helpful? Yes No