# Docs check — Office Watch and WIRED worked examples — Nov 2026

**Exchange Online (Office Watch 1,805-minute example): 95.82% uptime in Nov 2026 -> 50% service credit ≈ £14.00 off next bill. File by Thu 31 Dec 2026 (direct). 100% needs 356 more minutes of downtime this month at 2 affected users. SharePoint Online (WIRED 18-hour example): 97.50% uptime in Nov 2026 -> 50% service credit ≈ £12.44 off next bill. File by Thu 31 Dec 2026 (direct). 100% needs 1,081 more minutes of downtime this month at 1 affected users.**

> Consider waiting until Mon 30 Nov 2026 (month end) before filing: further downtime this month could move you to the next credit tier, and your deadline (Thu 31 Dec 2026) allows it. Third-party tactic — Office Watch: "Why not wait until November 30 to make a claim. If (heaven forbid) there’s more trouble, it might be possible to make a larger claim. [third-party tactic, Office Watch]"

Provider: microsoft365 · Purchase route: direct · Month: 2026-11 (30 days, 43,200 minutes) · As of 2026-11-16 · Currency GBP (symbol only)

## Per-service result

| Service | Users | User-minutes | Downtime user-min | Uptime % | Tier | Credit | Fee | Credit amount | Eligible? |
|---|---|---|---|---|---|---|---|---|---|
| Exchange Online (Office Watch 1,805-minute example) | 2 | 86,400 | 3,610 | 95.82% | < 99% → 50% | 50% | £28.00 | £14.00 | Yes |
| SharePoint Online (WIRED 18-hour example) | 1 | 43,200 | 1,080 | 97.50% | < 99% → 50% | 50% | £24.88 | £12.44 | Yes |

Totals: fees £52.88 · credit £26.44 · days added 0

- Exchange Online (Office Watch 1,805-minute example) next tier: below 95% needs 356 more minutes of downtime this month.
- Note (Exchange Online (Office Watch 1,805-minute example)): Fee shown is an example fee for illustration; replace it with the amount on your invoice.
- SharePoint Online (WIRED 18-hour example) next tier: below 95% needs 1,081 more minutes of downtime this month.
- Note (SharePoint Online (WIRED 18-hour example)): Fee shown is an example fee for illustration; replace it with the amount on your invoice.

## Deadlines

- Incident month ends (uptime is measured over this month): **Mon 30 Nov 2026** (Microsoft SLA)
- Service Health history keeps about 30 days — export your evidence before: **Sun 13 Dec 2026** (third-party: Office Watch)
- Direct claim deadline — Microsoft must receive the claim by: **Thu 31 Dec 2026** (Microsoft SLA)

## Incidents

- EX1550543 (exchange-online, posted as incident): 2026-11-12T10:05 → 2026-11-13T16:10 UTC (1,805 minutes, affected: all)
- WIRED-18H-EXAMPLE (sharepoint-online, posted as incident): 2026-11-05T00:00 → 2026-11-05T18:00 UTC (1,080 minutes, affected: all)

## Claim ticket (ready to paste)

```text
Subject: SLA Credit Service Incidents: EX1550543/WIRED-18H-EXAMPLE

I am the IT administrator for Northwind Surveyors. I am claiming a service credit under the Service Level Agreement for Microsoft Online Services.
Organisation: Northwind Surveyors
Tenant ID: {tenant_id}
Purchase route: Bought direct from Microsoft
Affected subscriptions purchased through CSP: No

Service affected (affected resource name): Exchange Online (Office Watch 1,805-minute example)
- Incident ID: EX1550543 (from the Service Health Dashboard)
  1. Description of the incident: Our users were affected by incident EX1550543 for Exchange Online (Office Watch 1,805-minute example). Description of errors that occurred during the incident: {describe_the_errors_users_saw}
  2. Time and duration of downtime: 2026-11-12T10:05 to 2026-11-13T16:10 (UTC), 1,805 minutes. In UTC: 2026-11-12T10:05:00.000Z to 2026-11-13T16:10:00.000Z.
  3. Number and location(s) of affected users: All 2 of our 2 licensed users, at {office_location}.
  4. Our attempts to resolve the incident at the time: {describe_what_you_tried — e.g. checked Service Health, tested other clients/networks, raised ticket {support_ticket_number}}
  Uptime calculation for Nov 2026:
  User Minutes: 43,200 minutes × 2 users = 86,400. Downtime: 3,610 user-minutes. Uptime Percentage: (86,400 − 3,610) / 86,400 × 100 = 95.82%.
  This is in the "< 99% → 50%" band. I request a 50% service credit = £14.00 against Applicable Service Fees of £28.00 for Exchange Online (Office Watch 1,805-minute example) for Nov 2026.

Service affected (affected resource name): SharePoint Online (WIRED 18-hour example)
- Incident ID: WIRED-18H-EXAMPLE (from the Service Health Dashboard)
  1. Description of the incident: Our users were affected by incident WIRED-18H-EXAMPLE for SharePoint Online (WIRED 18-hour example). Description of errors that occurred during the incident: {describe_the_errors_users_saw}
  2. Time and duration of downtime: 2026-11-05T00:00 to 2026-11-05T18:00 (UTC), 1,080 minutes. In UTC: 2026-11-05T00:00:00.000Z to 2026-11-05T18:00:00.000Z.
  3. Number and location(s) of affected users: All 1 of our 1 licensed users, at {office_location}.
  4. Our attempts to resolve the incident at the time: {describe_what_you_tried — e.g. checked Service Health, tested other clients/networks, raised ticket {support_ticket_number}}
  Uptime calculation for Nov 2026:
  User Minutes: 43,200 minutes × 1 users = 43,200. Downtime: 1,080 user-minutes. Uptime Percentage: (43,200 − 1,080) / 43,200 × 100 = 97.50%.
  This is in the "< 99% → 50%" band. I request a 50% service credit = £12.44 against Applicable Service Fees of £24.88 for SharePoint Online (WIRED 18-hour example) for Nov 2026.

Attached / available on request: {screenshots_error_messages_service_health_exports_and_PIR}
Contact: {your_name_role_and_email_on_this_tenant_domain}
```

## Evidence checklist

- [ ] A detailed description of the Incident (SLA claim item i).
- [ ] Information regarding the time and duration of downtime (SLA claim item ii).
- [ ] Affected resource names — the services above (SLA claim item iii).
- [ ] The number and location(s) of affected users (SLA claim item iv).
- [ ] A description of errors that occurred during the incident (SLA claim item v).
- [ ] Tenant ID — replace {tenant_id} with your tenant GUID. Partner Center also requires: "Customer tenant ID and outage ID (from the Service Health Dashboard) must be provided."
- [ ] Incident IDs from Service Health: "You can find the identifier for the outage incident on the Service Health page in the Microsoft 365 admin center."
- [ ] Evidence that proves customer impact (screenshots, error messages, Service Health exports, the Post-Incident Review when published). Export it before the Service Health history window closes.
- [ ] Descriptions of your attempts to resolve the incident at the time of occurrence (Partner Center required information).
- [ ] Where to file (as written in research): direct customers — "admin center, Help & support | Contact Support" (third-party, Office Watch, https://office-watch.com/2026/microsoft-365-outage-sla-claim/); CSP customers — your provider creates the Partner Center support ticket ("Create a support ticket in Partner Center", official Partner Center guidance).

## Next steps

1. **Mon 16 Nov 2026** — Today: save your evidence — screenshot or export the Service Health incident pages, user error messages and the times your users lost and regained the service — export it before Sun 13 Dec 2026 (Service Health keeps about 30 days — third-party, Office Watch).
2. **Mon 16 Nov 2026** — Confirm the fee for each affected service from your invoice. If you buy a suite, confirm the share of the suite fee for each service — the SLA gives no fixed split, and credits are prorated to the affected service only.
3. **Mon 30 Nov 2026** — Wait until month end before filing if the next credit tier is within reach — more downtime this month counts towards the same claim (third-party tactic, Office Watch).
4. **Thu 31 Dec 2026** — File the claim ticket with Microsoft support (admin center, Help & support | Contact Support — third-party wording, Office Watch) so Microsoft receives it by the deadline. Keep the case number and a copy of everything you sent.
5. **Thu 31 Dec 2026** — Check the next bill for the credit. Credits are applied to service fees (Microsoft) or as days added / a monetary equivalent (Google monthly online billing); they are not automatic and the provider decides every claim.

---
Outagepilot · Daily Ships · Planning aid, not legal advice. Credit maths follows Microsoft's and Google's published SLA terms (checked 16 Nov 2026); the provider decides every claim.
