Unable to save when granting Row Level Security

[Anonymous]

Hi 

Would like to know if any of you are experiencing issue saving when granting row level security?

I am able to add the user into the row but when I click save, it takes forever to save and an error message throws up

Would need help to resolve this soon. 

Thanks

[Anonymous]

I'm assuming this also affects adding internal users?  Several of us are experiencing the same issue when trying to add internal users.

[negi007]

@Anonymous I hope your issue would been resovled by now as it was a technical glitch and Microsoft has already deployed a fix for it.

Power BI customers with premium capacities using Row Level Security may experience issues while adding external guest users (AAD B2B) to roles with the message, "The Role could not be updated. Please try again later". As a workaround, users can move their workspace to Shared, add the external guest user, then move it back to the capacity. Engineers have identified the issue and a fix is expected to be deployed by end-of-day 02/20/2021

[Anonymous]

Hi negi007

I believe the issue is still there. I tried it awhile ago and the error message is still there. 

[v-jingzhang]

Hi @Anonymous 

There is an issue with premium capacities using Row Level Security. You may try the suggested workaround below. Support | Microsoft Power BI

Regards,

Jing

[Anonymous]

Hi Jing

Thank you for the reply. 

Could you share how I can move the workspace to shared and then move it back to the original workspace?

Apologies if its a stupid question

Thanks

[v-jingzhang · Accepted solution]

@Anonymous You can switch that in workspace settings > Premium > Premium capacity.

[Anonymous]

Hi JingZhang 

Thank you for the work around! Have accepted it as a solution.

[Anonymous]

Hi  @Anonymous 

Are you using Power BI premium capacity workspace? If yes, then please check below support URL in the awareness section.

https://powerbi.microsoft.com/en-us/support/

This is a global issue and will get fixed on 19 Jan 2021. You can try the workaround suggested.

Thanks,
Rahul