Feb 07 2017 04:09 AM
Feb 07 2017 04:09 AM
It seems that the hide membership option we had for Office 365 Groups is not working / available: http://www.michev.info/Blog/Post/1314/you-can-now-hide-group-membership-for-modern-groups-in-office-... any idea? cc @Vasil Michev @Tony Redmond
Feb 07 2017 06:11 AM
We discussed this at Ignite and at that time we said that hidden group membership does work but it's imperfect - the group has to be private, etc. That's logical when you think of it because there's no point in having a public group with hidden members. I think a couple of other flaws were in the mix too that Microsoft was looking at fixing too.
Feb 07 2017 06:36 AM
Feb 07 2017 06:44 AM
Feb 07 2017 09:56 AM - edited Feb 07 2017 09:57 AM
Interesting, on the EN page for Set-UnifiedGroup it lists it but with a description of "This parameter is reserved for internal Microsoft use."
I also no longer see it available in my tenant. I would guess this aligns with the upcoming
Feb 07 2017 10:56 AM
I can confirm the parameter is gone for me too. Or maybe the whole hidden group membership story is just a thing I made up and made you believe :p
Feb 14 2017 10:13 AMSolution
I asked the question and here's the situation.
If you want to hide the membership of a group, use PowerShell to create the group and specify the HiddenGroupMembershipEnabled switch as the New-UnifiedGroup cmdlet still supports it. However, because Set-UnifiedGroup does not (it will again in the future), you cannot change the hidden membership status again. That is, until Microsoft updates Set-UnifiedGroup...
Jan 09 2018 12:00 PM
I ran the following command and was still able to see the group members:
New-UnifiedGroup -DisplayName "Company All" -HiddenGroupMembershipEnabled:$true -Alias Company.All -PrimarySmtpAddress "Company@gitbit.org" -Name "Company All" -ConvertClosedDlToPrivateGroup
Maybe I missed a parameter but it didn't work for me.
I ended up creating a dynamic distribution group and hiding the actual distribution group:
The user's can then send to the new dynamic distribution group.
Jan 09 2018 12:13 PM - edited Jan 09 2018 02:16 PM
I just created a new group with PowerShell and set the parameter... But I also set the group to be Private.
I suspect that the access type is the key because if you attempt to set the group to public, you get an error saying that a group with hidden membership must be private.
Did you really use the parameters that you quoted? I just tried them and PowerShell flagged a "property set cannot be resolved using the specified named parameters" error.
Jan 12 2018 04:16 PM
Sorry I must have copied the wrong command. I just ran the following command:
New-UnifiedGroup -DisplayName "dev01" -Alias dev01 -HiddenGroupMembershipEnabled -AccessType Private
The list can be expanded in Outlook. I'm not worried about it. We created dynamic groups.
Jan 13 2018 02:16 AM
Did you check with the account who created the group or an account that is not a member of the group?
Group members can see the membership. The account that creates a group is automatically a member and can therefore see the membership. People who are not a member cannot.
Dynamic groups cost extra because they need AAD premium licenses. Hence the reason why people like to avoid this feature. https://www.petri.com/microsoft-clarifies-premium-features-office-365-groups