Employees in a professional office staying connected through alternative communications during a Microsoft cloud outage

Microsoft Outage: Could Your Business Be Entitled to a 50% Service Credit?

The recent Microsoft 365 outage lasted more than 12 hours for many businesses. That may mean some organisations can claim a substantial service credit. But the incident also raises a bigger question: what should your IT provider be doing when a critical cloud supplier fails?

12+ HOURSCould that mean a 50% SLA credit?
The business question

First, check the credit. Then check the response.

Even Microsoft can fail. Businesses lost normal email and collaboration for a working day or longer. If materially affected, ask your provider to investigate a service credit. Then ask how they kept people working.

No technology provider is completely resilient.
The commercial question

Could Your Business Claim a 50% Microsoft Service Credit?

Microsoft's financially backed SLA includes these availability bands for Exchange Online, Teams, SharePoint and OneDrive. Credits cover the affected service, not the whole plan or lost revenue and productivity.[Source]

November has 720 hours. Twelve hours of full unavailability gives 98.33% availability, potentially the 50% band. Microsoft compares affected user-minutes with total service user-minutes, so partial impact and staggered recovery matter. Copilot uses different measures.

Below 99.9%

25%

Potential service credit

Below 99%

50%

Potential service credit

Below 95%

100%

Potential service credit

Standard user-minute availability bands. Apply the highest qualifying band.

Service-credit estimator

November 2026: 30 days, 720 hours. Assumes stable user numbers, the same impact duration for affected users and no scheduled downtime. Use service fees, not the full bundled licence price.

Estimated monthly availability
98.33%
Potential SLA band
50%
Illustrative potential service credit
£1,000.00
Affected user-minutes
72,000

The band uses unrounded availability. Final eligibility depends on Microsoft's service-specific SLA and recorded impact.

Use recorded unavailability, not global incident duration. Desktop Outlook problems alone do not establish an Exchange claim: its availability SLA covers sending or receiving email through Outlook Web Access.[Source]

What actually happened?

Global disruption, uneven recovery

The incident began on 12 November 2026 at around 17:25 GMT. Outlook and Exchange Online were affected globally, alongside Teams functions and Copilot. Many businesses experienced more than 12 hours of disruption. Recovery progressed unevenly, and the global incident continued into 14 November, when Microsoft announced full recovery. That timeline does not mean every user lost every service throughout.[Source]

Microsoft described a technical issue associated with a network capacity upgrade following a recent network change. It restored service gradually, checking stability at each stage. On 13 November it said the incident was not related to cyber activity or AI agents. Microsoft promised a fuller post-incident review.[Source]

Teams remained usable for some affected users, not everyone. For a business leader, the useful record is which services your people could actually access, when disruption began and when normal work resumed.

Credits are not automatic

Ask the question while the evidence is fresh

Ask your Microsoft provider, rather than wait for a credit. November calendar-month Microsoft 365 claims and supporting information are due by 31 December 2026. Start sooner. Partner Center requires impact evidence and the customer's request, with an evidence email from the affected tenant's domain.[Source]

  • Tenant GUID and incident reference
  • Affected service and subscription
  • Start, end and duration
  • Affected users and locations
  • Errors and impact evidence
  • Licensing and service fees
Own the escalation

Who Actually Deals With Microsoft When Something Goes Wrong?

Wavex is a Microsoft Direct Bill Cloud Solution Provider. For Wavex CSP services, we work directly with Microsoft. Indirect resellers are not poor providers, but a distributor or indirect provider adds another commercial and support layer.[Source]

Microsoft accepts CSP credit requests from direct and indirect providers, not indirect resellers. Ask: 'Are you our Microsoft CSP, and can you submit the claim directly?'[Source]

Direct CSP model

Customer
Wavex
Microsoft

Indirect reseller model

Customer
IT provider
Distributor / Indirect Provider
Microsoft
Know who owns submission, not just who sends your invoice.
Keep people informed

If Email Goes Down, How Does Your IT Provider Email You?

Without updates, employees wonder whether this is a cyberattack or rebooting will help. Wavex's APEX App displays user notifications; our SMS gateway sends messages at scale. Updates should acknowledge outages, explain workarounds, report progress, flag security risks and confirm recovery.

Microsoft-dependent channels

Email unavailable

Teams: only where still operational

Independent communication

  • APEX App
  • SMS gateway
  • Phone
Separate the emergency channel from the failed service.
Your emergency communication method should not rely entirely on the service that has failed.
Approved alternatives

Knowing There Is an Outage Is Not Enough. People Still Need to Work.

Where Teams works, use internal chat, channels or mobile Teams away from desktop email. For external conversations, create a meeting, send joining details through an agreed route such as SMS, independently verify the person and exchange documents through controlled sharing. Teams is a conditional workaround, not an independent Microsoft contingency.

Keep security intact

Attackers Know Your Normal Processes Have Changed

Stress makes alternative login links, password resets, personal email, unusual file-sharing, changed payment instructions and fake support calls sound plausible. Keep approval rules and cybersecurity controls intact.

Names, employers, email addresses and dates of birth are weak checks. Wavex can send a unique-number popup to the caller's registered PC or Mac. Reading it back adds evidence of device access. Exceptional circumstances need independent fallback checks, not waived verification.

  1. 1

    Call support

  2. 2

    Registered-device popup

  3. 3

    Read unique number

  4. 4

    Engineer checks identity

Registered-device access adds evidence to the identity check.
An outage should make identity verification more important, not less.
Protect the information

Choose file-transfer alternatives before the outage

Free sharing sites can create data residency, retention, access and encryption problems. Use approved services meeting UK GDPR requirements. Overseas hosting is not automatically unlawful: restricted international transfers need a compliant route, such as adequacy or appropriate safeguards. Agree alternatives before a client deadline.[Source]

Do not solve an email outage by creating a data-protection problem.
Understand the spend

You Cannot Claim or Optimise Costs You Cannot See

Costs span Microsoft 365, Azure, backup, security, SaaS and separate invoices. Wavex dashboards show licence usage and allocation, recurring spend, consumption, invoices, trends and drill-down. Complete IT Visibility supports everyday optimisation and identifying affected-service fees instead of guessing from a bundled bill.

IT cost visibility

Illustrative layout

Licences

Usage and allocation

Recurring spend

Service-level fees

Cloud consumption

Azure and SaaS

Invoices

Trends and drill-down

Review service-level costs before estimating a claim.
Beyond availability

Supplier failure is not always an outage

Microsoft suffered an availability failure. ConnectWise Cloud Backup, formerly SkyKick, suffered unauthorised application credential access. ConnectWise said encrypted, isolated archives were preserved, with no indication of compromise. Backups and restores resumed for re-authorised tenants from 28 October; other platform restoration continued in its 4 November update.[Source]

Check tenant authorisation and successful snapshots. Outages, compromised identities, vulnerabilities, commercial failures and broken integrations need different responses. Include MSP tool architecture in supplier-risk planning.

An owned response

What Good Looks Like During a Major Supplier Outage

A good provider should do more than forward Microsoft's status page. Agree action owners, updates and recovery checks.

  1. 01Confirm
  2. 02Communicate
  3. 03Work Around
  4. 04Secure
  5. 05Recover
  6. 06Claim
  7. 07Improve
Seven stages, from first confirmation to lasting improvement.
  1. 01

    Confirm the problem

    Local, tenant-specific, supplier-wide or security-related?

  2. 02

    Communicate independently

    Use unaffected channels.

  3. 03

    Give safe workarounds

    Name approved alternatives.

  4. 04

    Maintain security

    Warn about attacks.

  5. 05

    Verify identities

    Check unusual requests.

  6. 06

    Coordinate recovery

    Test users, integrations, backlogs.

  7. 07

    Assess commercial impact

    Identify services and spend.

  8. 08

    Submit eligible claims

    Assign ownership and deadlines.

  9. 09

    Learn from the incident

    Test improved continuity arrangements.

The Wavex approach

Resilience Is More Than Keeping Systems Running

Wavex combines Direct CSP, APEX App, SMS, 24x7 real engineers, verification and cost dashboards with managed IT, cybersecurity, supplier management, incident response and continuity planning. Suppliers can fail. Our job is to make sure clients know what to do.

Resilience does not mean nothing ever fails. It means failure does not leave your people wondering what to do next.

Further reading

Understand your supplier dependencies

SkyKick / ConnectWise: Is Your Data at Risk?

Supplier security and backup recovery.

Read the Insight

Cybersecurity Is No Longer About Buying Tools

Understand risk, not just products.

Read the Insight

What Happens to Your IT While Nobody Is Watching?

Operational ownership beyond office hours.

Read the Insight

MSP Technology Security: Tool Architecture and Blast Radius

Examine privileged supplier dependencies.

Read the Insight

Nine questions to ask your provider

How would you contact our employees if Microsoft 365 was unavailable?

Request tested independent channels, current contact details and an owner for updates.

What approved workarounds would you recommend?

Expect approved alternatives and safe instructions, including when Teams is unavailable.

How do you verify people who call your helpdesk?

Expect checks beyond public information, registered-device verification and controlled fallbacks.

Can you identify which of our users and services were affected?

Request service-specific impact and actual downtime, not the global outage timeline.

Are you our Microsoft CSP?

Confirm each subscription's supplier and commercial owner. Different services may have different providers.

Are you Direct CSP, an indirect provider or an indirect reseller?

Ask who sits between you and Microsoft for escalation and claims.

Who submits our Microsoft SLA claim?

Name the submitting provider. Agree evidence, deadlines and submission acknowledgement.

Can you immediately show what we spend on affected services?

Request service-level fees, licence allocation and invoices, not just whole-plan totals.

What did you change after the last major outage?

Look for updated communications, tested workarounds and assigned actions, not just lessons logged.

Were You Affected by the Microsoft Outage?

If your organisation experienced prolonged disruption, Wavex can help you understand the affected services, review your licensing and determine whether a Microsoft SLA claim may be appropriate.

Talk to Wavex Explore Cybersecurity & Compliance

Discuss your Microsoft outage claim

Tell us which services were disrupted and what you would like to review.

No commitment required. Your enquiry is handled under our privacy policy.