Yeah onedrive is seriously annoying. It's nice when the free 15GB backup/sync for the desktop, pictures, and documents folder works (for people who put things there) but the way other MS products work with it seems user-hostile to me.
e.g. it took until 2025 for this RFC to be opened on moving PowerShell profiles and modules out of Onedrive: https://github.com/PowerShell/PowerShell-RFC/pull/388. It should not be taking seconds for my powershell profile to load just because i have onedrive enabled by default.
I also had a non-technical friend recently get burned by a default MS Office setting where edited documents located in the OneDrive folder save directly to onedrive, and it only gets saved on disk when onedrive gets the new copy and uploads it back it to the user's disk. So if the MS office to onedrive integration fails your changes won't save. Apparently users have to enable a setting to first save to a folder on disk? That folder can even be the onedrive folder so onedrive will eventually sync it back up.
e.g. it took until 2025 for this RFC to be opened on moving PowerShell profiles and modules out of Onedrive: https://github.com/PowerShell/PowerShell-RFC/pull/388. It should not be taking seconds for my powershell profile to load just because i have onedrive enabled by default.
I also had a non-technical friend recently get burned by a default MS Office setting where edited documents located in the OneDrive folder save directly to onedrive, and it only gets saved on disk when onedrive gets the new copy and uploads it back it to the user's disk. So if the MS office to onedrive integration fails your changes won't save. Apparently users have to enable a setting to first save to a folder on disk? That folder can even be the onedrive folder so onedrive will eventually sync it back up.