Keystone Licensing Update · Date (16/11/2026)
On 12–13 November 2026 (UTC), a Microsoft 365 connectivity incident disrupted Exchange Online/Outlook and dependent services in multiple regions. Microsoft linked the disruption to an infrastructure/network issue. Service credits are not automatic: each customer must demonstrate qualifying impact under the SLA applicable to its services. [4]
The incident numbers and approximate duration
| Microsoft incident | What was affected | Incident timeframe (UTC) |
|---|---|---|
| EX1550543 — Exchange Online | Mailbox access, Outlook and delayed mail | 12–13 Nov 2026 (approximately one day) |
| MO1550821 — Microsoft 365 suite | Exchange-dependent Microsoft 365 features | 12–13 Nov 2026 (approximately one day) |
| TM1550488 — Microsoft Teams | Separate Teams messaging/chat incident | 12 Nov 14:45 – 15:53 (68 min) |
Important: The Exchange Online and Microsoft 365 suite incidents spanned approximately one day across 12–13 November 2026 (UTC). Actual impact varied by region and tenant. Credit claims must use actual qualifying user-impact minutes, not an assumed global outage duration. The separate 68-minute Teams chat incident mainly affected services hosted in or routed through the Americas. If you operate worldwide, record user impact by region and time zone (including UTC offsets), and avoid counting overlapping minutes twice.
Step 1 — Collect the information Microsoft will ask for
| What to provide | Where to find it |
|---|---|
| Microsoft incident record | Microsoft 365 admin centre > Health > Service health > Issue history (7 or 30 days). Open each matching ID; save the status, impact, times and updates as screenshots/PDF. [1] |
| Tenant and subscription | Tenant GUID: entra.microsoft.com > Entra ID > Overview > Properties. Product/quantity: admin.cloud.microsoft > Billing > Your products. Add invoice, subscription ID or EA agreement/enrolment reference. [5][6] |
| Proof of your impact | Helpdesk tickets, affected functions, user count and locations, exact start/end with time zone or UTC offset, screenshots/errors, monitoring logs and troubleshooting attempted. Separate regional populations if impacted differently; state staggered recovery. [2] |
| Written request | Contact and legal entity; explicit “SLA service credit request” for the relevant incident(s). For CSP, email your provider from an address on the affected tenant domain. [2] |
Step 2 — Lodge via the correct purchasing agreement
| Your agreement | Exactly what to do |
|---|---|
| Enterprise Agreement (EA) | Admin: admin.cloud.microsoft > Help & support. Search “manage volume licensing – SLA credit”, then Contact Support. Supply EA agreement/enrolment number, workload, incident ID and evidence. Involve your LSP/Microsoft account team where appropriate; request case number and credit route. [3] |
| Microsoft Customer Agreement (MCA), direct billed | Admin: admin.cloud.microsoft > Help & support > enter “Microsoft 365 SLA credit – [incident ID]” > Contact Support (headset). Choose email/phone; attach the incident and impact evidence plus subscription/invoice. Request a case number. [3] |
| Cloud Solution Provider (CSP) | Email your CSP partner from the affected tenant domain. Ask its authorised direct/indirect provider to open a Partner Center support ticket with your evidence; indirect resellers cannot submit directly. Obtain the provider case number, submission date and acknowledgement. [2] |
Step 3 — Make the claim explicit
Subject: Microsoft 365 SLA service credit request | 12–13 Nov 2026 | [Incident ID(s)]
Please assess our SLA credit entitlement for [tenant GUID / legal entity], [affected service, product, subscription or EA reference]. Our users experienced [failed function] from [start] to [end, time zone], affecting [number and locations of users]. Attached: Microsoft Service health record, helpdesk/technical evidence, troubleshooting details and invoice/agreement reference. Please confirm the claim case number, any additional evidence, applicable SLA, eligible service fee base and how an approved credit will be applied.
Step 4 — Follow up and reconcile the result
Expect: Microsoft or the CSP provider may ask for logs, user counts, timestamps, specific features or billing evidence. Reply in the same case and retain a copy of every response. [2][3]
Decision: Ask for written approval or a specific rejection reason, the SLA metric used, eligible affected-service charges, percentage and calculated credit. An incident ID alone does not establish eligibility. [2][4]
Billing: For CSP claims, approved credits appear in the provider’s next invoice/reconciliation data; ask the partner how the customer credit will be passed through. For direct/EA, check the Microsoft billing/credit adjustment. Do not deduct an estimate from an invoice. [2]
CLAIM DEADLINES | November 2026 incident [2][4]
EA (Enterprise Agreement): Microsoft must receive the complete SLA claim by 31 December 2026, under the standard Online Services SLA.
MCA (Microsoft-direct): Same standard SLA deadline: 31 December 2026. Lodge with Microsoft support, including all required evidence.
CSP: Your authorised provider must submit within one month after the end of the relevant billing month (31 December 2026 if that month ends 30 November). Send evidence to your CSP earlier.
Check before lodging: Any negotiated terms, different billing cycles, and earlier partner cut-offs. An outage ticket alone may not constitute a complete SLA credit claim.
Worked calculation — illustrative only
1. Service uptime % = [(total eligible user-minutes - qualifying downtime user-minutes) / total eligible user-minutes] x 100. Total eligible user-minutes = eligible users x days in the SLA period x 1,440; downtime user-minutes = sum of (affected users x qualifying outage minutes).
2. Estimated credit = eligible affected-service charge x applicable SLA credit %. Use the Exchange Online availability tiers below as a guide; other workloads or functions may have different measurements and terms. [4]
| Exchange Online uptime percentage | Service-credit percentage |
|---|---|
| 99.9% or higher | No credit |
| 99.0% to below 99.9% | 25% |
| 95.0% to below 99.0% | 50% |
| Below 95.0% | 100% |
Example: In November (30 days), 1,000 eligible Exchange users have 43,200,000 user-minutes (1,000 x 30 x 1,440). If all 1,000 experience 18 hours of qualifying downtime, downtime is 1,080,000 user-minutes (1,000 x 1,080). Uptime = 97.50%, giving a 50% Exchange Online availability tier in this illustration. 8,000 in your invoice currency x 50% = 4,000 in that currency estimated credit, subject to Microsoft's verification. [4]
This is not 50% of the whole Microsoft 365 invoice. Microsoft validates the qualifying minutes, user population, feature-specific SLA, exclusions and eligible service-fee allocation. Use the currency and charges actually billed to the relevant subscription; do not claim a separate full-suite credit merely because multiple incident IDs appear. [2][4]
Conclusion
If the claim is difficult to lodge, the evidence is unclear or you need help reviewing Microsoft’s decision, please contact your Keystone Advisor. Please note that Keystone cannot guarantee the outcome as the final decision remains at Microsoft discretion
References
[1] Microsoft — How to check Microsoft 365 service health
[2] Microsoft — How and when to request a credit (Partner Center)
[3] Microsoft — Get support for Microsoft 365 for business, including volume licensing
[4] Microsoft — Service Level Agreements for Online Services (current and archived)
[5] Microsoft — How to find your Entra tenant ID
[6] Microsoft — What Microsoft business subscriptions do I have?
Keystone Negotiation is a global leader in Microsoft Negotiations Advisory Services. For independent advice on your Microsoft Enterprise Agreement renewal, Azure and M365 optimisation, or licensing questions, visit www.keystonenegotiation.com or contact [email protected]
Keystone Negotiation Pty Ltd | Level 17, 123 Pitt Street, Sydney NSW 2000
Version 3.40 | November 2026