Required Home Page URL

[mbwseco]

I keep getting the following error, when I try and run the RDL Migration tool.

"AADSTS50011: The redirect URI specified in the request does not match the redirect URIs configured for the application."

If you use the link that is listed on the readme file https://dev.powerbi.com/apps it takes you to the following page:

However, when you click Sign In in takes you back to the main Power BI page:

Because I was not able to use that link to complete the app registration, I used the link at the bottom of the page https://docs.microsoft.com/en-us/power-bi/developer/register-app to try and register the app. This led me to a new app registration link which I was able to get logged into. https://app.powerbi.com/embedsetup

However, it then asks for the following information, which does not match the ReadMe file. The ReadMe file asks for a Native Application Type.

And this is what it asks for in the ReadMe file

You can see that I cannot change the application type from this link https://app.powerbi.com/embedsetup

From there I went into Azure and tried to manually configure the app. I tried both the Native and Web App Application Type, however both require a home page URL. However, there is no documentation on what this URL should be. I tried the Power BI service https://app.powerbi.com/, however, that did not work. I also tried the three default web URLs from the Native App Type and none of those worked either.

Any help would be much appreciated as I have about 150 SSRS reports that I need to migrate that all use shared data sources.

[massyfigini]

@mbwseco did you find a solution for this?

[cnavarrete]

It's hard to believe this is still the case in 2024

[sauvesean]

The Reply URI that you have to add to the app registration is: urn:ietf:wg:oauth:2.0:oob

You can find this in the ElementNameConstants.cs file in this repo.

I added it to a "Mobile and desktop applications" platform type on the app registration after creating the app with https://app.powerbi.com/embedsetup and deleting the platform configuration that it created. I'm not sure if that was needed, but during troubleshooting this problem I had ended up deleting the existing platform and the Mobile and desktop applications worked so I stuck with it.