SOLVED

Attempt to groupify a classic SharePoint Team site programmatically fails

%3CLINGO-SUB%20id%3D%22lingo-sub-183701%22%20slang%3D%22en-US%22%3EAttempt%20to%20groupify%20a%20classic%20SharePoint%20Team%20site%20programmatically%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183701%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20attempting%20to%20groupify%20a%20single%20classic%20team%20site%20using%20the%20article%20posted%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Ftransform%2Fmodernize-connect-to-office365-group%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EConnect%20to%20an%20Office%20365%20Group%3C%2FA%3E%26nbsp%3Band%20following%20the%202nd%20method%20which%20provides%20sample%20scripts%20to%20do%20it%20programmatically%20using%20PowerShell.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20first%20PS%20script%20runs%20and%20checks%20for%20blockers%2C%20etc.%2C%20and%20the%20target%20site%20passes%20with%20no%20issues.%20Then%2C%20when%20I%20run%20the%20second%20script%20(updating%20the%20variables%20and%20sections%20appropriately)%2C%26nbsp%3Bit%20fails%20to%20create%20a%20new%20group%20and%20attach%20it%20to%20the%20updated%20Team%20Site.%20I'm%20assuming%20this%20is%20what's%20going%20wrong%2C%20because%20I%20notice%20that%20in%20the%20log%2Foutput%2C%20the%20ID%20of%20the%20group%20that%20it's%20trying%20to%20add%20to%20is%20%2200000000-0000-0000-0000-000000000000%22%20(i.e.%2C%20%24site.GroupId%20is%26nbsp%3B%3CSPAN%3E00000000-0000-0000-0000-000000000000%3C%2FSPAN%3E)%20and%20that%20looks%20bogus.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20troubleshooting%20ideas%20as%20to%20why%20group%20creation%20might%20fail%20in%20this%20script%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%20color%3D%22%23001000%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-183701%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGroups%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278735%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Attempt%20to%20groupify%20a%20classic%20SharePoint%20Team%20site%20programmatically%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278735%22%20slang%3D%22en-US%22%3EI%20have%20not%20been%20able%20to%20get%20this%20command%20to%20work%20on%20any%20of%20my%20tenants.%20The%20error%20is%20always%3A%20Add-PnPOffice365GroupToSite%20%3A%20The%20root%20site%20collection%20for%20this%20tenant%20cannot%20be%20connected%20to%20an%20Office%20365%20Group.%20Is%20groupifying%20a%20root%20site%20collection%20disallowed%20by%20design%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189616%22%20slang%3D%22en-US%22%3ERE%3A%20Attempt%20to%20groupify%20a%20classic%20SharePoint%20Team%20site%20programmatically%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189616%22%20slang%3D%22en-US%22%3ESee%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FRolling-out-tenant-admin-tools-to-connect-existing-SharePoint%2Fba-p%2F188750%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Blog%2FRolling-out-tenant-admin-tools-to-connect-existing-SharePoint%2Fba-p%2F188750%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-184605%22%20slang%3D%22en-US%22%3ERe%3A%20Attempt%20to%20groupify%20a%20classic%20SharePoint%20Team%20site%20programmatically%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-184605%22%20slang%3D%22en-US%22%3Eno%20worries%2C%20coming%20real%20soon...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-184568%22%20slang%3D%22en-US%22%3ERe%3A%20Attempt%20to%20groupify%20a%20classic%20SharePoint%20Team%20site%20programmatically%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-184568%22%20slang%3D%22en-US%22%3EThank%20you%20Christophe!%20I%20thought%20I%20was%20going%20crazy.%20I%20did%20read%20that%2C%20but%20for%20some%20reason%20I%20misinterpreted%20it%20to%20mean%20that%20although%20it%20wasn't%20be%20available%20via%20a%20GUI-menu%20operation%20yet%2C%20that%20the%20PowerShell%20method%20was%20ready.%20My%20mistake.%20Bob%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183771%22%20slang%3D%22en-US%22%3ERe%3A%20Attempt%20to%20groupify%20a%20classic%20SharePoint%20Team%20site%20programmatically%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183771%22%20slang%3D%22en-US%22%3E%3CP%3EBob%20we%20have%20not%20released%20this%20yet%20as%20stated%20in%20the%20article%3A%20%22%3CSPAN%3EThe%20option%20to%20connect%20an%20Office%20365%20group%20to%20an%20existing%20site%20is%20%3C%2FSPAN%3E%3CSTRONG%3Enot%3C%2FSTRONG%3E%3CSPAN%3E%20yet%20available%20and%20will%20be%20released%20during%20Q2%20of%20calendar%20year%202018.%3C%2FSPAN%3E%22%20%2B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8984%22%20target%3D%22_blank%22%3E%40Tejas%20Mehta%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Contributor

I'm attempting to groupify a single classic team site using the article posted here: Connect to an Office 365 Group and following the 2nd method which provides sample scripts to do it programmatically using PowerShell. 

 

The first PS script runs and checks for blockers, etc., and the target site passes with no issues. Then, when I run the second script (updating the variables and sections appropriately), it fails to create a new group and attach it to the updated Team Site. I'm assuming this is what's going wrong, because I notice that in the log/output, the ID of the group that it's trying to add to is "00000000-0000-0000-0000-000000000000" (i.e., $site.GroupId is 00000000-0000-0000-0000-000000000000) and that looks bogus.

 

Any troubleshooting ideas as to why group creation might fail in this script?

 

 

5 Replies
best response confirmed by Bob Manjoney (Regular Contributor)
Solution

Bob we have not released this yet as stated in the article: "The option to connect an Office 365 group to an existing site is not yet available and will be released during Q2 of calendar year 2018." + @Tejas Mehta

Thank you Christophe! I thought I was going crazy. I did read that, but for some reason I misinterpreted it to mean that although it wasn't be available via a GUI-menu operation yet, that the PowerShell method was ready. My mistake. Bob
no worries, coming real soon...
I have not been able to get this command to work on any of my tenants. The error is always: Add-PnPOffice365GroupToSite : The root site collection for this tenant cannot be connected to an Office 365 Group. Is groupifying a root site collection disallowed by design?