Oh the horror
I was going to be sarcastic, talking about not being able to get into one's email, but I read that Outlook users can (must?) use OWA as a workaround and that really is a horror.
Microsoft is investigating an issue that is keeping some users from being able to fully use the Microsoft 365 cloud service and Teams admin centers on Thursday. The problem kicked off this morning with Redmond saying it was looking into errors within its caching infrastructure. In an advisory, the Windows goliath wrote "some …
I'm no great fan of the web outlook client either, but it does have one advantage: you needn't be running Windows on your PC to use it.
At previous $JOB the Corporate IT Central Bureaucracy[tm] dictated only Microsoft for email, but allowed that the OWA client was acceptable. This allowed those of us with Linux to carry on ... for a while.
Eventually they brought in some Cisco(?) LAN access "solution" which dictated only Microsoft systems allowed, and that was that. Lost some good engineers from that sort of thing.
Seemed a bit self-defeating for a company with products based on Linux. I doubt management has connected the dots between folks leaving and their shrinking market share....
My philosophy is to only use computers I own and manage myself. To this day I've never had to rely on any computer that was owned, built or managed by someone else and it is that feeling that keeps the cockles warm.
Tbh, I'm not a big fan of people, don't trust 'em. Much safer to do everything yourself.
To this day I've never had to rely on any computer that was owned, built or managed by someone else
Ah, so you don't look at webservers, use only hard IP addresses so you don't need to resolve FQDNs and run your own email server? OK, the last one is actually possible provided you have a static IP address (it's a lot more challenging with a dynamic IP address, though not impossible), but I suspect you get my point.
What I would agree with is that - given the above - you have to think hard about which risks you're willing to accept beyond that, especially if they are resources managed by world's largest provider of security problems, Microsoft..
"Rely on" != "make use of"... If I lost all network connectivity at Chez Chris, I'd still be able to e.g. use my locally installed Office apps to update my locally stored documents, whereas if I was reliant on the web-based versions of those apps to edit cloud-stored documents then I'd be up a certain malodourous waterway without a means of boat propulsion.
That's the issue here - it's one thing to lose the ability to watch some cat videos in your lunch break if someone elses system fails, it's quite another to lose the ability to do the fundamental stuff that justifies having the computer on your desk in the first place.
Yes, but when the cloud companies go to the pointy-haired-bosses and say why are you paying for computers, space to store them, and engineers to keep them running? Instead, outsource to us. We'll pay for the computers, space, and engineers, and rent them to you for a very modest sum.
So, they move to the cloud, sell their computers and their building, and fire the engineers. Just then, as if by magic, the cloud provider starts raising their prices and charging by the transaction. The resulting bill is DOUBLE what it used to be, and they're now in the grip of another company for their existence. And they can't go back, because they jettisoned everybody who knew how the old system worked.
But by this time, the CEO has been rewarded for cutting costs, and the stockholders have taken their money and run.
Happens.Every.Single.Time.
"Someone remind me of the advantages of relying on other people's computers the cloud"
Well, I heard somewhere that your system will never run out of resources so long as you have enough money because "the cloud" can scale to meet your demands, so there will never be outages due to CPU or other over utilisation of resources :-)