

No… then they don’t do what I’m talking about. I’m sorry you deal with the suck, but your IT team still gets hammers.
My workplace backs up to OneDrive itself. No requirement of work VPN, just sign in on a work machine with internet connection and confirm the MFA prompt.
Technically OneDrive is some unholy patchwork on top of Sharepoint Online, as evidenced by a ton of back end settings going through the SharePoint admin UI, but that’s not relevant to the discussion.
I didn’t even know it was possible to hijack Onedrive to point to SharePoint Server. For that matter who in the absolute fuck is still using Sharepoint Server? It went out of support two years ago, and extended support (at significantly extra cost) ends July 14th.
There is technically another On-Prem version past 2019, but it’s obvious bare minimum life support.
Plus, Microsoft locks so many of their security and other features baked into Azure behind Office 365 E5 licenses that most places are just using those for Office etc, and those come with a shit ton of storage per-user in OneDrive and SharePoint online.
We also don’t have auto-deletion turned on (yet). I’ve already done what I can to talk my boss out of it, but we will have options to prevent it on specific files and folders, as we already do with email (auto delete past certain age, unless it’s in the archove folder. you can set up auto archive rules if you need, but there’s rules on max space).
TL;DR- Your workplace does not in fact do “essentially what I described”, which is a large contributor to the issues you’ve seen. Go get hammers and beat your IT staff with them.
Especially the Sharepoint Server shit. That’s horrifying. No one should have to even think about touching that. Ewwww.














I don’t disagree, but corps are going to push the settings in their software and products that makes them the most money. It sucks but should be expected.
It’d be better if there were competitve open source options with the same ease of use, of implementation at scale, and ease of management at scale, but unless you’re willing to do custom forking and dev work, most of the time it’s easier to go with whatever is the overwhelming standard is and work around the rough spots, as at least then you’ll almost never be in completely uncharted waters.
I spent a few years building a custom solution for integrating a semi-popular but still relatively new HRIS system with a hybrid AD/Entra environment with a somewhat unique hybrid Exchange (email) setup. Doing it live, no real documentation to speak of because the few other places that had done it turn out to be consulting groups that sell their solutions for ridiculous amounts of money. My workplace has now hired an entire team and spent at least half a mil on a new software suite that will replace my solution eventually, after more dev work by this new team.
That was after I burned a year trying to figure out how in the hell I could programatically try to clean up a horribly misconfigured and mismanaged old SolarWinds Orion setup that had accumlated tech debt for years, only to be stymied because they don’t allow public discussion of their fucking database structure, and what I found out myself was batshit. Don’t trust software that use their own custom bastardization of SQL.
After those experiences I’m pretty damn content to stay in the land of “well documented and popular” and just work around the rough edges. Keeping up with patch and update news and delaying updates a little usually gives plenty of time to effectively opt-out by changing the settings before it hits our environment at large.
Fuck Microsoft’s bullshit, but at some point it’s the enemy you know, especially in a corporate environment. I’m no stranger to masochism through tech work, but I’ve gotten used to MS’s brand of fuckery, as a lot of us have.