With so many people working in a hybrid environment and relying on cloud services like OneDrive and SharePoint, it’s critical to have insights into the health of OneDrive sync across your organizatio...
Updated Jun 07, 2022
Version 1.0
Blog Post
Hi dmalayeri.
Regarding your claim that the user-impacting changes to OneDrive were because "Apple deprecated the kernel extension that we were using for OS integration": this is a lie.
Yes, Apple absolutely did make changes. But those changes did not require to Microsoft to degrade the user experience in the way that it has. This change applies to all cloud storage vendors, and of the vendors that have adapted their product to Apple's new requirements, only Microsoft has chosen this path. A path which aligns with Microsoft's very clear (and oft-stated) intention to increase customer lock-in by forcing all our data into your cloud, and treating our (customer-owned) PCs as much like dumb terminals as possible.
So that's not just a lie, it's an easily debunked lie that transparently reflects Microsoft's self-serving interests at the expense of the customer. And I plan to keep calling Microsoft out on this. Your marketing and messaging be damned.
If you care to explain precisely why one of the largest companies in the entire world is apparently incapable of preserving customer-desired operation of a product through an upstream supplier's library code change, when all your competitors in the space have managed to preserve that exact customer-desired behaviour, I'm willing to listen. I am quite interested in precisely what rationalization Microsoft has for being somehow unable to match the technical capabilities of its competitors in this space.
Please...do explain. Because the rationale for the user-hostile choices Microsoft made in the 2/1 blog post does not stand up to even the most basic scrutiny.