Forum Discussion
Removing the empty classic team root site and create a new modern communication root site
I want to start a new Office 365 project. and i am facing with the same old/new issue, is that there root site collection is actually a classic team site collection. but i want to have it as modern c...
ChrisHoardMVP wrote:
AFAIK, a remove and add would not be a supported scenario.
Best, Chris
is there any official documentation about this ? that it is not supported? and why this will not be supported if new tenants will have their root site collection as a communication site collection..
No official documentation that I can find that it is either supported or not supported. As this uservoice is currently open for it
https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/20308864-set-communication-site-as-root-site-collection
And the fact that they are bringing out shell commands to convert suggest it is unsupported.
Of course, nothing says it 100% isn’t. I am also going on the fact of doing things, they not work and contacting MS support only for them to say it is not officially supported after. I guess my point is there is nothing official to say this supported
Best, Chris
https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/20308864-set-communication-site-as-root-site-collection
And the fact that they are bringing out shell commands to convert suggest it is unsupported.
Of course, nothing says it 100% isn’t. I am also going on the fact of doing things, they not work and contacting MS support only for them to say it is not officially supported after. I guess my point is there is nothing official to say this supported
Best, Chris
ChrisHoardMVP wrote:
No official documentation that I can find that it is either supported or not supported. As this uservoice is currently open for it
https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/20308864-set-communication-site-as-root-site-collection
And the fact that they are bringing out shell commands to convert suggest it is unsupported.
Of course, nothing says it 100% isn’t. I am also going on the fact of doing things, they not work and contacting MS support only for them to say it is not officially supported after. I guess my point is there is nothing official to say this supported
Best, Chrisok i got your point. so if this is the case, then what do you think of just using the current classic team site as-is.. and i can define modern pages and use the modern UI on the custom lists i am planning to add.. so in this case the classic team site will just look as a modern communication site...