Bad Request: Signing In a Web App registered on Azure Portal

[nka]

Hi, I have trouble signing in to my web app that embeds a Power BI report. The situation is as follows.

I have a user A who exists in two directories B and C on Azure Active Directory. I registered my web app, which is a slight modification of the C# sample app of Power BI Embedded REST Client, using Power BI App Registration Tool with this user A to the directly B. User A can signin to this app and it works without any problem.

However, I want to use this app in the directly C due to the need for integration with other apps in the directly. Therefore, I registered the same app to the directly C on the Azure Portal. I followed the instructions on this page and believe I completed the described configurations. Yet, user A cannot signin to this app and receives the following message:

Sorry, but we’re having trouble signing you in. We received a bad request.

The directly B has a domain with onmicrosoft.com while C does not. When I used the registration tool, the app was automatically added to the directly B. What else am I missing for the app to work in the directly C? Please let me know if more details are necessary to identify the cause of this.

Thank you for your help!

[Eric_Zhang]

---

@nka wrote:

Hi, I have trouble signing in to my web app that embeds a Power BI report. The situation is as follows.

I have a user A who exists in two directories B and C on Azure Active Directory. I registered my web app, which is a slight modification of the C# sample app of Power BI Embedded REST Client, using Power BI App Registration Tool with this user A to the directly B. User A can signin to this app and it works without any problem.

However, I want to use this app in the directly C due to the need for integration with other apps in the directly. Therefore, I registered the same app to the directly C on the Azure Portal. I followed the instructions on this page and believe I completed the described configurations. Yet, user A cannot signin to this app and receives the following message:

Sorry, but we’re having trouble signing you in. We received a bad request.

The directly B has a domain with onmicrosoft.com while C does not. When I used the registration tool, the app was automatically added to the directly B. What else am I missing for the app to work in the directly C? Please let me know if more details are necessary to identify the cause of this.

Thank you for your help!

---

@nka

I think your problem is "How one Azure AD app registered in one AAD can work in another AAD", which is more Azure AD related. I suggest you post in the dedicated Azure AD forum, as there're more experts and you'll get more proper response there.

[nka]

Thank you @Eric_Zhang! I will check Azure AD Forum as you suggested.