November 12 Microsoft 365 and Outlook incident

Keep project work moving without creating a second problem

When Microsoft 365 interrupts email, files or project coordination, the answer is not personal email, a new file-sharing app or a weaker sign-in policy. CloudWorks Solutions’ practical continuity approach starts with Service Health, approved communication, existing offline access and a controlled handback when service returns.

Microsoft 365 outage business continuity means continuing approved work with existing local or functional services, controlled ownership and a deliberate reconciliation process—without weakening security or losing track of changes.

Status rechecked November 15, 2026: Microsoft lists EX1550543 and MO1550821 as service restored, with an incident end time of November 13 at 8:10 AM Pacific. Its final status describes a technical issue introduced during an earlier network-capacity upgrade and surfaced by a later network change—not cyber activity or AI agents. A full post-incident report is pending. Use this guide for recovery review and your next continuity exercise; check Health > Service health for any current tenant issue.

Start with facts

Confirm the incident and name the work that cannot wait

Microsoft’s Exchange incident covers Outlook on the web, desktop MAPI, Exchange ActiveSync and REST connections, with possible delivery delays. The broader incident affects particular Microsoft 365 features, not every feature in the same way. An administrator should check Health > Service health and record the incident IDs, timestamp and affected functions your firm actually uses.

Give one person responsibility for status updates and another for the critical-project list. Identify the client deliverable, model revision, consultant question, supplier approval or deadline that needs a decision today. Use the established business-phone or out-of-band process for urgent coordination and tell staff when the next update will arrive.

The first five records

  • Service Health timestamp
  • Affected projects and owners
  • Approved staff communication route
  • Offline files and editors
  • Next update and reconciliation time

Workaround matrix

Choose the safest option for each project task

Project taskOption to testBoundary
Review email or prepare a responseUse existing local email in classic or new Outlook on a managed workstation; save drafts or Outbox items.A new offline setting cannot retrieve mail still on the server. Do not remove accounts or repeatedly resend.
Edit a model, drawing or proposalUse an existing local or synced project copy, with one named editor and a change log.Do not create unmanaged copies or move files to personal storage. Very large or linked models need a deliberate version check.
Open a shared documentTest the direct Microsoft 365 file storage library or an already synced copy.Microsoft said direct Microsoft 365 file storage file access remained functional at the checked update; Exchange-dependent features may still fail.
Coordinate the project teamTest your normal core Teams chat or meeting, then use the approved business-phone or downtime route.Calendar scheduling and other Exchange-dependent functions can fail even when core messaging works.
Approve a supplier or client changeQueue it where possible or use the established independent verification and two-person process.Urgency is not a reason to approve new bank details, app consent or access from the same email thread.
Possibilities to test in your tenant, not guaranteed fixes for every user

Continuity in practice

Six steps that keep temporary work under control

01

Freeze risky changes

Do not disable MFA, Conditional Access, DLP, mail rules or sensitivity labels, install a recovery tool or forward work to personal accounts. Those actions do not repair Microsoft’s infrastructure.

02

Use what is already available

Check previously cached email, Office documents already on the device and synced project folders on managed devices. Microsoft explains new Outlook offline access, classic Cached Exchange Mode and working with Office files already on the device separately.

03

Assign every interim edit

Name one editor and one reviewer for each live document or model. Record the source version, changed sections and anyone who needs the result; do not let parallel copies multiply across devices.

04

Hold the security process

Keep help-desk verification, supplier call-backs and access approvals intact. Treat unexpected restoration links, MFA prompts or recovery tools as suspicious and report them through the normal route.

05

Log the incident window

Record delayed messages, unavailable features, security-console gaps, temporary procedures and client commitments. A good log tells the recovery team exactly what to reconcile.

06

Plan the handback before reconnecting

Decide who checks delayed mail, duplicate sends, file versions, permissions and linked models. Return each project to normal work only after its owner accepts the reconciled result.

Security during recovery

A green status icon is not the whole recovery check

Test the real workflows: sign-in, mailbox access, sending and receiving, direct file access, calendars and project integrations. Administrators can use Exchange admin center > mail flow > message trace for specific delayed messages, following Microsoft’s delivery guidance. Trace data can also be delayed.

Review sign-ins, new devices and MFA methods, inbox and forwarding rules, app consent, and late Safe Links, Defender, Purview and Intune events where your licenses provide them. Microsoft listed possible Safe Links and other security-function effects during this incident. No console alert is not proof that no action is needed.

Do not carry these forward

  • Personal email or file-sharing accounts
  • Disabled identity or data controls
  • Unverified password or MFA resets
  • Duplicate client messages
  • Unreconciled offline versions

Next-time readiness

Turn the incident log into a better continuity plan

Review which projects stopped, which offline copies helped, where ownership was unclear and whether any security function was delayed. Update the critical-project list, approved communication route, local-access expectations and reconciliation assignments. Then exercise the plan with the people who would actually use it.

Keep independent backups and run approved restore tests; synchronization is not the same as recovery. Our project continuity approach links interim work, restore order, vendor communication and failback. For identity, email and sharing fundamentals, see ACS Cyber’s Microsoft 365 security baseline.

Evidence to keep

  • Actual impact and timestamps
  • Approved workarounds and owners
  • Message-trace and security findings
  • Restore-test and reconciliation results
  • Post-incident actions and owners

Related CloudWorks resources

Build continuity around your projects

Continuity for a law firm

Need to protect client work and legal documents during a cloud outage? Explore ACS Legal IT’s illustrative law-firm continuity scenario for safe temporary work, document ownership and controlled recovery.

Outage questions

Microsoft 365 continuity FAQs

You can test your normal clients, but Microsoft listed Outlook on the web, desktop MAPI, Exchange ActiveSync and REST as potentially affected. Switching clients is not a guaranteed fix; previously synchronized local content may be more useful.

No. Use only existing offline access on approved, managed devices and your established project-continuity process. Personal accounts and unmanaged copies create security, privacy and version-control problems.

Do not promise either delivery or loss. Microsoft said delivery may be delayed. Review outgoing queues and message trace for specific messages after recovery, and use an approved independent route for urgent communications.

Start with the workflow that caused the most uncertainty in this incident. Name its owner, approved communication route, offline source, recovery order and reconciliation step, then test that plan with the people who would use it.

Your project continuity plan

Know what your team can do before the next outage

Bring one critical project, your current Microsoft 365 setup and your last restore-test result to a free 30-minute IT assessment. We will help you map the files, devices, communication and recovery checks that fit your firm—without promising uninterrupted cloud service.

Your privacy choices

The checks on this site run in your browser. Nothing you tap is saved or sent until you book. You can turn optional analytics off for this browser at any time.

When you book or tap our phone number, we also save which pages of this site you read and for how long, with a random browser ID and no name, email address or phone number, so our team can prepare for the call. Turning analytics off here (or sending GPC) stops this and keeps the tool summary out of your booking. We honor the Global Privacy Control (GPC) signal. Details are in our Privacy Policy.