Forum Discussion
Office Group as Security Group
Office 365 Groups can't be used in the same way as an AAD security group. For example, you cannot use an Office 365 Group as the basis for the RBAC permissions as deployed inside Exchange Online. But SharePoint Online has special code to allow it to use Office 365 Groups to manage membership for a site collection through the groups that you mention (a surplus of groups). These groups are a construct specific to SharePoint and do not appear when you look at Groups through the Office 365 Admin Center as they are not AAD groups. I guess to make SharePoint work, there's an internal mapping between the membership links exposed in Office 365 Groups to the owner and member groups for the site collection.
Office 365 Groups can't be used in the same way as an AAD security group. For example, you cannot use an Office 365 Group as the basis for the RBAC permissions as deployed inside Exchange Online. But SharePoint Online has special code to allow it to use Office 365 Groups to manage membership for a site collection through the groups that you mention (a surplus of groups). These groups are a construct specific to SharePoint and do not appear when you look at Groups through the Office 365 Admin Center as they are not AAD groups. I guess to make SharePoint work, there's an internal mapping between the membership links exposed in Office 365 Groups to the owner and member groups for the site collection.
The different group types are such a clossal pain, there are three types and it seems like every app is allowed to randomly pick 1 or 2 of these not to support.
For example
- Skype call queues will use Unified or Mail Enabled Security Groups, but not Security Groups.
- PowerApps only seems to like Mail Enabled Security Groups
- Flow can update the members of Security Groups, Unified groups but not Mail Enabled Security Groups
It's time there was only one type of group, and collaboration features were options on each.
Not to mention the places where you can select a distribution group from a picker, but not an Office 365 group...
Is there a work around to this limitation? Maybe a dynamic security group that auto updates itself based on changes to Office 365 group?
