Provisioning: born on first touch
A user's OneDrive is a personal SharePoint site collection (URL shape
/personal/user_domain_com). It isn't created when the account is; it's
provisioned on first access — the user opens OneDrive, or is shared a file
that lands there. Admins can pre-provision in bulk with
Request-SPOPersonalSite so a OneDrive exists before day one (useful for Known
Folder Move rollouts, next module). Until provisioned, the OneDrive simply
doesn't exist to enumerate.
Quota
Each licensed user gets a OneDrive quota (commonly 1 TB by default, raisable per
plan and by request for eligible plans). It's set with
Set-SPOSite -Identity <odburl> -StorageQuota or tenant-wide via
Set-SPOTenant -OneDriveStorageQuota. OneDrive storage is separate from the
SharePoint site pool — a user filling their OneDrive doesn't starve team sites.
The leaver problem (the incident this concept exists for)
When the user's Entra account is deleted, their OneDrive does not vanish immediately. Two mechanisms bridge the gap:
- Access delegation to the manager. OneDrive can be configured so that when an account is deleted, the departed user's manager (from the directory) is automatically granted access to the OneDrive for a set number of days — the "give the manager the leaver's files" pattern, configured in the OneDrive admin center. No manager attribute set → no automatic delegate.
- The orphaned-OneDrive retention window. The OneDrive is retained for a
period after account deletion — governed by
OrphanedPersonalSitesRetentionPeriod(default ~30 days, settable up to ~3650) — then it is permanently removed. That window is your only chance to recover or hand off content by default.
The failure modes
- "Shared in a Teams chat, now gone." Files shared in one-to-one/group chat live in the SENDER's OneDrive. Sender leaves → OneDrive offboards on the retention clock → every chat link to that file breaks ~30 days later. The file's fate was tied to a person, not a team (the one-content-system concept).
- No manager, no handoff. Automatic delegation needs a manager attribute; contractors and execs often have none, so their OneDrive silently expires with no one notified.
- Retention/holds override the clock. A OneDrive under a retention policy or legal hold is preserved past the orphan window (and its content sits in the Preservation Hold Library — compliance module), so "it should have been deleted" content persists for eDiscovery.
- License removed ≠ account deleted. Removing the SharePoint/OneDrive license starts a different countdown to OneDrive removal; the account can still exist.
What to watch (proofs)
- Provisioned OneDrives:
Get-SPOSite -IncludePersonalSite $true -Filter "Url -like '-my.sharepoint.com/personal/'"— the personal-site inventory. - The retention setting:
Get-SPOTenant | fl OrphanedPersonalSitesRetentionPeriod— how long a leaver's OneDrive survives; the recovery window in days. - Manager-delegation config: OneDrive admin center → Storage → "Days to retain" and the access-delegation setting — is a manager actually granted on deletion?
- Leaver audit: the unified audit log for the deleted user's OneDrive access events post-departure — proof the handoff happened before the clock ran out.