Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Microsoft has rolled out a new set of PowerShell scripts that give IT admins a much simpler way to view, export, and delete users’ Windows settings backup data. Instead of hand-crafting calls against the Microsoft Graph windowsSetting APIs, admins can now run a couple of purpose-built cmdlets and get the job done in minutes.
Why This Matters
Managing Windows backup data through raw Graph API calls has always been possible, but it was a tedious process that required admins to understand endpoint structures, authentication flows, and payload formatting. This new tooling wraps all of that complexity into two straightforward scripts, lowering the barrier for day-to-day data governance and compliance tasks.
What’s Included
The release ships with two key scripts:
- View-WindowsBackup.ps1 — lets you view and export a user’s backup data
- Delete-WindowsBackup.ps1 — irreversibly deletes backup data, with confirmation prompts and a summary of what will be removed before anything happens
Key Commands
Get-WindowsBackup
Get-WindowsBackup -UserId user@domain.com
Remove-WindowsBackup -UserId user@domain.com
Running Get-WindowsBackup with no parameters returns your own backup data — no special permissions needed. To view or remove another user’s data, you’ll need the Microsoft 365 Backup Administrator role assigned to your account.
Prerequisites
- Windows PowerShell 5.1 or PowerShell 7
- The
Microsoft.Graph.Authenticationmodule (installs automatically on first run) - Internet access to
login.microsoftonline.comand the Graph API endpoints
Installation
Microsoft is distributing the tooling through the PowerShell Gallery:
Install-Module WindowsBackupAdmin -Scope CurrentUser
A Few Things to Keep in Mind
- These scripts rely on Microsoft Graph beta APIs, which can change without notice and potentially break functionality — don’t build critical automation around them just yet.
- The module pulls in
Microsoft.Graph.Authenticationas a runtime dependency, but Microsoft notes the scripts themselves contain no third-party code. - Because the delete operation is irreversible, treat
Remove-WindowsBackupwith the same caution you’d apply to any destructive Graph or Exchange cmdlet — test in a non-production tenant first.
Bottom Line
This is a small but genuinely useful quality-of-life release for admins who regularly handle Windows Backup and Restore data across a fleet of devices. It won’t replace a full backup management platform, but for quick lookups, exports, and cleanup tasks, it beats scripting raw Graph calls every time.
