SOLVED

Default Wiki Home - Modern SharePoint Home Page

%3CLINGO-SUB%20id%3D%22lingo-sub-729683%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729683%22%20slang%3D%22en-US%22%3EHi%20Ajay%2C%3CBR%20%2F%3E%3CBR%20%2F%3EWould%20recommend%20you%20read%20this%20post.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FCommunications-Sites-AMA%2FChange-Tenant-Root-into-a-Communication-Site%2Fm-p%2F263650%23M645%25C2%25A0%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FCommunications-Sites-AMA%2FChange-Tenant-Root-into-a-Communication-Site%2Fm-p%2F263650%23M645%25C2%25A0%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ENow%2C%20as%20you%20will%20see%20in%20the%20post%20you%20can%20redirect%20but%20it%20you%20wait%20a%20bit%20longer%20you%E2%80%99ll%20have%20tools%20to%20either%20convert%20the%20root%20site%20into%20a%20comms%20site%2C%20or%20move%20an%20existing%20comms%20site%20to%20the%20root.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20helps%20to%20answer%20your%20question!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-729739%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729739%22%20slang%3D%22en-US%22%3EAbility%20to%20convert%20the%20root%20site%20into%20a%20communication%20site%20is%20comming...additionally%2C%20it%20will%20be%20also%20possible%20to%20make%20an%20existing%20communication%20site%20your%20root%20site%20so%20it's%20just%20a%20question%20of%20time.%20If%20you%20don't%20want%20to%20wait%20until%20any%20of%20those%20options%20happens%2C%20what%20I%20would%20recommend%20is%20simply%20create%20a%20modern%20page%20in%20your%20root%20site%20and%20%22mark%22%20as%20home%20page%20of%20your%20site...it%20should%20be%20enough%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-730038%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-730038%22%20slang%3D%22en-US%22%3EHi%20Juan%2C%3CBR%20%2F%3Ethanks%20for%20the%20feedback%2C%20any%20idea%20what%20is%20the%20timeline%20in%20regards%20to%20the%20availability%20of%20the%20functionality%20to%20convert%20root%20site%20to%20communications%20site%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-730073%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-730073%22%20slang%3D%22en-US%22%3ECY2019%20Q4%20per%20Microsoft365%20roadmap%20update.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%E2%80%99ll%20need%20to%20search%20for%20feature%20Number%2046338%20on%20the%20roadmap%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-729658%22%20slang%3D%22en-US%22%3EDefault%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729658%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20All%2C%3C%2FP%3E%3CP%3ELooking%20for%20some%20best%20practice%20feedback%20from%20the%20community.%20When%20we%20were%20assigned%20a%20SharePoint%20tenant%20as%20part%20of%20our%20Office%20365%20subscription%2C%20our%20SharePoint%20home%20page%20is%20old%20(classic)%20Wiki%20page%20by%20default.%20What%20is%20the%20best%20practice%20to%20replace%20the%20default%20home%20page%20with%20a%20modern%20SharePoint%20communications%20page%20and%20redirect%20the%20current%20home%20URL%20%3CA%20href%3D%22https%3A%2F%2Fxxx.sharepoint.com%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fxxx.sharepoint.com%3C%2FA%3E%20to%20the%20new%20home%20page.%3C%2FP%3E%3CP%3EIt%20will%20be%20great%20to%20get%20some%20perspective%20what%20the%20community%20is%20doing%20in%20this%20regard!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-729658%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDefault%20Home%20Page%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EModern%20Communications%20Site%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESite%20Upgrade%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-730603%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-730603%22%20slang%3D%22en-US%22%3EThanks%20Chris!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-795840%22%20slang%3D%22en-US%22%3ERe%3A%20Default%20Wiki%20Home%20-%20Modern%20SharePoint%20Home%20Page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-795840%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20new%20switch%20root%20site%20Power%20Shell%20Camlet%20is%20now%20available%20%E2%80%A6.%20maybe%20a%20little%20late%20...%20but%20you%20can%20build%20a%20Modern%20Template%20site%20and%20then%20with%20the%20PS%20command%20switch%20it%20to%20the%20root%20site.%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F156607%22%20target%3D%22_blank%22%3E%40Ajay%20Mandal%3C%2FA%3E%26nbsp%3B%20Have%20Fun!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello All,

Looking for some best practice feedback from the community. When we were assigned a SharePoint tenant as part of our Office 365 subscription, our SharePoint home page is old (classic) Wiki page by default. What is the best practice to replace the default home page with a modern SharePoint communications page and redirect the current home URL https://xxx.sharepoint.com to the new home page.

It will be great to get some perspective what the community is doing in this regard!

6 Replies
Highlighted
Hi Ajay,

Would recommend you read this post.

https://techcommunity.microsoft.com/t5/Communications-Sites-AMA/Change-Tenant-Root-into-a-Communicat...

Now, as you will see in the post you can redirect but it you wait a bit longer you’ll have tools to either convert the root site into a comms site, or move an existing comms site to the root.

Hope that helps to answer your question!

Best, Chris
Highlighted
Ability to convert the root site into a communication site is comming...additionally, it will be also possible to make an existing communication site your root site so it's just a question of time. If you don't want to wait until any of those options happens, what I would recommend is simply create a modern page in your root site and "mark" as home page of your site...it should be enough
Highlighted
Hi Juan,
thanks for the feedback, any idea what is the timeline in regards to the availability of the functionality to convert root site to communications site?
Highlighted
Best Response confirmed by Ajay Mandal (Occasional Contributor)
Solution
CY2019 Q4 per Microsoft365 roadmap update.

https://www.microsoft.com/en-us/microsoft-365/roadmap

You’ll need to search for feature Number 46338 on the roadmap

Best, Chris
Highlighted
Thanks Chris!
Highlighted

The new switch root site Power Shell Camlet is now available …. maybe a little late ... but you can build a Modern Template site and then with the PS command switch it to the root site.@Ajay Mandal   Have Fun!