That's my feeling too. I work in a private sector business that's basically "all Microsoft" (like most of our competitors). Once you get on the "Microsoft train", you ride their rails and go to the stops they dictate. You have to jump back off otherwise.
We ran into the typical situation where once people saw they had OneDrive capabilities to share files or folders with other people or groups, they started trying to create folders of information needed by entire teams. If they left the company, all of that data was at risk of vanishing because it was, after all, stored on their personal OneDrive, tied to their user account with only that person as its administrator.
Microsoft's answer to this is SharePoint. Create new SharePoint sites for your groups, so I.T. can be administrator of them and control them (and/or optionally designate others to admin them as needed). And then, people can collaborate and use the shared content on the SharePoint site. Great, right? Well, not so much! Because Microsoft intertwined SharePoint and OneDrive. People needing easy access to the content of a SharePoint site or folder from their Windows Explorer have to "sync" it via OneDrive from that SharePoint site. Then they get a new "tree" of SharePoint sites that appear in their Explorer to get to the information without visiting the web site directly.
Now you get all sorts of headaches because OneDrive can get signed out on a PC accidentally, disconnecting those shared folders. Users may not notice for a while so they keep editing their locally cached copy of the documents - thinking those changed were getting to the cloud. Or OneDrive will do as it does, and gets corrupted and stops syncing properly -- requiring an uninstall/reinstall to fix it again. Or you have "permissions" fun, where a user is initially granted "edit" rights to some content he/she syncs with OneDrive. But their permissions get changed to "read only" at some point, causing them to have files forever stuck that get sync errors, because their changes are no longer allowed to go back up to the SharePoint.
When you have hundreds of people or more in a company using this stuff, these "edge case problems" come up daily and your help desk team is forever tasked with trying to sort out what's happened, and how to help people get the correct versions of documents back in the cloud for everyone to use.
And all this is before we even start talking about your advanced users, trying to link data between Microsoft Office applications. SharePoint still doesn't support some of that like your traditional desktop Office apps do. They're all written to link to data via your standard folder paths. They can't pull from, say, rows in an Excel workbook and import to a PowerPoint using the URL path needed to specify the location of the file out in a SharePoint site.
Companies like ours tried to eliminate the traditional file servers to replace them with the SharePoint and OneDrive combo Microsoft wanted people to pivot to using. But the reality is, we still have to keep a traditional file server around, just for these scenarios. It's half-baked.