Forum Discussion
External user experiencing the Owl error while attempting to access the guest tenant
- 1 year ago
Hi Bhaskar_D ,
Thank you for confirming the steps you've taken so far. This issue might be related to recent updates in tenant policies, authentication settings, or user permissions. Please follow these additional troubleshooting steps.
- Guest user tokens can sometimes expire or become invalid. Try removing the user from Azure AD and then re-inviting them to reset any stale authentication tokens.
- In Azure AD, navigate to External Identities Cross-tenant access settings and ensure that B2B collaboration is properly configured, and the guest tenant is allowed.
- Check if any Conditional Access Policies have been updated recently that might be blocking external users. If so, try temporarily disabling them for testing purposes.
If none of these steps resolve the issue, please consider raising a support ticket for further assistance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Regards,
Yugandhar.
Hi Bhaskar_D ,
Thank you for reaching out to the Microsoft Fabric Community. You've already taken several important steps, including adding the external user as a guest in AAD and enabling relevant settings. However, the issue persists.
Here are a few additional steps to try.
- Confirm that the external user's email and credentials are correct and match those used to add them as a guest.
- Ask the user to clear their browser cache and cookies, then attempt to access the guest tenant again. Suggest using a different browser or device to determine if the issue is browser specific.
- Ensure that the guest tenant settings permit external users to access content. You may need to adjust additional settings in the guest tenant's admin portal.
- Advise the user to try accessing the guest tenant using InPrivate or Incognito mode to rule out any browser-related issues.
- Sometimes, re-establishing the connection can resolve internal authentication glitches. Try disconnecting and reconnecting the data warehouse in Fabric.
Once you've reviewed the information. If my response solved your query, please mark it as the Accepted solution to help others find it easily.
And if my answer was helpful, I'd really appreciate a 'Kudos'.