Test as role does not work with Single Sign-On (SSO)

Hi nirun00s ,

Thank you for joining us on the Microsoft Fabric Community Forum.

Core reason: Test as role does not work with Single Sign-On (SSO) occurs due to a limitation in Power BI.

• The test as role feature allows developers to simulate Row-Level Security (RLS) to see how specific roles affect data visibility. When SSO is enabled, Power BI uses the real user's identity for data source authentication.
• With SSO enabled, Power BI cannot simulate roles because it always uses the authenticated user’s identity.
• To get seamless SSO connectivity, configure your on-premises data gateway for real-time updates of Power BI reports and dashboards.

         Overview of single sign-on for on-premises data gateways - Power BI | Microsoft Learn.

• With Power BI, you can use Row-Level Security (RLS) to limit data access for certain users. This RLS feature is only effective for users who have Viewer permissions.

         Row-level security (RLS) with Power BI - Microsoft Fabric | Microsoft Learn.

To address your query, please follow the steps outlined below:

1. Identify the application displaying the error message regarding SSO and role testing.
2. Log in to the application and navigate to the section where your dataset is located.
3. Access the settings for your dataset by clicking on the ellipsis (three dots) next to it and selecting "Settings."
4. Look for any options related to Single Sign-On (SSO) in the dataset settings. If there is an option to temporarily disable SSO, consider doing so for testing purposes.
5. If you have the ability, create a test user account that has the role you want to test, ensuring that this user does not have SSO enabled.

Please refer to the official documents below for more details:

Overview of single sign-on for on-premises data gateways - Power BI | Microsoft Learn.

If my answer addressed your query, kindly mark it as the Accepted Solution to assist others.

I'd also be grateful for a 'Kudos' if you found my response useful! 

Hi nirun00s ,

The issue might be related to the authentication method used with your cloud connections. Using Personal Cloud Connect for both sources could be causing conflicts with the role testing functionality.

Please consider switching from Personal Cloud Connect to another authentication option. Ensure that all required permissions are correctly set up for both data sources. 

Could you help us verify your access permissions to ensure everything is in place?

If you need further assistance, please let us know.