Current Answer: OneDrive Is a Native Cloud Drive in ZimaOS Files
In June 2026, OneDrive authorization was broken globally for a period because IceWhale's Microsoft Azure application secret expired. That incident explains why users could log in and then see nothing in Files. It is historical now: current ZimaOS documentation again lists OneDrive as a supported cloud drive directly inside Files.
Use Files → Add Cloud Drive → OneDrive
The current ZimaOS Cloud Drive says Google Drive, Dropbox and OneDrive mount directly beside local storage in Files. You should not need a separate OneDrive Docker container or rclone setup for the built-in integration.
The ZimaOS file access provides the user-access layer around those mounted cloud drives.
If Login Succeeds but OneDrive Still Does Not Appear
Remove the stale cloud-drive connection, add it again, complete Microsoft authorization, and then refresh Files. Check the current ZimaOS version before applying June 2026 workarounds—the original OAuth failure required a server-side credential fix and could not be solved by editing a local mount path.
How to Recognize an OAuth Credential Failure
Microsoft documents AADSTS7000222 as an expired client-secret condition in Entra application authentication. See Microsoft's Entra OAuth error codes. If a future integration outage shows a provider OAuth error, collect the exact code instead of repeatedly reinstalling ZimaOS.
Do Not Confuse Cloud Mounting With Backup
A mounted OneDrive is a live cloud filesystem. If your goal is a separate protective copy, create a ZimaOS Backup task from cloud to local storage or vice versa. The ZimaOS backup covers that workflow.
Use Microsoft Status as a Second Check During a Widespread Outage
If many users fail at the same authorization step, verify both the ZimaOS integration and Microsoft's current service state rather than assuming your local filesystem is broken. Microsoft's Microsoft service health is one independent control.
