Microsoft 365 Outage Disrupts Teams Interviews and Outlook: Server Failures Stall Recovery

Here's what's confirmed, what's still unclear, and what to do if the outage cost you an interview, a meeting or a business day.

What actually broke​

The Economic Times led with the human side of the story. Microsoft's own explanation, as reported by ABC News in Australia, was about server capacity. Microsoft said a large number of servers unexpectedly became unavailable, which pushed their load onto the servers that were still running. It also said the extra load was not caused by an overall rise in traffic. A process on the affected servers that handles secure connections then became overwhelmed, and those servers stopped processing requests.

That's a cascade: some servers go down, the rest take on their work, and then they fail too. It also explains why recovery kept stalling. Servers that were brought back online could become unresponsive again once traffic returned to them.

Other reporting shows how wide the impact was:

• BleepingComputer said that in a Microsoft 365 admin center advisory tracked as MO1550821, Microsoft confirmed that customers may be unable to connect to multiple services, including Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot, and Microsoft Defender XDR.
• ABC News reported that Microsoft's Service Health Status site also listed Planner, To Do, Intune, Purview and Power BI, and that Authenticator was affected.
• NBC News reported that consumer services were hit too. Microsoft's notice said the issue "impacts Outlook.com, OneDrive, OneNote To Do, Teams, and Microsoft 365 for the web." NBC added that by 11 p.m. ET Thursday, Microsoft's status pages also listed Windows 365, cloud printing services, and mobile device management programs as having issues.
• BleepingComputer also noted that the outage came after a separate Microsoft Teams incident earlier Thursday that caused an outage for users in North and South America, and that Microsoft has not indicated whether the two incidents are related.

Reports of the start time differ. The Economic Times said around noon on the US East Coast. Al Jazeera said problems with Microsoft products began at about 16:00 GMT on Thursday. TechRadar put it at around 1pm ET / 6pm GMT on Thursday November 12. These are probably different moments: when user reports started, when Microsoft acknowledged the problem, and when it peaked. Until Microsoft publishes a final root-cause report, treat any exact start time as approximate.

Section summary: Microsoft blames servers that failed unexpectedly and an overloaded secure-connection process, not a traffic surge. The impact went well past Outlook and covered both business and consumer services.

Not a cyberattack, so far​

Big outages always bring rumours of hacking. ABC News reported that Microsoft said there was no sign of malicious activity. Australian Home Affairs Minister Tony Burke said Microsoft told him it did not believe a cyberattack was the cause. TechRadar's live coverage carried the same message from Microsoft, saying there was "no indication" of a cyberattack.

Australia's National Cyber Security Coordinator looked into the incident. That's what governments normally do after a disruption this large, and it doesn't suggest an attack happened. Burke also said Australia had activated a cyber agreement with Microsoft so that Australian services would be given priority during restoration.

The recovery: good news, then bad news​

This part of the story is a chain of status updates that kept contradicting each other.

1. The Economic Times, citing CNN, reported that at 1:59 a.m. GMT Microsoft said it was seeing positive results from restarting affected infrastructure and restoring server availability one piece at a time.
2. At 3:13 a.m. GMT, Microsoft said the changes it had applied were not working as expected.
3. ABC reported that just after 9 a.m. AEST, Microsoft said a gradual recovery had begun. About an hour later, it said some restored servers were becoming unresponsive again.
4. Al Jazeera reported that Microsoft had only "marginal success" in restoring its most widely used workplace services, more than 12 hours after a global outage knocked out Outlook and disrupted Teams and Copilot for users in 74 countries.
5. In an update at 8:05 a.m. ET Friday, BleepingComputer reported that Microsoft says its services are gradually recovering from the widespread Microsoft 365 outage, with improvements in email access and delivery.

By Friday night in Australia, ABC said access was gradually returning in Asia-Pacific, with improvement in Europe and the US. Even so, Gulf Business reported that Microsoft had yet to confirm full restoration of Outlook and other affected Microsoft 365 services. "Recovering" is not the same as "resolved." If your mailbox is still slow or not syncing, the outage may not be over for you yet.

Section summary: Recovery went in fits and starts. Restored servers kept falling over under load, so Microsoft brought traffic back gradually. Full resolution had not been confirmed when this was written.

The interview that didn't happen​

The Economic Times headline points to reporting from ABC, which spoke with Manny Flores, a job seeker in Melbourne. He couldn't get into Teams for a job interview, and it was moved to the following week. He told ABC he had been unemployed for almost a year and had reached a final interview. That kind of delay hurts a lot more than a backed-up inbox.

ABC collected other examples as well. An Adelaide business owner couldn't process invoices because Authenticator was down. An occupational therapist was locked out of Outlook. A patient's medical scans were cancelled because referrals arrive by email. A flight to Papua New Guinea was held while someone carried printed pre-flight documents out on foot. Schools asked parents to phone in absences. TAFE students using Teams virtual classrooms couldn't attend classes.

These are individual accounts. They show the kinds of problems people had, not a count of how many were affected. Downdetector numbers need the same caution. ABC reported a peak of more than 120,000 Outlook reports and more than 45,000 Microsoft 365 reports on Downdetector's US site. The Economic Times cited about 130,000. Both are complaints sent to an outage tracker, not confirmed totals of affected users.

What to do if you missed an interview or meeting​

The Economic Times gives the obvious advice, and it's correct: contact the person or organisation through another channel and ask to reschedule. A few more details can help it go smoothly:

• Get in touch quickly, and not through the broken service. Call the recruiter or hiring manager, or use a personal email account that isn't affected. If you only have a company switchboard number, use that.
• Point to the public outage, briefly. Something like: "Microsoft 365 and Teams were down worldwide on November 12–13, and I couldn't join the meeting." The outage was covered by major news organisations, so the interviewer has very likely heard about it, and may have been locked out too.
• Take a screenshot of any error messages or failed joins. You probably won't need it, but it costs nothing.
• Suggest a backup format for the new slot, such as a phone number you can be reached on if the video link fails.
• Don't panic about how it looks. Employers aren't obliged to reschedule. Still, a missed interview during a widely reported global outage is about as understandable as reasons get.

A practical note from Al Jazeera: there is little users can do themselves, as the problem lies with Microsoft's servers rather than their own devices. It added that the desktop version of Outlook may still show emails already downloaded, while Teams chats and calls have largely continued working. So check your cached desktop Outlook for that interview invite and the recruiter's phone number before assuming everything is gone. Reinstalling Office or resetting your PC won't fix a problem on Microsoft's servers.

For IT admins: check Service health before troubleshooting​

When helpdesk tickets pile up, the first question is whether the problem is yours or Microsoft's. Microsoft's own Learn documentation explains how to check:

1. Sign in to the Microsoft 365 admin center with an admin account and go to Health > Service health. Users with the Service Support admin or Helpdesk admin role can view it too.
2. Look under Active issues Microsoft is working on. Each issue shows affected services, user impact, status and an update feed. This is where IDs such as MO1550821 appear.
3. Know the terms. An advisory means some users are affected but the service is still available. An incident means the service, or a major function of it, is unavailable.
4. If you can't get into the admin center, Microsoft points to its public Service Health Status page and the @MSFT365Status account on X. Microsoft's incident-readiness guidance treats these as backups, because the in-tenant view shows the services your tenant actually uses.
5. If your problem isn't listed, use Report an issue in Service health.
6. Set up alerts under Customize > Email (up to two addresses per admin) for future incidents. The Microsoft 365 Admin mobile app can also send push notifications.

One caveat from experience: if Exchange Online is down, email alerts about Exchange Online being down may not arrive. Send those notifications to addresses outside your tenant, or rely on the mobile app.

The bigger lesson​

Concentration risk is real. ABC quoted Niusha Shafiabady, head of IT at Australian Catholic University, who argued that systems are getting smarter but not necessarily more resilient. Microsoft has dealt with large outages before. In January 2023, NPR reported that Microsoft confirmed the outage was a result of a network change and not outside actors. Each event leads to the same discussion, and many organisations still don't have a plan for running without email.

Microsoft's incident guidance says it publishes a post-incident report with root-cause details for major events. Expect one for this outage. In the meantime, use it as a test of your own setup. Do you have an agreed fallback channel for urgent conversations? Is there a phone tree? Can your staff sign in to anything if Authenticator is down? It's better to answer those questions now than during the next outage.

Bottom line: If Teams cost you an interview, call the employer, explain briefly and reschedule. If you run a tenant, check Service health first, set up alerts that don't depend on Exchange, and keep an eye out for Microsoft's root-cause report.