Microsoft 365 Service Degradation
Is it fixed? Yes.
Resolved after 1 d 5 h. First reported Nov 13, 07:33 UTC, resolved Nov 14, 12:47 UTC. The vendor posted it on its status page first.
What happened
An ongoing Microsoft 365 service outage caused delayed or failed email notifications for merchants using custom SMTP with Microsoft 365, affecting Chargebee users. The incident has now been resolved.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Timeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on Bluesky post
⚠️ Chargebee is reporting an incident: Microsoft 365 Service Degradation
Source - Official statement
⚠️ Chargebee is reporting an incident: Microsoft 365 Service Degradation Monitoring: Due to an ongoing Microsoft 365 service outage, merchants using custom SMTP with Microsoft 365 may experience delayed or failed email notifications.
Source - Official statement
✅ Resolved: Chargebee - Microsoft 365 Service Degradation
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Evidence
2 reports · 2 BlueskyShow
- [1]Bluesky First report⚠️ Chargebee is reporting an incident: Microsoft 365 Service Degradation(opens the official status page in a new tab)
⚠️ Chargebee is reporting an incident: Microsoft 365 Service Degradation Monitoring: Due to an ongoing Microsoft 365 service outage, merchants using custom SMTP with Microsoft 365 may experience delayed or failed email notifications. We are monitoring the situation and will autom… t.lpl.dev/bpIhuf6
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments
- [2]Bluesky✅ Resolved: Chargebee - Microsoft 365 Service Degradation(opens the official status page in a new tab)
✅ Resolved: Chargebee - Microsoft 365 Service Degradation
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments90% match
FAQ
What happened in the Microsoft 365 outage?
An ongoing Microsoft 365 service outage caused delayed or failed email notifications for merchants using custom SMTP with Microsoft 365, affecting Chargebee users. The incident has now been resolved.
What is affected by the Microsoft 365 outage?
Microsoft 365. Also affected at the same time: Anthropic, OpenAI, Netlify, Resend.
When did the Microsoft 365 outage start and end?
It started Nov 13, 07:33 UTC and was resolved Nov 14, 12:47 UTC, after 1 d 5 h.
How do I get alerts for Microsoft 365?
Subscribe to the Microsoft 365 RSS feed for every new Microsoft 365 incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Microsoft 365 is down. Microsoft 365 feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 2 reports from 1 independent source, including the vendor’s own status page.