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.


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.


Check the Microsoft status page for updates first, then decide whether to manually switch to the backup channel—don't just wait.
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.
The key is still assessing the scope of impact—don't rush to shift the blame.
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.
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.