Forum Discussion
PowerShell new-team command creates team and SP online site but does not link
We are migrating a large number of legacy SharePoint internal sites to Teams / SP Online using the Microsoft SharePoint Migration Tool. Manually, the tool works with some quirks. However, we have ove...
I made a change to my new-team command to include the intended /teams/target as the -MailNickName and this was the key to creating the SP online site, however, now after 2 hours, Teams continues to say it's "setting up your file directory". Will it eventually link the Team and SP site? If it's just a tenant throttling and will eventually connect, then my process will work as soon as the SP site is created.
- Happy to report that after 3+ hours, the Team and SP site were properly linked. I expected cloud to be slower for some access, but it appears that throttling of new sites and migrations is having a bigger impact than we expected.
- This is ridiculous. After performing the migration of a second set of 6 sites, all Teams and SP sites are created, but 3 of 6 continue to show "setting up your file directory" after 20 hours! This has to be an issue with the Teams background processing that is probably beyond my control. I intend to escalate a formal ticket with MS support. We can't schedule turnover meetings with business departments without reliable predictable performance of Team creation. FYI - this issue can sometimes happen with interactive Team creation but seldom for more than 3-4 hours.