2.24.22 UPDATE: We've been listening to your feedback, and we've made some design changes. We're releasing a new version that addresses the most common themes and makes it easier to achieve the previ...
Updated Feb 24, 2022
Version 12.0
Blog Post
The problem is - and that MS won't publicly acknowledge - is that the behavior we are seeing (mass files moving from cloud locations) is EXACTLY what Ransomware does - which is why many of us suspected that was what was happening when we first saw the changes. The throttling is part of mitigation about that (it shouldn't be easy to mass-move files between locations).
Unfortunately MS really haven't thought through the business use cases of OneDrive, and assume they can behave as if we were all on a 100% reliable intranet. How they have managed to miss this is baffling to me. Did no-one internally sound an alarm that this would break a large number of very common use cases?
Oh I'm sure they had all kinds of customer stories and it was all so pretty and Agile. But the people doing the research live in a bubble and have no interest in venturing outside of it.
The closest parallel I can think of is New Coke, where in taste tests as a replacement for "Classic" coke, their customers all said two things:
1) This tastes really good
2) Don't replace Coca-Cola with it
The people behind new coke all stopped reading at 1). History records in detail what happened next. My analogy is:
1) People by and large like Files-On-Demand
2) People by and large hate large-scale modifications to their computers that aren't absolutely necessary
the onedrive root change is necessary. It's a pain, but in and of itself, is not damaging. That had to be done. The forced move to FOD did NOT have to be done, but they stopped reading at 1)
and I am absolutely sure no one on the OneDrive team lives anywhere they have to drive for 30 minutes to an hour to get anything resembling "fast" internet connections to redownload many GB of data.