If the OneDrive authorization window in ZimaOS opens and immediately closes, update to the current stable ZimaOS and retry the current Cloud Drive flow before editing rclone or recreating credentials. The 2026 source issue was traced by community logs to an expired Microsoft Entra client secret, producing AADSTS7000222.
That was an upstream integration outage, not a broken OneDrive account. Current September 2026 ZimaOS documentation again lists OneDrive as a supported Cloud Drive.
What the Historical Failure Looked Like
Previously connected users could no longer reauthorize; the login dialog appeared briefly and closed before OAuth completed, blocking new backup jobs.
Check the Current Cloud Drive Workflow
The current ZimaOS Cloud Drive guide lists OneDrive, Dropbox, and Google Drive as supported providers.
Step 1: Update and Hard-Refresh
Use a current stable build and test in a private browser window to remove stale frontend and OAuth pop-up state.
Step 2: Capture the OAuth Error
If the window still closes, inspect browser developer tools or backend logs. The historical outage produced AADSTS7000222, which meant the application's Microsoft credential had expired.
Step 3: Do Not Rewrite rclone.conf First
ZimaOS-managed Cloud Drives include UI metadata/provider state beyond a bare rclone remote. Manual remotes can work in terminal while remaining unmanaged in Files/Backup.
Step 4: Verify the Microsoft Account Separately
Sign in to OneDrive directly. If Microsoft accepts the account but ZimaOS OAuth fails, the problem is more likely integration/client state.
Step 5: Verify Recovery Before Backup
After authorization succeeds, browse a known cloud file, then re-enable backup jobs. The backup planning guide helps keep mount and backup failures distinct.
Check Popup and Cookie Blocking
OAuth depends on opening a login window and returning an authorization result. Browser popup protection, strict third-party cookie rules, or privacy extensions can interrupt that flow. Test once in a clean browser profile before changing server configuration.
Separate OneDrive Mounting from Backup
First make OneDrive appear and browse correctly in Files. Only then test a backup task. Troubleshooting both layers at the same time makes it hard to know whether the failure is OAuth, mounting, or Backup.
Do Not Revoke Working Microsoft Sessions Without a Reason
If the error is a shared application credential failure, revoking your own account consent does not renew IceWhale's client secret. Preserve the working provider-side account state while the integration is being repaired.
What to Send Support
Include ZimaOS version, browser, exact timestamp, Microsoft error code, whether Dropbox/Google Drive work, and whether OneDrive works directly on Microsoft's site. That evidence quickly separates local account trouble from a provider integration outage.
Check Whether Other Providers Still Work
If Dropbox or Google Drive still authorizes while OneDrive alone fails, that strongly narrows the problem to the Microsoft integration path rather than the entire ZimaOS cloud-drive service.
If all providers fail simultaneously, investigate browser popups, ZimaOS network connectivity, time synchronization, and the Files backend before focusing on Microsoft-specific credentials.
FAQ
Was the 2026 OneDrive problem global?
Community logs linked it to an expired shared Azure/Entra client secret.
Is OneDrive supported now?
Yes. Current ZimaOS Cloud Drive documentation includes it.
Should I delete my Microsoft account connection?
Not until you know the failure is local.
Can I use manual rclone as fallback?
Advanced users can, but it may not integrate cleanly with Files and Backup.
