Is anyone seeing the tis behavior:
Adding Azure AD group as SPO Site Collection administrator using group name and group SID creates two different users in the SPO site membership. Is it A bug?
Set-spouser -site $url -LoginName "c:0-.f|rolemanager|$($GroupSID)" -IsSiteCollectionAdmin $true
Set-spouser -site $url -LoginName "c:0-.f|rolemanager|$($GroupGroupName)" -IsSiteCollectionAdmin $true
The group added with just a group name does not have SID assisted with it (Looking at the group Details) and provides no access to any group members:
The group created with SID provides access to group members fine:
Looks like a bug to me. Any body see the similar behavior? The Set-spouser -site $url -LoginName "c:0-.f|rolemanager|$($GroupSID)" -IsSiteCollectionAdmin $true should fail and give an error since it is misleading by adding a group without membership!