Skip to content

What the November 2026 Microsoft Outage Taught Us

At about 11 a.m. Toronto time on Thursday, November 12, Outlook stopped delivering mail. Within the hour, Teams meetings were dropping, Copilot was unresponsive, and IT teams who went to check device status in Intune found they could not get in either. For most offices in the GTA, that was the middle of a normal working day, and it stayed broken well into Friday.

Microsoft says it was not a cyberattack, and it has not yet published a full root cause. But you do not need the root cause to learn from it. Here is what the outage taught us, and what we are changing with clients because of it.

The short answer: the outage proved that for most mid-sized businesses, Microsoft 365 is a single point of failure for email, meetings, files, security tooling and device management all at once. You cannot prevent a Microsoft outage, but you can decide in advance how your people will communicate, what your IT team can still do, and how long the business can run without it.

Moving off Microsoft is not the lesson. The lesson is that your continuity plan probably assumes your office or server fails, not your cloud provider. Add three things: a way to reach staff that does not run on Microsoft 365, offline copies of your critical runbooks and contacts, and a written decision on what the business does at the 2-hour, 8-hour and 24-hour mark.

Cloud concentration risk

Cloud concentration risk is the exposure a business takes on when many critical functions (email, chat, file storage, identity, security and device management) depend on a single cloud provider. When that provider has an outage, all of those functions fail together instead of one at a time.

What happened in the November 2026 Microsoft outage?

Problems began at about 16:00 GMT on Thursday, November 12 (11 a.m. Eastern). Outlook was hit hardest across web, desktop and mobile. Copilot was disrupted, and according to TechCrunch, Defender, Intune admin dashboards and some Cloud PCs were affected as well.

Microsoft described a large number of servers becoming “unexpectedly unavailable” and said there was no evidence of malicious activity. By Friday it was rolling back a network change, though it had not said whether that change was the cause. More than 12 hours in, Microsoft reported only “marginal success” restoring service.

74

Countries and territories that logged Outlook, Teams and Copilot problem reports on Downdetector within about an hour (Al Jazeera, Nov 13 2026)

~18 hrs

Approximate downtime before traffic began returning to Microsoft’s services, per network analyst Doug Madory of Kentik (TechCrunch, Nov 13 2026)

This was also not a one-off. It follows a January 2026 Microsoft 365 outage that lasted nearly 10 hours across North America. Two major multi-hour incidents in one year is enough to plan around.

Lesson 1: Is Microsoft 365 a single point of failure for your business?

For most companies with 50 or more staff, yes. Email, Teams, SharePoint and OneDrive files, sign-in, endpoint security and device management very often all come from the same Microsoft tenant. On November 12 several of those failed at the same time, which is very different from losing one tool.

Consolidating on Microsoft 365 is still the right call for most businesses: it is cheaper, more secure and easier to manage than a patchwork of vendors. The trade-off is that you have concentrated your risk, so your continuity planning has to account for it. Map which business functions depend on the tenant and you will usually find the list is longer than expected.

Business functionTypical Microsoft dependencyFallback to have ready
Staff communicationTeams, OutlookSMS or phone tree, conference bridge from a different provider
Customer contactOutlook shared mailboxesPhone lines and a holding message on the website
Files and documentsSharePoint, OneDriveLocally synced copies of critical files on key devices
Device managementIntuneOffline runbook and a list of who has local admin access
Security monitoringDefenderIndependent monitoring (firewall logs, MDR provider)

Lesson 2: How do you reach staff when Teams and Outlook are down?

You need a communication channel that does not run on Microsoft 365, set up before the outage. If your only way to tell 150 people “email is down, here is what to do” is an email or a Teams post, you have no way to tell them.

The simplest version is a current list of staff mobile numbers held outside the tenant, and a group SMS or phone tree that a manager can trigger. Add a conference bridge from a different provider for leadership, and decide in advance who sends the first message and what it says.

Write the first message now, while nothing is broken. Something like: “Microsoft email and Teams are down across the world. This is not a problem with our systems. Use phones for urgent client contact. Next update by [time].” A pre-approved message gets sent in five minutes instead of after a 40-minute discussion.

Lesson 3: Can your IT team still work when the admin portals are down?

Often not as much as you would think. During this outage, administrators reported being unable to reach Intune dashboards. The tools you would use to diagnose and respond were part of the outage.

The fix is unglamorous: keep the critical information somewhere that does not depend on Microsoft. That means an offline or printed copy of your incident runbook, vendor support numbers, your Microsoft tenant ID and support contract details, and emergency (break-glass) admin account procedures. If your runbook lives only in SharePoint, it went down with everything else.

Warning:

Do not “fix” an outage by loosening security. When sign-in is flaky, it is tempting to switch off MFA or relax Conditional Access to get people working. That does not fix a provider outage, and it is easy to forget to switch back on.

Lesson 4: Does a non-cyberattack outage still create security risk?

Yes. Microsoft said there was no sign of malicious activity, but large public outages are a gift to phishing crews. Expect emails and texts pretending to be Microsoft “service restoration” notices, fake password reset links, and calls from people claiming to be Microsoft support.

Tell staff plainly: Microsoft will not email, text or phone them individually about this outage, and IT will not ask for passwords. Also note that with Defender affected, some of your usual security screening may have been degraded for part of the outage. That is a good reason to have monitoring that does not depend on the same vendor, such as firewall logging or an independent managed detection and response service.

Lesson 5: Does your disaster recovery plan cover a cloud provider outage?

Most do not. Traditional disaster recovery plans are written for a fire, a flood, a ransomware attack or a failed server: something that happens to you, where you control the recovery. In a provider outage you control none of the recovery. Your plan is about how the business keeps working while you wait.

Do not count on the SLA to cover the cost either. Microsoft’s Service Level Agreement for Online Services pays out in service credits against your subscription, not compensation for lost productivity or lost sales. The commercial risk of a day without email sits with you.

Here is the short framework we use to add a provider outage to a client’s continuity plan:

List what runs on the tenant: Every business function that stops if Microsoft 365 stops, including the less obvious ones like scanners that email documents, phone systems tied to Teams, and line-of-business apps that sign in with Microsoft accounts.

Set decision points at 2, 8 and 24 hours: Decide now what happens at each. At 2 hours: staff message, switch client contact to phones. At 8 hours: notify key clients, defer deadlines. At 24 hours: leadership call on contractual or regulatory notifications.

Build the out-of-band kit: Staff phone list, SMS or call tree, alternate conference bridge, offline runbook and vendor contacts, all stored outside Microsoft 365.

Assign owners: Name who declares the incident, who sends the staff message, who talks to clients, and who watches the Microsoft service status page for updates.

Run it once a year: A 30-minute tabletop exercise (“it is 11 a.m. and Outlook and Teams are down, what do we do?”) will surface the gaps faster than any document review.

Should you move away from Microsoft 365 after this outage?

For almost every mid-sized business, no. Every major cloud provider has outages, and running a second, parallel email and collaboration platform costs far more than the occasional bad day it would protect you from. Switching vendors swaps one concentration risk for another.

The better investment is resilience around the platform: the out-of-band communication plan, offline runbooks, independent security monitoring, and a tested continuity plan. That is a few days of work, not a migration project, and it pays off the next time any vendor you depend on goes down.

The November 12 outage was Microsoft’s problem to fix, but how long your business stood still was yours. Companies that had a backup way to reach staff, offline runbooks and pre-agreed decision points lost hours of convenience. Companies without them lost a day of work. Use this outage as the reason to close that gap before the next one.

If you want a second set of eyes on how your business would handle the next one, our team can review your Microsoft 365 setup and your backup and disaster recovery plan together, and give you a short list of what to fix first. An incident readiness workshop is also a practical way to run the tabletop exercise above with your leadership team.

Sources

Managed IT Services for Law Firms: An Ontario Guide

Your firm has grown past the point where one IT person, or a partner’s nephew, can keep up. You have 50, 100, maybe 200 people, a document management system nobody fully understands, lawyers working from court and home, and trust account transfers going out every week. Then a client’s general counsel sends over a security questionnaire, and nobody knows how to answer half of it.

This guide covers what managed IT services for law firms should include, which Ontario obligations drive those requirements, and how to tell a provider who understands legal practice from one who just supports offices.

The short answer: managed IT services for a law firm should cover everything a general business needs (help desk, patching, backups, network) plus four things specific to legal practice: protecting privileged client data, securing the money movement around trust accounts, enforcing ethical walls inside your document system, and giving you evidence you can show clients, insurers, and the Law Society. If a provider can’t speak to all four, they are supporting your office, not your practice.

For an Ontario law firm, IT is part of professional responsibility. The Law Society expects technological competence, PIPEDA requires breach records, and LAWPRO’s cybercrime coverage has a ceiling. Managed IT should be scoped around those obligations, not just around keeping computers running.

Managed IT Services for Law Firms

Managed IT services for law firms is an arrangement where an outside provider runs a firm’s technology for a fixed monthly fee: user support, security, backups, cloud systems, and legal applications such as document management and practice management software. Unlike general office IT support, it is built around client confidentiality, trust account security, conflict and ethical wall controls, and records retention.

Why law firm IT is different from general office IT

Law firm IT is different because the data is privileged, the money moves through trust accounts, and the regulator holds individual lawyers responsible for how both are protected. A manufacturer that loses its email for a day loses productivity. A law firm that leaks a client file can face a negligence claim, a Law Society complaint, and the loss of the client relationship in one event.

Three things make legal environments harder to run than they look:

  • Access is matter-based, not department-based. Who can open a file depends on which matters they work on, and conflicts mean some people must be actively blocked from files their own colleagues use every day.
  • The work happens everywhere. Lawyers draft at home, review on phones between court appearances, and share files with opposing counsel and clients outside the firm.
  • Retention rules are long. Closed files have to be kept, findable, and protected for years after the matter ends, which makes backup design a professional obligation, not just a disaster plan.

When we take over IT at a mid-size firm, the pattern we see most often is not a missing firewall. It is permissions that grew by accident: shared folders opened “temporarily” years ago, former associates still in distribution groups, and a document system whose security model nobody has reviewed since it was installed.

What Ontario rules and obligations shape law firm IT

Ontario law firms answer to three sets of expectations that directly affect IT: the Law Society of Ontario’s professional conduct rules, federal privacy law, and the terms of their LAWPRO insurance. None of them hands you a technical checklist, which is exactly why firms need someone who can translate them into controls.

ObligationWhat it says, in plain termsWhat it means for your IT
LSO Rules of Professional Conduct, Chapter 3Lawyers must be competent, and the commentary on competence now covers understanding the technology they use. Confidentiality duties apply to client information wherever it is stored.Partners need to be able to explain, in plain language, how client data is protected. That means documented controls, not “the IT guy handles it.”
PIPEDA breach rulesBreaches that create a real risk of significant harm must be reported to the Privacy Commissioner and affected people, and every breach must be recorded and kept for 24 months.You need logging and monitoring good enough to know a breach happened, what was touched, and when.
LAWPRO cybercrime sublimitThe mandatory policy includes a $250,000 cybercrime sublimit, which LAWPRO itself describes as a modest safety net.A serious incident can exceed that cover. Separate cyber insurance, and the security controls insurers require for it, are part of the plan.
Good to know:

If your firm holds health information (personal injury, medical malpractice, disability claims), Ontario’s PHIPA can also apply to how that information is handled. Ask your provider how they treat health records differently from other client files.

The biggest cyber risk to law firms is the money, not the files

The most expensive attack on an Ontario law firm is usually not ransomware. It is a fraudster who gets into, or convincingly fakes, an email thread and redirects a trust account payment to their own bank account. LAWPRO has repeatedly warned about a rise in schemes that trick lawyers and law clerks into wiring funds out of trust accounts, especially around real estate closings and private mortgages.

These attacks work because they look like normal business. The email comes from a real client’s address (after their mailbox is compromised) or a near-identical domain, the timing matches a closing, and the request is a routine change to payment instructions. Recovery after the wire leaves is rare.

27%

of law firms surveyed reported having experienced a security breach at some point (ABA TechReport 2022, Cybersecurity)

Good managed IT reduces this risk on both sides: technical controls (multi-factor authentication on every mailbox, alerts on suspicious mailbox rules, filtering of look-alike domains) and process controls (a mandatory phone call-back to a number already on file before any change to payment instructions). We go deeper on the email side in our guide to business email compromise.

Check your mailbox rules today. In nearly every email compromise we investigate, the attacker’s first move is a hidden rule that forwards or deletes messages containing words like “wire,” “trust,” or “closing” so the real conversation never reaches the lawyer. Your IT provider should be alerting on new forwarding rules automatically.

What managed IT for a law firm should include

A complete managed IT service for a law firm covers day-to-day support, security, and the legal applications that the firm runs on. Use this table to check a current or proposed agreement. Anything in the right-hand column that isn’t in writing usually isn’t happening.

AreaGeneral office ITLaw firm IT should add
Help deskBusiness-hours supportAfter-hours coverage around filing deadlines and trial prep; support for court and remote work
Identity and accessUser accounts and passwordsMulti-factor authentication everywhere, matter-based permissions, ethical wall enforcement, same-day offboarding
Email securitySpam filteringImpersonation and look-alike domain protection, mailbox rule alerts, encrypted email for client files
MonitoringAntivirusEndpoint detection and response with a 24/7 SOC (security operations centre) that can tell you exactly what an attacker touched
BackupsNightly backupImmutable backups that ransomware can’t delete, tested restores, retention matched to file-retention obligations
ApplicationsMicrosoft 365Document management (iManage, NetDocuments), practice management, billing, e-discovery tools
ReportingTicket countsEvidence for client security questionnaires, cyber insurance renewals, and partner meetings

Offboarding deserves special attention in legal. Associates and clerks move between firms often, and a departing lawyer who keeps access to a shared drive or a synced phone is a confidentiality problem. We explain why the job isn’t finished on the last day in why user offboarding doesn’t end when an employee leaves.

Ethical walls need to exist in your systems, not just in a memo

An ethical wall (a screen that blocks specific people from specific matters because of a conflict) only protects the firm if the technology enforces it. A memo telling a lateral hire not to open certain files does nothing if their account can still open them, search them, and sync them to a laptop.

Done properly, a wall is applied in the document management system, mirrored in any shared drives or Teams sites that hold matter files, and logged so the firm can prove nobody behind the wall accessed the matter. When we review legal environments, the gap is almost always the second step: the document system is locked down, but copies of the same files live in a Teams channel or a personal OneDrive that the wall never reached.

Warning:

Microsoft 365 Copilot and other AI assistants search everything a user is allowed to see. If your permissions are loose, an AI tool will surface walled-off or confidential documents in answers. Fix permissions before turning on AI tools, not after.

How to choose a managed IT provider for a law firm

The right provider can explain your obligations back to you in plain language and show how each one maps to a control they run. Use these steps to evaluate any provider, including your current one.

Ask about trust account fraud first: have them describe how they would stop a redirected wire. If the answer is only “spam filtering,” keep looking. You want both technical alerts and a payment-verification process.

Ask how they enforce ethical walls: they should be able to explain how a wall is applied across the document system, Microsoft 365, and devices, and how access is logged.

Ask who is watching at 2 a.m.: confirm there is a 24/7 SOC with the authority to isolate a compromised device immediately, not just an alert emailed to someone who reads it Monday.

Ask for a restore test: request proof that a closed matter from several years ago can be found and restored. Untested backups are the most common surprise during an incident.

Ask for a sample report: it should be something a managing partner can read and something you could hand to an insurer or a client’s security team.

If your firm already has an internal IT manager, you don’t have to replace them. A co-managed IT arrangement lets your person keep ownership of the legal applications and relationships while a provider covers security monitoring, after-hours support, and the infrastructure work.

Cyber insurance makes the controls non-negotiable

Because LAWPRO’s cybercrime cover stops at $250,000, most mid-size firms carry separate cyber insurance, and those insurers now ask detailed questions about multi-factor authentication, endpoint detection, backups, and incident response plans. A wrong answer on the application can give the insurer grounds to deny a claim later.

Your managed IT provider should help complete those applications accurately and keep the controls in place all year, not just at renewal. We cover the claim side of this in will your cyber insurance actually pay out when you need it?

Managed IT for a law firm should be judged on four questions: can it stop a redirected trust payment, enforce an ethical wall, prove what happened during an incident, and produce evidence for clients and insurers? A provider that answers all four with specifics is supporting your practice, not just your office.

BALANCED+ has supported Ontario businesses since 1994, with a 24/7 SOC and a 15-minute critical response SLA. If you want an outside view of where your firm stands, see how we work with law firms and legal practices, or start with our managed IT services overview.

Sources

What a 24/7 SOC Actually Does at 2 a.m.

Most security tools are very good at noticing things. The problem is what happens next. At a lot of organizations with 50 to 300 staff, an alert at 2 a.m. goes to an inbox and gets read at 8:30. If it was real, the attacker had six and a half hours. If it came in on a Friday night, they had the weekend.

This post walks through what a 24/7 security operations centre (SOC) actually does overnight, three after-hours attacks it is built to stop, and five questions to ask any provider who says they offer round-the-clock monitoring.

The short answer: a 24/7 SOC is a team of security analysts who watch your firewall, laptops, servers and Microsoft 365 accounts through the night. Most of their time goes to ruling out normal activity. When something is real, they act in minutes: locking a stolen account, cutting an infected laptop off the network, or removing a mailbox rule set up for fraud. That matters because most ransomware is launched when nobody is in the office.

An alert is not a response. If nobody can act on an alert until morning, your security tools are recording the attack, not stopping it. A real 24/7 SOC closes the gap between detection and action at the hours attackers prefer.

Security Operations Centre (SOC)

A security operations centre is a team of security analysts, and the tools they use, that monitors an organization’s systems around the clock. A SOC collects alerts from firewalls, endpoints (laptops and servers), cloud services and identity systems in one place, decides which alerts are real threats, and responds to contain them. A “24/7 SOC” means a person is watching and able to act at every hour, including nights, weekends and holidays.

Why do attackers strike after business hours?

Attackers strike after hours because nobody is watching. An attack that would be spotted and stopped at 11 a.m. on a Tuesday can run for hours at 2 a.m. on a Sunday. Criminal groups know this, and they plan around it.

88%

of ransomware cases had encryption deployed outside business hours (Sophos Active Adversary Report 2026, 661 incident response and MDR cases)

The same Sophos research found that 79% of data theft activity also happened outside the workday, and that identity techniques (stolen or abused logins) were the root cause in 67% of cases. In Canada, the Canadian Centre for Cyber Security’s National Cyber Threat Assessment 2025-2026 names ransomware as the top cybercrime threat to Canadian organizations.

Put those together and the risk is plain: the most damaging attacks start with a login, and they get finished at night.

What does a SOC analyst actually do overnight?

Most of a SOC analyst’s night is spent deciding what is not a threat. Every network produces a steady stream of alerts: a sales rep signs in from a hotel, a backup job runs long, a laptop downloads a large update. Almost all of it is normal, and each one has to be ruled out quickly and correctly.

That takes context. It is why, when we onboard a new client to our managed detection and response (MDR) service, the first step is learning what normal looks like in their environment: who signs in from where, which systems talk to each other, when backups run. Without that baseline, an analyst can’t tell an attack from a staff member working late, and the client gets either missed threats or a flood of false alarms.

It is also why “our IT team keeps an eye on alerts after hours” rarely works. One or two IT people can’t check every alert properly overnight and still do their day jobs. The alerts either go unread or get waved through.

Good to know:

A SOC is only as good as what it can see. If it watches your firewall but not your Microsoft 365 sign-ins or your laptops, it will miss the login-based attacks that cause most incidents. Ask any provider for the full list of sources they monitor.

What does an after-hours attack look like?

After-hours attacks rarely look dramatic. They look like small, quiet changes that only stand out to someone who knows what normal is. The three examples below are typical patterns, not stories about any one client.

1:47 a.m. A login that looks right but isn’t

Someone signs in to your controller’s Microsoft 365 account with the correct password. The multi-factor prompt gets approved, often because the controller tapped “approve” on a stray notification earlier. The location is a city nobody on your team is in. The analyst checks: the controller is asleep in Mississauga. The account is locked, every active session is signed out, and the password reset is waiting for the controller in the morning.

3:10 a.m. A laptop starts rewriting files

A laptop left on in the office starts changing hundreds of files on a shared drive, fast. That is how ransomware behaves. The analyst cuts that one laptop off the network so it can’t reach anything else. One machine needs rebuilding. The shared drive doesn’t.

Saturday, 11:20 p.m. A quiet rule in someone’s mailbox

A new rule appears in an accounts payable mailbox: copy anything with “invoice” in it to an outside address, then hide it. Nobody gets a pop-up for this. It is how business email compromise and payment fraud start. The rule is removed, the account is secured, and on Monday your team knows exactly which emails were exposed.

In all three, the damage is decided in the first hour, not the next morning. We see the same thing in phishing investigations: the useful evidence is in the trail the attacker leaves after the first click, which we covered in Following the Phishing Attack Path.

What is the difference between 24/7 monitoring and 24/7 response?

24/7 monitoring means something is watching. 24/7 response means someone can act. Many offers use the first phrase and imply the second, and the gap only shows up on the night you need it.

At 2 a.m.Alert-only monitoring24/7 SOC with response
Who sees the alertAn automated rule, then your inboxA security analyst, in real time
Who decides if it’s realYour IT team, in the morningThe analyst, using a baseline of your normal activity
What happens to a stolen loginIt stays active until someone reads the emailAccount locked and sessions signed out
What happens to an infected laptopIt keeps reaching shared drivesIsolated from the network
What you get in the morningA pile of unread alertsA plain account of what happened, what was done, and what needs your decision

Tools like a SIEM (a system that collects and searches security logs) are part of this picture, but on their own they still need someone to act. We compared the two approaches in MDR vs SIEM: Which One Does Your Business Need?

What should you ask a 24/7 SOC provider before you sign?

Ask for specifics in writing. “24/7 protection” on a sales page tells you nothing about what happens at 2 a.m. These five questions do, and they apply to every provider, us included.

Who looks at the alert? A named team of security analysts, or an automated rule that forwards it to you?

Can they act without waking you? Locking an account or isolating a laptop at night, under rules you agree on ahead of time.

What is the response time on critical issues? A number, not “fast”. Ours is a 15-minute critical response SLA.

What do they watch? The firewall only, or also laptops, servers and Microsoft 365, where most login-based attacks start?

What do you get in the morning? A plain report of what happened, what they did, and what still needs your decision, plus a root-cause report after any confirmed incident.

Agree the after-hours rules before anything happens. Write down which actions the SOC can take on its own (lock an account, isolate a device, block an address) and which need a call to a named person on your side. Then put that person’s mobile number in the agreement. That one page removes most of the hesitation on the night it matters.

For a broader checklist that covers the rest of the agreement, see How to Evaluate an MSP Before You Sign.

Should you build an in-house SOC or outsource it?

For most organizations with 50 to 300 staff, outsourcing the SOC is the realistic option. Covering every hour of the week takes several trained analysts once you account for nights, weekends, holidays and sick days, and a week has 168 hours. Few mid-market IT budgets stretch to that.

Outsourcing doesn’t mean handing over control. Your IT team keeps the decisions about your systems; the SOC covers the hours and the alert volume they can’t. For the full comparison, read SOC as a Service vs. In-House SOC.

Warning:

If a cyber insurance questionnaire or an auditor asks how security alerts are handled outside business hours, “they go to an inbox” is a hard answer to give. Know your real answer before someone asks.

How to find your own after-hours gap

Pick one alert type, such as a sign-in from a new country, and trace it. Where does the alert go? Who sees it at 2 a.m. on a Saturday? What can they do about it, and how long would that take? If the answers are “an inbox”, “nobody” and “Monday”, you have found the gap.

Attackers plan around your office hours. A 24/7 SOC is worth paying for only if someone on it can act at those hours, sees your logins and laptops as well as your firewall, and tells you plainly in the morning what happened.

BALANCED+ has provided managed IT and cybersecurity since 1994, and our 24/7 SOC watches client environments every hour of the year. If you want to see where your after-hours coverage stands, start with our cybersecurity services or book a consultation. It’s a conversation, and you’ll leave knowing what to fix first.

Sources