Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I am experiencing some issues after login in a multi-tenant scenario.
Scenario:
- User 1 in Tenant A (Premium per User license in Tenant A)
- Login as User 1 (External Azure AD B2B Guest) in tenant B (Premium per User Workspace), using an URL like
https://app.powerbi.com/home?ctid=4xxxxxxxxxxxxxxxxxxxxxxxxxx6
- Getting first the message "You've selected Microsoft Power BI" - with "You already have a license for Microsoft Power BI"
- Redirect to app.power.bi but getting a looping redirect message with "Preparing Power BI".
I tried to access several links / urls the resources (Reportip) with no success - there is always a redirect starting with the message "Preparing Power BI".
Internal user to the organisation (Power BI Admins) can however access the power BI service in their tenant.
It is currently unpossible to use the service as an external user in my scenario.
I tried it on several browser, after a reboot, and also on several machines - same results.
Any ideas how to fix this? Is it a temporary bug on the service?
Other issues - out of subject, but another issues some user are experiencing in our multi-tenant scenario is the message "Sorry, we couldn't find your app" when accessing an application in an external tenant.
It seems to exist some issues with login on multi-tenant scenarios...
Solved! Go to Solution.
Hi @picander,
I believe we solved the issue, although I still need to figure out exactly why it would be an issue. We noticed a difference between the users in ADD that were able to access the report and the users that ran into this looping crediential issue.
In Azure AD, these external users were either marked as a "Member" or "Guest" user type. The external users that were marked as "Member" seemed to be running into the looping credential issue, but those marked as "Guest" user type in AAD were able to access the report as expected.
We updated the user properties in AAD for the external users marked as "Member", and immidiatly they were able to login successfully and view the report. Not sure exactly what is going on yet that causes the "Member" user type to cause this issue, but it must have something to do with the double tennant... If we find out more details around the cause of this issue, I will update this thread. Thanks!
Hi,
We are exactly in the same scenario. We have added some users from others domain on our tenant
On our PBI platform, access to Guest users has been enabled.
User has been granted access a Power BI app, but when he tries to access it he enters in an endless loop
We have checked that problem only appears for users that has been added to tenant as members. For users added as Guest no problems.
What is the reason of that? How to fix it?
Hi @picander,
I believe we solved the issue, although I still need to figure out exactly why it would be an issue. We noticed a difference between the users in ADD that were able to access the report and the users that ran into this looping crediential issue.
In Azure AD, these external users were either marked as a "Member" or "Guest" user type. The external users that were marked as "Member" seemed to be running into the looping credential issue, but those marked as "Guest" user type in AAD were able to access the report as expected.
We updated the user properties in AAD for the external users marked as "Member", and immidiatly they were able to login successfully and view the report. Not sure exactly what is going on yet that causes the "Member" user type to cause this issue, but it must have something to do with the double tennant... If we find out more details around the cause of this issue, I will update this thread. Thanks!
What does "We updated the user properties in AAD for the external users marked as "Member", exactly mean?
This was indeed the solution we found - without really understanding how it works as well...
Hi!
The issue resolved itself - I presume this was a bug in the service...
The multi-tenant experience in PBI is still terrible. I would advise to use strictly different browsers / profiles per tenant.
Keep us updated if you found the reason for this behaviour!
Hi picander,
I realize this is months down the road from when you first raised this issue, but were you have to solve for this? I am running into the exact same error in our organization today.
Thank you
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.