Forum Discussion
Announcing Office 365 Groups + Team Sites integration!
MicrosoftIt's still being rolled out, thanks for your patience. Until then see this demo I gave this week: https://www.youtube.com/watch?v=JR9KJq_5BP8&feature=youtu.be
One thing I'm not sure on is when this comes online does it mean there is now no difference between a Team site created by a Group and one created within SharePoint? Would all the navigation options etc be the same.
Also is a normal intranet site meerly a public group without a fixed list of members?
- cfiessinger
from our deck last week at Ignite
From all the descriptions I've read, I'd say yes, a group has a site, and site has a group. Both should look the same, if created after the release of the update.
I'm not sure about existing team sites/groups.
Also I'm not quite sure what that means for the root site collection (https://tenantname.sharepoint.com) that's also based on the teamsite template I think.
In theory the group memberships (owner/members) should be the existing site memberships sitename owner/member of a teamsite. Visitors group does not appear to be used yet by groups.
Therefore I'm uncertain if the root site collection, that might already have custom permissions (e.g. everyone read), suddenly gets a group in AAD.
At Ignite I think I saw a demo where you can opt out of the Group part when you add a Team site.
The concern with this is permissions. Curently our exiting team sites are based largley on AD security groups to determine access levels.
For the same effect with Group memberships would we not need dynamic groups, which is an Azure AD premium feature we don't have?
The ability to control permissions on the Group SharePoint site separate from the Group membership will still be available.
- Existing team sites will receive updates such as modern pages, home page and so on but they won't receive a group...same happens with the root site collection...this for existing tenants. For new tenants, I would like to know what Microsoft has to say :-)
