RLS roles empty after deployment

[Anonymous]

Hi there,

We current use a deployment pipeline in Power BI with dev, test and prod. We have a report in dev with row-level security roles configured and members added. When we deploy the report and dataset to the next stage everything seems to be okay, but the row-level security roles are empty and all members have to be assigned again. The roles itself, however, still exists after the deployment.

Does anyone have an idea as to why this is happening and how we can resolve this?

[rubayatyasmin]

Hi, @Anonymous 

The issue you're facing with the row-level security roles not being carried over during the deployment pipeline in Power BI could be caused by a few different reasons.

To resolve the issue, you can try the following steps:

1. Double-check the deployment process: Review the steps involved in your deployment pipeline to see if any steps might be inadvertently excluding the security roles.

2. Export and import roles manually: If the automated deployment is causing issues, try manually exporting the report with the roles from the dev environment and then importing it into the subsequent environments.

3. Verify data source connections: Ensure that the data source connections used for row-level security are valid and accessible in all environments.

4. Use Power BI REST API: If you're using automation scripts or tools for deployment, consider using the Power BI REST API to explicitly manage security roles during the deployment process.

5. Test with a smaller report: Create a smaller test report with row-level security and go through the deployment process to see if the roles are retained. This might help narrow down the issue.

6. Check for Power BI updates: Keep an eye on Power BI updates and documentation to see if there have been any changes or fixes related to row-level security in newer versions.