There are multiple issues with this feature roll-out. Not sure who's sleeping at the switch at Microsoft. 1) Autosave can be turned OFF via GPO, but not ON. I've opened a ticket for this and they said I'd have to go to user voice. I gather some admins don't want files saved automatically to the cloud, so I get being able to disable auto-save via GPO, but like ALL GPO we should be able to turn ON if we want. This isn't something that users should vote on, it's a freaking bug. 2) Autosave to local disks is now apparently not possible. Bizarre, as for 30+ years ONLY auto-save to local disks was available, and worked. So someone had to specifically code around this. Microsoft is pushing their cloud policy down our throat, and contributing to data loss to get their hands on our data. This is NOT acceptable. 3) "KFM" is very fragile and can break. I found 40% of our users had a broken KFM move because "OneNote" files couldn't be moved, so the whole OneDrive folder relocation hung. They weren't even using OneNote. 4) KFM requires a manual step to log into OneDrive, even after Active Directory was synchronized. Apparently, local workstations have to be hybrid joined. This was not documented in the steps to get KFM working. What's more ironic is that Teams will incessantly popup windows asking you to log in. Why can't OneDrive do this, especially after seing the GPO's to make KFM move mandatory? == John ==