Forum Discussion
SharePoint communication site launch scheduler not working on Root site collection?
- Nov 22, 2022
I have spoken to one of my connections within Microsoft about this and it turns out I misinterpreted the following note:
Launches must be scheduled at least seven days in advance and each wave can last one to seven days.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/portallaunchscheduler?view=o365-worldwide
This quote actually means that waves have to be scheduled at least seven days in advance. At the launch date of the first wave the launch process will start indexing all the added security groups / users. After indexing the launch process will make the portal available to the the indexed users one by one. Therefore this process can take up to seven days.
The exception which can be set for example for testing purposes will also follow this process and is in essence also a wave.
I have spoken to one of my connections within Microsoft about this and it turns out I misinterpreted the following note:
Launches must be scheduled at least seven days in advance and each wave can last one to seven days.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/portallaunchscheduler?view=o365-worldwide
This quote actually means that waves have to be scheduled at least seven days in advance. At the launch date of the first wave the launch process will start indexing all the added security groups / users. After indexing the launch process will make the portal available to the the indexed users one by one. Therefore this process can take up to seven days.
The exception which can be set for example for testing purposes will also follow this process and is in essence also a wave.