Skip to content

Commit a80f17e

Browse files
authored
Update modernize-connect-to-office365-group.md
Removing notice on not being able to groupify certain types of sites. Tested all of the mentioned scenarios and all of them are no longer valid. Any classic site type can now be groupified without any problem.
1 parent 3fa17f2 commit a80f17e

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

docs/transform/modernize-connect-to-office365-group.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,6 @@ You can connect your site to a new Microsoft 365 group from the user interface s
1414

1515
In this article, you'll learn how to prepare for such a bulk operation for associating sites to new Microsoft 365 groups and how to actually make it happen.
1616

17-
> [!IMPORTANT]
18-
> For publishing portals (sites based upon BLANKINTERNET#0, ENTERWIKI#0, SRCHCEN#0, SRCHCENTERLITE#0, BICENTERSITE#0, POINTPUBLISHINGHUB#0, POINTPUBLISHINGTOPIC#0 or sites using the “Pages” library) it's not currently supported to connect these to a Microsoft 365 group or to use modern pages. If you want to modernize your publishing portal it's recommended to start from a new communication site and configure that one accordingly.
19-
2017
> [!IMPORTANT]
2118
> - It is **not** supported to connect a Communication site to Microsoft 365 group.
2219
> - You cannot group connect the root site collection in your tenant.

0 commit comments

Comments
 (0)