Forum Discussion
Solved
Request-SPOPersonalSite does not seem to work as desired (RESOLVED!)
I'm testing the PowerShell provisioning of OneDrive sites with simple script but it does not appear to be working.
$tenant = "AAAAAA"
Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking
Connect-SPOService -Url https://$tenant-admin.sharepoint.com
$emails = "jbagadonuts@AAAAAA.com,bmeints@AAAAAA.com"
Request-SPOPersonalSite -UserEmails $emails -NoWait
I have all the latest modules, I run the script, and nothing happens. I've waited 24+ hours for the accounts to be provisioned, but in the admin panel when looking at users, it shows user's OneDrive not provisioned. Anyone else see this behavior?
Found the solution after working with Microsoft Premier support. There are two errors on this page: https://technet.microsoft.com/en-us/library/dn792367.aspx (as of 8/21/2017). It does not mention:
1. In addition to being an admin account, the account doing the provisioning MUST be licensed for SharePoint Online.
2. The syntax of the PowerShell was incorrect in the original Microsoft page. The emails should be EACH in quotes, separated by a comma ("mail1","mail2"): so in original example it should read:
$emails = "jbagadonuts@AAAAAA.com","bmeints@AAAAAA.com"
after running the PowerShell, SP Online timer job provisioned both in a few minutes.
2 Replies
Found the solution after working with Microsoft Premier support. There are two errors on this page: https://technet.microsoft.com/en-us/library/dn792367.aspx (as of 8/21/2017). It does not mention:
1. In addition to being an admin account, the account doing the provisioning MUST be licensed for SharePoint Online.
2. The syntax of the PowerShell was incorrect in the original Microsoft page. The emails should be EACH in quotes, separated by a comma ("mail1","mail2"): so in original example it should read:
$emails = "jbagadonuts@AAAAAA.com","bmeints@AAAAAA.com"
after running the PowerShell, SP Online timer job provisioned both in a few minutes.
Just two additional points:
- If the account is synced with AD, do not enable the option the user has to change his password at the next logon. The Request-SPOPersonalSite command has a timeout if the option is active.
- Request-SPOPersonalSite is also not possible if the account is disabled or blocked.
Regards
Tobias
