Since the inception of the OneDriveMapper script, I’ve often been asked if there is a way to pre-provision Onedrive for Business storage for users.

When a user signs into Office 365 for the first time and clicks Onedrive, their Onedrive for Business storage will be allocated and initialized, before that, it is not possible to map their OneDrive storage, or sometimes more importantly: to migrate data to it.

As a good consultant or IT admin, you don’t want to force your users to do this before they can map their drive or before you migrate their data because you like to automate things, repetitive or manual process tend to be unreliable.

Doing this the smart way, is scripting it. Of course your users already have to have a license.

Don’t forget to set administrative permissions on all accounts afterwards, if you intend to migrate data there for your users.

The following script will pre-provision OneDrive for ALL users in your Office 365 environment.

ODFB_BP_v0.2

Source:

########
#ODFB Bulk Provisioning
#Copyright: Free to use, please leave this header intact
#Author: Jos Lieben (OGD)
#Company: OGD (http://www.ogd.nl)
#Script help: http://www.lieben.nu
#Purpose: Provision Onedrive for all users in Office 365
########
#Changes:
#V0.2 fixed a bug, .Clear() does not function as expected in Powershell, = @() does.
#V0.21 changed the default batch size to 10, this seems to work better (reported by Iain)
########
#Requirements:
########
<#MS Online Services Signin Assistant:
https://www.microsoft.com/en-us/download/details.aspx?id=41950
Azure AD Module (x64):
http://social.technet.microsoft.com/wiki/contents/articles/28552.microsoft-azure-active-directory-powershell-module-version-release-history.aspx
Powershell 4
.NET 4.5
Sharepoint Server 2013 Client Components
https://www.microsoft.com/en-us/download/details.aspx?id=42038
run “Set-Executionpolicy Unrestricted” in an elevated powershell window
Windows 7+ or Windows Server 2008+
#>

$o365login = "admin@ogdemo1.onmicrosoft.com" #Username of O365 Admin
$o365pw = "YourPassword" #Password of O365 Admin
$logfile = ($env:APPDATA + "\ODFB_BP.log") #Logfile in case of errors
$spURL = "https://ogdemo1-admin.sharepoint.com" #URL to your SP Admin site $batch_size = 10 #Maximum accounts to provision at once, technet lists 200 as the max, but users have reported 10 is optimal 

#Start script
ac $logfile "-----$(Get-Date) ODFB_BP v0.2 $($env:COMPUTERNAME) Session log-----`n"

#build Credential Object
$secpasswd = ConvertTo-SecureString $o365pw -AsPlainText -Force
$Credentials = New-Object System.Management.Automation.PSCredential ($o365login, $secpasswd)

#Load sharepoint module
try{
 [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client") | Out-Null [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.Runtime") | Out-Null [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.UserProfiles") | Out-Null
}catch{
 $errorstring = "ERROR: Failed to load Sharepoint Libraries, exiting"
 ac $logfile $errorstring
 Write-Host $errorstring
 Pause
 Exit
}
#load Azure module
$env:PSModulePath += ";C:\Windows\System32\WindowsPowerShell\v1.0\Modules\"
try{
 Import-Module msonline
}catch{
 $errorstring = "ERROR: Failed to load Azure module, exiting"
 ac $logfile $errorstring
 ac $logfile $error[0]
 Write-Host $errorstring
 Pause
 Exit
}
#connect to MSOL
try{
 Connect-MsolService -Credential $Credentials
}catch{
 $errorstring = "Critical error, unable to connect to O365, check the credentials"
 ac $logfile $errorstring
 ac $logfile $error[0]
 Write-Host $errorstring
 Pause
 Exit
}

#fetch all UPN's
$users = Get-MsolUser -All | Select-Object UserPrincipalName

#Build sP object
$client = New-Object Microsoft.SharePoint.Client.ClientContext($spURL) $clientweb = $client.Web $client.Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($o365login,$secpasswd) #Connect $client.Load($clientweb) try{ $client.ExecuteQuery() }catch{ $errorstring = "Critical error, unable to connect to Sharepoint Online, check admin url and credentials"
 ac $logfile $errorstring
 ac $logfile $error[0]
 Write-Host $errorstring $error[0]
 Pause
 Exit } $loader =[Microsoft.SharePoint.Client.UserProfiles.ProfileLoader]::GetProfileLoader($client) $profile = $loader.GetUserProfile() $client.Load($profile) $client.ExecuteQuery() #enqueue per batch_size users (max is 200 users per batch) $total = $users.Count $batchjob = @() for($i = 0; $i -lt $total; $i++){ $batchjob += $users[$i].UserPrincipalName if($i+1 -eq $total -or $batchjob.Count -gt $batch_size){ #enqueue in loader try{ $loader.CreatePersonalSiteEnqueueBulk($batchjob) $loader.Context.ExecuteQuery() }catch{ $errorstring = "Critical error, unable to create bulk provisioning job in Sharepoint Online"
 ac $logfile $errorstring
 ac $logfile $error[0]
 ac $logfile $batchjob
 Write-Host $errorstring $error[0] $batchjob } $batchjob = @() } } ac $logfile "Script finished" Write-Host "Job Finished" Pause Exit 

Script was inspired by Frank Marasco’s post on technet.