OneDrive for Business with PowerShell 7: Leavers, Sharing and Pre-Provisioning

I have worked in IT for about 20 years. A lot of that was MSP operations. Today I work as an M365 cloud admin.

I kept writing the same scripts. So I cleaned them up and shared them on GitHub. This toolkit is for OneDrive for Business admins. It uses the SPO module and Microsoft Graph with PowerShell 7.

Repo: onedrive-powershell-toolkit

The problem it solves

When someone leaves, their manager often needs their files. Doing that by hand is fiddly.

Users also share files with "anyone" links and forget about them.

And before a migration, new users may not have a OneDrive yet. These scripts handle all three.

Highlight scripts

Grant-DepartedUserOneDriveAccess.ps1

Gives a manager access to a leaver's OneDrive as a secondary admin. A matching script removes that access later.

./Grant-DepartedUserOneDriveAccess.ps1 -DepartedUser former.user@contoso.com -Delegate manager@contoso.com -WhatIf

Get-OneDriveSharingAudit.ps1

Lists shared files and folders per user with the link type. Use -AnonymousOnly to see just the "anyone" links.

./Get-OneDriveSharingAudit.ps1 -UserPrincipalName user1@contoso.com -AnonymousOnly

Request-OneDrivePreProvisioning.ps1

Pre-provisions OneDrive for licensed users who never signed in. Handy before a file migration.

./Request-OneDrivePreProvisioning.ps1 -CsvPath ./samples/preprovision-users.sample.csv -WhatIf

Other scripts cover OneDrive inventory and storage, usage reports and tenant settings. The docs include Known Folder Move notes.

How the scripts are built

• PowerShell 7.4 or later.
• Comment-based help on every script. Run Get-Help ./script.ps1 -Full.
• Reports export to CSV.
• Change scripts support -WhatIf and -Confirm.
• Certificate (app-only) or interactive sign-in.
• No secrets in the repo. Examples use contoso.com and placeholder GUIDs.

Please test in a dev or test tenant first. Read each script before you run it.

My usual workflow

I start with the reports. They are read-only and safe. I open the CSV in Excel and look for anything odd.

Then I pick one fix. I run the change script with -WhatIf and read the output. If it looks right, I run it again for real.

For jobs I repeat, I use a certificate and schedule the script. That way nobody has to remember to run it.

Getting started

Clone the repo:

git clone https://github.com/anthonybuhnerkemper/onedrive-powershell-toolkit.git
cd onedrive-powershell-toolkit

Every toolkit ships the same Connect-M365Admin script. Dot-source it, then connect.

# Interactive sign-in
. ./scripts/Connect/Connect-M365Admin.ps1
Connect-M365Admin -Service SharePoint, Graph -Interactive -ClientId 00000000-0000-0000-0000-000000000000

# Or app-only with a certificate
$env:M365_TENANT_ID       = '00000000-0000-0000-0000-000000000000'
$env:M365_CLIENT_ID       = '00000000-0000-0000-0000-000000000000'
$env:M365_CERT_THUMBPRINT = '0000000000000000000000000000000000000000'
Connect-M365Admin -Service SharePoint, Graph

Run a report, check the CSV, then call Disconnect-M365Admin when you are done. The README lists the modules and roles each script needs.

More toolkits

I have nine more free toolkits that use the same pattern: graph-powershell7-admin-toolkit, entra-id-powershell-toolkit, exchange-online-powershell-toolkit, sharepoint-online-powershell-toolkit, teams-powershell-toolkit, intune-powershell-toolkit, defender-xdr-powershell-toolkit, sentinel-kql-toolkit, purview-compliance-toolkit.

You can find them all on my GitHub profile.

Feedback welcome

Issues, ideas and pull requests are welcome. What would you add? Tell me in the comments.