This seems catastrophically bad.
Not for my wife, her solution was "you can mop the floors then".
A good employee finds work
Microsoft 365 Outage
121–130 of 166 posts
Re: Microsoft 365 Outage
#122Earlier quoted context omitted.
I have always been very sceptical of software moving to the cloud. Me too. After a disastrous episode with DropBox while travelling in foreign countries nearly a decade ago, I instituted my own File Server that's accessible via the Internet. All of my data is 'safe at home' with daily backups.
How do you secure it from unwanted access? I have been wanting to do something similar but I am unsure of the best practices
Either sftp/ssh with key-only logins (ie. no passwords), or Syncthing (depending on the volume of data, rate of changes, speed and costs of your network transits)
I now keep my primary 'work' and 'private' collections (10-30g each) and a large shared set (350g) synced across desktop & laptop, and also 3 off-site archive servers, using Syncthing. This includes a literal satellite connection for one site.
Re: Microsoft 365 Outage
#123Earlier quoted context omitted.
That is awful and why I have always been very sceptical of software moving to the cloud. Just yesterday I had a similar issue with Resharper, where our local licence server was down for the day. Luckily I was able to enable a 30-day trial. (and I guess Resharper isn't that mandatory to get work done)
> That is awful and why I have always been very sceptical of software moving to the cloud. Because you're less likely to brick your IDE than Microsoft is?
Haven't bricked emacs yet :-)
Re: Microsoft 365 Outage
#124Earlier quoted context omitted.
I have always been very sceptical of software moving to the cloud. Me too. After a disastrous episode with DropBox while travelling in foreign countries nearly a decade ago, I instituted my own File Server that's accessible via the Internet. All of my data is 'safe at home' with daily backups.
How do you secure it from unwanted access? I have been wanting to do something similar but I am unsure of the best practices
Not sure if it's a "best practice", but you can get a fairly Dropbox'ish experience by running a nextcloud/owncloud instance. It even comes in docker containers, so setup is quite simple.
Re: Microsoft 365 Outage
#125I'm reminded of what Leslie Lamport (who ironically went on to work for Microsoft) once observed:
"You know you have a distributed system when the crash of a computer you’ve never heard of stops you from getting any work done."
Re: Microsoft 365 Outage
#126There's an unconfirmed rumor that this outage has taken out 911 services in multiple parts of the US.
https://www.nbcnewyork.com/news/local/nationwide-reports-of-...
Re: Microsoft 365 Outage
#127"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable."
Ironically found on https://www.microsoft.com/en-us/research/publication/distrib...
The cloud is the ultimate rent-seeker's dream. The world's computing power in the hands of a few enormous companies... who then sell it to you in tiny pieces and charge for every little thing you use on their services. And when something goes wrong, you are powerless to do anything about it.
Re: Microsoft 365 Outage
#128"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable." Ironically found on https://www.microsoft.com/en-us/research/publication/distrib... The cloud is the ultimate rent-seeker's dream. The world's computing power in the hands of a few enormous companies... who then sell it to you in tiny pieces and charge for every little thing you use on…
This is why my new strategy is to avoid purchasing mission-critical components of my infrastructure from gigantic vendors.
For example, right now I could be using Azure SSO, which would have been free with Office 365 at the level we're bought in at, and then all of my other cloud products would be just as inaccessible as Office 365 is. Even when it is working, I could have an edge case issue and never see a feature added or a bug fixed to help me at all. Or, I could go with a 3rd party authentication company, and get a product that their company lives or dies on. My experience is that, if chosen well, you'll get a much better experience even though you have to do some legwork here and there to make things work together.
Re: Microsoft 365 Outage
#129Earlier quoted context omitted.
Yes, that's pretty nice. A clear, concise, and accurate description of the problem, noting that the change is bring reverted.
Absolutely! It's more about the presentation. "Title:" makes it look like a grade school book report.
It looks like it was copied from a text file, since if you view the source the actual formatting is there; but HTML's default whitespace/newline treatment causes it to turn into one big blob of text.
Re: Microsoft 365 Outage
#130I wish this were only limited to Office 365. It's most services that use authentication backed by Azure Active Directory.
https://status.azure.com/en-us/status
A few days ago a similar outage occurred with Google Accounts.