Microsoft 365 went down on Thursday evening. Here is what to check so you do not lose enquiries or bookings.
The short answer: A global Microsoft 365 outage began on Thursday 12 November 2026. The BBC reported that Teams, Outlook and Copilot were affected, and that users may have been unable to view certain files or calendar details. CNBC reported that SharePoint was also among the services that were largely down, and that the server issues lasted more than 20 hours, with email still recovering on Friday. The BBC reported that Outlook problem reports on Downdetector peaked at nearly 140,000 around 18:00 GMT. CNBC reported that Microsoft said it had not detected malicious activity.
What happened in the Microsoft 365 outage?
Microsoft said a number of its servers had become "unexpectedly unavailable", which strained the rest of its systems, according to the BBC. CNBC reported that some servers were failing automated health checks, and that Microsoft first put it down to a traffic surge in part of its infrastructure and a problem with a component that processes server health. Around 4pm US Eastern time on Thursday, CNBC reported, Microsoft said it had validated an alternative service health check method and was bringing servers back online in stages.
The BBC says Microsoft warned that some users may have been unable to view certain files or calendar details, and that Copilot might not work properly. Microsoft also warned that services which had come back "can become unresponsive again", and that customers "in any region" could be affected.
In a Friday update at around 9am US Eastern time (14:00 in the UK), CNBC reported that Microsoft was "continuing to see improvements in service availability, with email queues significantly reduced and approaching normal levels". Intermittent problems were still expected.
The BBC understands there is no indication it was a cyber-attack. CNBC reports that Microsoft said it had not detected any malicious activity.
Who else was affected?
It was not only Outlook users. The BBC reported that OpenAI was looking into an issue with its connections to Microsoft's services, which had stopped some of its tools working as expected. CNBC reported that the NHS said some of its services were affected, and that a hospital group serving South West London and Surrey warned that calls could face long waits.
CNBC also reported that Air India "temporarily rerouted" emails so it could keep receiving customer messages. That is a big company doing something any small firm can plan for.
Will I lose emails sent to me during the outage?
Microsoft said it was prioritising efforts to preserve emails delayed during the recovery. According to CNBC, it extended the timeout window, so delayed emails keep trying to deliver, to 48 hours, to help protect messages.
That is not a promise that every delayed email will arrive, so it is still worth checking a second place where enquiries are stored, and looking through anything that landed later with a Thursday timestamp. An enquiry that arrives a day late can look old and get skipped.
What should you check this week?
These checks are my own advice, not Microsoft's. None of them needs new software or technical skill.
Do your website enquiries rely only on email?
If your contact form sends an email to your Outlook inbox and nothing else, an email outage means enquiries pile up where you cannot see them. It is worth having the form save each enquiry somewhere else as well, such as a spreadsheet or your CRM (customer list), so you can still see who got in touch and call them back.
Can you see tomorrow's bookings without your calendar?
If your diary sits in Outlook and Outlook will not load, you can lose sight of who is coming in. Keep a second view of upcoming appointments, for example in your booking system or a simple daily list sent to your phone the evening before. For a studio or venue, that can be the difference between a calm morning and turning people away by mistake.
Do your automations tell someone when they fail?
Lots of small firms now have automations that pass enquiries or bookings between their tools. When one of those tools goes down, a badly set up automation just stops quietly and nobody notices for days. Ask whoever built yours whether it sends an alert when a step fails, and who that alert goes to. I have also written about admin work you can automate first.
Do you know how you'd tell customers?
If clients cannot reach you by email, they will try somewhere else. Decide now where you would post a short update, such as a banner on your website or a post on your Google Business Profile, and make sure your phone number is easy to find on your site.
What does this outage mean for a small business?
Thursday's outage was not anyone at your business getting something wrong. It is a reminder that most small firms now depend on a handful of very large suppliers. As James Owen, managing partner of Digital Risks at consultancy Control Risks, told CNBC, it "shows the importance of proper recovery planning in the case of an IT outage."
For a small business, recovery planning does not have to mean a thick document. It mostly means making sure an enquiry or a booking cannot get stuck in one place. That is how I set up the automations I build for clients: if one tool goes down, the information still lands somewhere a person can see it.
If you would like a second pair of eyes on where your enquiries go when email fails, you can book a call with Tom. You can also get in touch in writing. The work is priced on a call.
Sources
- BBC News, "Global Microsoft outage affecting tens of thousands of users", Adam Goldsmith, Jessica Lamb and Osmond Chia, 12 to 13 November 2026, accessed 13 November 2026: https://www.bbc.com/news/articles/c5gm3g9ldz8xo
- CNBC, "Microsoft says email queues 'approaching normal levels' as Outlook issues persist", Jenni Reid and Samantha Subin, published 12 November 2026 and updated 13 November 2026, accessed 13 November 2026: https://www.cnbc.com/2026/11/12/microsoft-outage-outlook-aws-google.html
Frequently asked questions
When did the Microsoft 365 outage start, and how long did it last?
CNBC reported that connectivity problems began shortly before 1pm US Eastern time on Thursday 12 November 2026, which is shortly before 18:00 in the UK. It described the server issues as lasting more than 20 hours, with email still recovering on Friday. The BBC reported that Outlook problem reports on Downdetector peaked at nearly 140,000 around 18:00 GMT on Thursday.
Which Microsoft 365 services were affected?
The BBC said Teams, Outlook and Copilot were affected by connectivity problems, and that users may have been unable to view certain files or details on their calendar apps. It also said messaging and online meetings were largely functional at one point. CNBC reported that Outlook (email and calendar), SharePoint and Copilot were largely down during Friday's Asian business day, the European morning and into the early US hours, and that Teams was among the services affected.
Will I lose emails sent during the Microsoft 365 outage?
CNBC reported that Microsoft was prioritising efforts to preserve emails delayed during the recovery, and that it had extended the timeout window, so delayed emails keep trying to deliver, to 48 hours to help protect messages. That is not a promise that every delayed email will arrive. Check anything that landed later with a Thursday timestamp, and look at a second place where enquiries are stored, not only the inbox.
Was the Microsoft outage a cyber attack?
The BBC understands there is no indication the outage was caused by a cyber-attack. CNBC reported that Microsoft said it had not detected any malicious activity. At the time this was written, Microsoft had not published an official post-incident report, so the cause should be treated as what the company has said so far, as reported by those two outlets.
Why did the Microsoft 365 outage happen?
The BBC reported that Microsoft said a number of its servers had become "unexpectedly unavailable", which strained the rest of its systems. CNBC reported that Microsoft first put it down to a traffic surge in part of its infrastructure and a problem with a component that processes server health, and that some servers were failing automated health checks. CNBC also reported that, around 4pm US Eastern time on Thursday, Microsoft said it had validated an alternative service health check method. The official cause is not yet in a post-incident report.