cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Anonymous
Not applicable

Error while trying to connect with Azure App using Custom Connector

Hi All,

I have registered the a new App in Azure.

Then I have created the custom connector in PowerApps and tried to connect with the Azure App. I have followed the steps in link https://github.com/bguidinger/Xrm.ReportScheduler/blob/master/docs/INSTALL.md

 

When I try to connect with App, it works fine from the "Default Environment".

But, when I try the same at "Prodution Environment", I get the error that "The reply url specified in the request does not match the reply urls configured for the application: '00000000000000000000000000'" as in attached image.
Same for Development Environment as well.

 

Does anyone face similar problem? Any help would be much appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Power Apps
Power Apps


@Anonymous wrote:

But, when I try the same at "Prodution Environment", I get the error that "The reply url specified in the request does not match the reply urls configured for the application: '00000000000000000000000000'" as in attached image.


 

Hi @Anonymous , when you receive that error, it is because the reply URL that you have set up is wrong either in the connector or in its app registration. Can you check your settings and make sure it's consistent?

 

Else, can you share more information about your setup?

View solution in original post

2 REPLIES 2
Highlighted
Power Apps
Power Apps


@Anonymous wrote:

But, when I try the same at "Prodution Environment", I get the error that "The reply url specified in the request does not match the reply urls configured for the application: '00000000000000000000000000'" as in attached image.


 

Hi @Anonymous , when you receive that error, it is because the reply URL that you have set up is wrong either in the connector or in its app registration. Can you check your settings and make sure it's consistent?

 

Else, can you share more information about your setup?

View solution in original post

Highlighted
Anonymous
Not applicable

@Mr-Dang-MSFT  Thanks for your reply.

I am able to resolve the issue. The reply url that I added (https://msmanaged-na.consent.azure-apim.net/redirect) in Azure was region specific which is for US region. But, when I replaced it with global consent url(https://global.consent.azure-apim.net/redirect), that started working.

However, I am still not clear as how it worked in the default environment with the US region URL.

If anyone is aware of difference between these two URL's, then please share your thoughts on it. What is purpose of region specific URL and global consent URL?

Thanks.

 

 

 

 

 

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (8,722)