HuaRenCa
Back to Forum
Community

Microsoft/Exchange is down too...

ymz
ymz

1 week ago

Our company's IT was already dealing with an incident in our own systems, and halfway through, we discovered Outlook had blown up too...

Indian colleague: I just checked X...MS has confirmed this issue, not our/my fault.

Microsoft/Exchange is down too...

Microsoft/Exchange is down too...

5
1.0K

Comments (5)

Your avatar
Sign in to comment
jason71lee4
jason71lee41 week ago

Who's going to eat the lost billable hours from this delay? We'll be arguing over the invoice again at the end of the month.

轻松和谐
轻松和谐1 week ago

Check the Microsoft status page for updates first, then decide whether to manually switch to the backup channel—don't just wait.

嫂子的强求
嫂子的强求1 week ago

If you have a publicly committed SLA, I'd suggest first confirming whether this incident qualifies as force majeure under the contract before deciding whether to proactively notify customers. The precondition is that the contract actually includes a liability exemption clause for cloud provider outages—otherwise, sending a notice rashly could end up putting you in a tight spot.

刘石峰
刘石峰1 week ago

The key is still assessing the scope of impact—don't rush to shift the blame.

leoning
leoning1 week ago

That Indian guy's "not our fault" line is pretty funny, but can you share the confirmation screenshot from X so I can take a look? I want to check whether it's the same batch.