[Bug] Sharing to Distribution Groups - newly added users are not given access

[alex-potter]

Has anyone else noticed this?  If you add a Distribution Group to a dashboard, you have to reshare it with the DG after adding any users for them to recieve access.  Is this a known bug?  Is there any timeline on getting it to work?

[chrichua]

This should not be the case with the latest update. Can you verify if this is still happening and reply to me? Thanks!

[alex-potter]

Just tested and here is what we got:

We have a dashboard that is shared with a Distribution Group.  We removed a member of the DG to see if they lost access to the dashboard - the user was still able to access the dashboard even though he had been removed from the DG.  After removing the DG and resharing to it from Power BI, the user was unable to access the dashboard. 

Next we added the user back into the DG to see if access is granted after updating the DG.  After adding the user to the DG, we had him test and he was still unable to access the dashboard.  We then removed the DG from Power BI sharing and reshared the dashboard with the DG.  Currently the user is still unable to access that dashboard. 

How long is it supposed to take for changes to a DG to propagate to other services?  Should we be waiting a given amount of time?  As of now it appears to still not be working, but it may be that we aren't allowing DG changes to fully realize.

Thank you,

Alex Potter

[deldersveld]

The default timing for synchronization in Azure AD Connect is three hours. If you make a change locally in AD, wait up to three hours and then try to test in Power BI.

[alex-potter]

If the change is made in something like Forefront Identity Manager 2010 (Microsoft IDWeb) - would it potentially take longer or shorter?

Alex

[deldersveld]

I am not familiar with Forefront so unfortunately cannot say.