Forum Discussion
Turning off email notifications for Office 365 Groups
We need to start using "unified groups" in Office 365/Azure AD for an intranet project that uses Azure AD as the identitiy provider. We want communication to stay in the platform, and what we don't w...
Thanks for that Doc link - it's very informative. But... I think you'll find that if you use the New-UnifiedGroup command it doesn't actually create an associated Sharepoint Teamsite.
As evident by the 24 new groups I had and 0 new sites.
I ended up having to delete the groups and recreate them using Microsoft 365 Admin Center, then running my Set-UnifiedGroup PowerShell script to 'silence' all the groups. The SP sites now exist and are linked to the groups as expected.
For what it's worth, here's a quick Google search on the topic https://www.google.com/search?client=opera&q=new-unifiedgroup+does+not+create+sharepoint+site&sourceid=opera&ie=UTF-8&oe=UTF-8
As evident by the 24 new groups I had and 0 new sites.
I ended up having to delete the groups and recreate them using Microsoft 365 Admin Center, then running my Set-UnifiedGroup PowerShell script to 'silence' all the groups. The SP sites now exist and are linked to the groups as expected.
For what it's worth, here's a quick Google search on the topic https://www.google.com/search?client=opera&q=new-unifiedgroup+does+not+create+sharepoint+site&sourceid=opera&ie=UTF-8&oe=UTF-8
rpdodds *Updated* I noticed this https://github.com/MicrosoftDocs/office-docs-powershell/issues/3765 and I suppose it's what you experienced as well. But this should be able to work and I believe that either the associated services had not been fully provisioned, that is synchronized completely, or it could be a thing where one needs to actually access a service within the newly created group for it to populate. So it's all there, but could be "hidden". We have the process automated using Microsoft Graph.
