Bug Fix: Active Directory group name changes should syncronize to SharePoint Online site Collection
Note: This idea reflected in case# 616031193642732.
Scenario: An AD group is assigned permissions to a SharePoint OL site within a SharePoint Security Group.
Problem: Group name changes in active directory are automatically reflected in O365 after DirSync runs but name changes are not automatically updated in existing SharePoint site collection.
Solution: Ensure changes to AD group names in O365 are automatically updated in the SharePoint OL site collection.
So I change the name in Azure AD but the group names don't update in SharePoint Online when I look to grant permissions. I can search and add the group with the new name but when applied they revert to the old name. Please do something about this.
Simon de Lisle commented
Cannot believe there is not a PowerShell Script to fix this yet.
Kevin Still commented
I renamed a group. The Display Name, and CN are also updated however SharePoint permissions still shows this group as the old name. Very ANNOYING
Issue is still there!!!
How can Microsoft Azure AD not talk nicely with Microsoft SharePoint Online?
William M commented
How can Microsoft Azure AD not talk nicely with Microsoft SharePoint within the same O365 tenant?! Please fix.
apurva mishra commented
Is there any update on this issue, it is a known issue in our environment.
The only solution is to delete the AD group from the SIte Collection and then re-add the AD group to List/Library/SIte.
anyupdate oin this I still ahve names incorrectly named. Makes it very difficult auditing access when the names don't match AD
Any updates on this?
Bart Hoofd commented
If not automatically, please allow for a method to do this manually / scripted. I've tried using the web interface, but it doesn't allow for name changes of Azure AD groups. I tried PowerShell for SharePoint Online, but couldn't find any method of updating the display name of a Azure AD group linked to SharePoint Online.
Anthony Rettig commented
Any solution to this issue?