And at 40$ per employee per month, with all those employees now without access to the company (auth is not working so internal apps are going to be dead to), 50% of that for one month covers less than 50 minutes of downtime if your employees work 38 hours per week for 5000$ on average (and I do hope they make at least 2x more, since this is before tax).

The loss for a random due to MS software at this point is about 1400$ per seat (but probably at least double that) and rising.

Which is why every manager should now realize that their microsoft contract can never work as a valid disaster recovery option.

I tried to bring this out of our management staff when they were going all in on a SaaS that's 99% AWS backed. The SaaS was basically as integral is email is to many businesses to their line of work, and it was required to complete the business's b2b contracts which often had a turn around date. If the SaaS goes down, they're basically sitting idle and hitting contractual deadlines.

The response was basically, "we have a uptime garuntee and will pay out for downtime". But when it's clear _all_ of their clients have the same SaaS contract garuntee and a serious enough disruption would see _every_ client needing payment back, well, it's not much of a warranty is it.

Now I'm sure the SaaS has the redundancy in their system, but AI is the next deep integration that's going to hallow out a bunch of companies because some third party is just going to have a catastrophic loss somewhere down the line.

Yeah theres also another insurance policy which is you say “aw shucks man happy Thursday are we still down for golf this weekend, yeah we cant get that to you because Microsoft is down”.

they were in equity, so the problem would have been having to aw shucks a lot of martinis and golf clubs, but point taken.