AskKhamsay.
← Blog

· Khamsay Phimmasanh-Baig, AskKhamsay

When Microsoft 365 Goes Quiet: What the Outage Taught Us About Cloud and AI

By Khamsay Phimmasanh-Baig, AskKhamsay

AskKhamsay cover: When Microsoft 365 Goes Quiet, What the Outage Taught Us About Cloud and AI

What do you do when Outlook won't open, Copilot stops answering, and your calendar acts like it's never met you?

On Thursday, November 12, a lot of businesses found out the hard way.

Microsoft 365 started having problems around midday Eastern time. Outlook went down. Copilot went quiet. Calendar access became a problem. By Friday morning, Microsoft was still working through recovery, region by region.

Microsoft said a number of servers had unexpectedly gone offline, putting additional strain on the servers that were left. It said this wasn't caused by a traffic spike and that it had no indication of malicious activity.

I've been in IT since 1998. Outages aren't new. What's new is how much we now pile into one place.

The detail most people missed

Teams chats and online meetings mostly kept working.

But scheduling meetings and accessing calendar information could still be affected.

Why? Because Teams and Exchange are connected. Your meeting link might still work, but if the calendar invitation containing it is sitting in an inaccessible Exchange mailbox, getting to that link becomes another problem.

A service can be up and still useless to you.

That's what happens when one cloud ecosystem connects email, files, meetings, and AI. One disruption can ripple across the whole operation.

Here's what I'd sort out before the next one.

1. Pick a backup meeting spot

When the usual tools go down, people scatter. Someone texts. Someone emails from Gmail. Someone waits for someone else to fix it.

Pick one backup, like Zoom or Google Meet, and create a standing link.

Save it somewhere you can reach without signing in to Microsoft. A note on your phone works. So does a sticky note, honestly.

Then tell everyone: if we can't get into our usual meeting, we meet here.

Nobody should have to guess.

2. Decide who talks to clients

Your clients don't know Microsoft is having a bad day. They just know you haven't answered.

Decide ahead of time:

A quick call or text beats silence every time.

One person. One job. Keep people in the loop.

3. Keep your must-have files on your device

Cloud storage is great until you can't reach it.

Pick the few files you can't work without. Think current proposals, open invoices, key procedures, and important contacts.

In OneDrive, use Always keep on this device for critical files. Set this up before an outage, and verify those files are actually downloaded and accessible offline.

Keep that device locked down and those files current.

You don't need a copy of everything. You need the few things that let you keep working.

Your AI has dependencies too

Copilot isn't magic running on its own. It relies on Exchange and the other Microsoft services that hold your email, calendar, and files.

During this outage, Microsoft warned that Copilot might not load or might be unable to access email, calendar, and files.

So before you build your day around an AI assistant, ask:

If the answer to the last one is "no," that's your homework.

Nothing in the cloud has perfect uptime. Plan like you know that.

Your turn

How much of your business runs through one provider? And what's your plan when it doesn't?

Tell me in the comments. I'm genuinely curious how people are handling this.

Don't guess. Ask Khamsay.

PROMPT. CREATE. IMPACT.

Sources

Based on reporting available Friday morning, November 13, 2026. Microsoft's service status may change as recovery continues.