All of this came eight days after the November 12 Microsoft 365 outage, when Exchange Online was unreachable for most of a day. Admins have a long week behind them, and it helps to keep these problems apart.
Friday's Downdetector reports: a signal, not a diagnosis
IBTimes Australia reported that Downdetector users flagged problems with Outlook on Friday. Outlook covers email, calendar, contacts and tasks on web, PC, Mac and mobile. Several details were missing:
- How many users were affected: no confirmed count
- What the symptoms were: no breakdown
- The cause: not established
- A resolution time: none given
Downdetector also flagged Microsoft 365, Apple Pay and Starbucks on the same day, with nothing to suggest the reports were linked. Downdetector counts people who report problems. It does not measure an outage directly, so a spike tells you that people are unhappy, not why.
Section summary: As of the IBTimes report, no Microsoft-confirmed, Outlook-wide outage stood behind Friday's reports.
A narrower, confirmed problem: attachments in new Outlook
A Microsoft 365 service-status mirror run by Earlham College showed Exchange Online in a "service degradation" state on Friday. It listed incident EX1561765: some users may be unable to open or upload attachments, or view inline images, in the new Outlook client. The mirror's latest update for that entry was timestamped 21:41 UTC on November 20.
This is a defined problem with a defined symptom. That doesn't mean it explains every complaint on Downdetector, and the available evidence doesn't give its full scope or a fix date. If your problem is specifically attachments or inline images in new Outlook, though, this incident is the one to watch.
The same mirror listed other active Microsoft 365 issues that day. One was IT1549049, under which some Windows devices enrolled in Intune may get policies, apps and other changes late. Another was MP1507695, which covers delays in Purview Audit log results. Neither is an Outlook problem, but admins juggling everything at once should know about them.
The contacts bug: MO1489432 and a moving finish line
The second strand of the story is Microsoft advisory MO1489432, and it has dragged on for a while.
What users see
Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. Microsoft's description is specific: this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
This is not a general Outlook contacts failure. If your whole address book has vanished in a way that doesn't fit that pattern, look elsewhere.
What went wrong
Microsoft's root-cause statement, reproduced on the University of Pennsylvania's mirror of Microsoft incident reports, says a contact-processing component split some Profile Based Contacts (PBCs) from their associated profiles when certain contact information wasn't explicitly stored. That made the affected contacts show up blank. The advisory gives a start time of September 25, 2026, at 07:30 UTC. Microsoft's first public validation of the cause appeared on October 6.
The repair timeline so far
The full update history from Microsoft's Service Communications feed, as mirrored by Flowbotics, shows this has been hard to fix:
| Date (2026) | Microsoft's status |
|---|---|
| Oct 6 | Cause validated; fix in development and internal validation |
| Oct 7 | Fix deployment began; completion expected Oct 14 |
| Oct 19 | First fix fixed only a small share of affected contacts; second fix in validation |
| Oct 26–28 | Second fix deployed; about 90% of affected contacts processed |
| Oct 30 | About 95% processed |
| Nov 2 | Over 99.5% processed; some users still affected |
| Nov 5 | Original recovery complete, but a separate underlying code issue is blocking some contacts |
| Nov 13 | Per-user code fix rolling out; completion due Nov 20 |
| Nov 20, 14:16 UTC | Deployment still ongoing; completion now expected Nov 24 |
Correction to Friday's coverage
IBTimes Australia said the rollout was due to finish Friday, November 20. That was Microsoft's November 13 target. Microsoft's latest update, posted at 14:16 UTC on Friday, says it is still deploying the code fix to the remaining affected contacts on a per-user basis and now expects to finish by Tuesday, November 24, 2026. Microsoft's next update is scheduled for 15:00 UTC that day. It's a target, not a promise, and the date has already moved once.
Microsoft's own support staff are pointing confused users to this advisory. On a Microsoft Q&A thread where a user described contacts disappearing from Teams after signing out, the answer said what you're seeing is likely related to an ongoing service incident and directed them to review this incident report in the Service health menu in Microsoft 365 admin center.
Section summary: MO1489432 is real, narrow and nearly fixed. Microsoft's latest completion target is November 24, not November 20.
The backdrop: the November 12 Exchange Online outage
Friday's jitters make more sense given what happened the week before. IBTimes reports that the November 12 outage lasted about 24 hours and hit organizations in more than 70 countries. Users couldn't connect to Exchange Online mailboxes, and mail delivery stayed delayed even after service started coming back. Microsoft apologized and said it was not a cyberattack.
BleepingComputer, reporting on Microsoft's preliminary post-incident report in the Microsoft 365 admin center, filled in the technical detail:
- Timing: The incident ran from 11:20 AM ET on November 12 until 11:10 AM ET on November 13. The Penn mirror records the end time as 4:10 PM UTC on November 13.
- The bug: A software bug that shipped in July in an update for Microsoft 365 networking gateway servers. It ran without problems for more than three months.
- The trigger: Teams automatically failed over onto Exchange Online's networking infrastructure about 15 hours before the outage, adding traffic. About 14% of gateway capacity was already offline because of an unrelated issue.
- The cascade: Traffic shifted from failing servers to healthy ones and overloaded them too. At the worst point, more than 80% of the servers were unresponsive.
- Why Exchange took longest: Teams, OneDrive and SharePoint could switch to other infrastructure and recover sooner. Exchange Online couldn't make that switch.
Microsoft also said its load testing missed the bug because the labs used weaker hardware with fewer cores than production machines, and the contention problem gets worse on newer, higher-core servers. BleepingComputer reported that Microsoft has since added capacity, improved monitoring and put safeguards in place against traffic redirection causing the same kind of cascade.
Section summary: The November 12 cause is specific to that outage. It doesn't explain Friday's reports, the attachment incident or the contacts bug.
What to do if Outlook is misbehaving
Start by working out which problem you actually have:
- Contacts or Speed Dial blank or grey in Teams/Outlook? That matches MO1489432. In the meantime, a Chasms outage brief suggested reach the person by typing their name or email in the Teams or Outlook search bar for now. The same publication advised do not wipe and recreate contacts yet while Microsoft may still be restoring them. Microsoft is repairing affected contacts per user, so deleting them could make things worse.
- Can't open or upload attachments in new Outlook? That matches EX1561765. Trying Outlook on the web or the classic desktop client can tell you whether the problem is limited to new Outlook. Nothing in the available evidence says switching clients will get around a service-side fault.
- Something else entirely? Check the Microsoft 365 Status account on X. If you're on a work or school account, ask IT to look at Service health in the Microsoft 365 admin center, which shows incidents scoped to your tenant.
Admins: when users flood the help desk and quote Downdetector, the admin center is the place to check what's actually affecting your tenant.
Analysis: three separate problems on one Friday
Look at Friday as three unrelated problems that happened at the same time, not one big Outlook outage. One is a vague crowd-sourced signal. One is a narrow, confirmed attachment problem in new Outlook. One is a contacts bug that has taken two months to fix.
The contacts advisory is the more worrying one for IT. It started on September 25 and has needed at least three rounds of fixes, and Microsoft found a second code defect partway through recovery. Few users are affected now, but for those people it has gone on for weeks. Coming eight days after a global outage caused by a bug that sat undetected for three months, it also explains why users are quick to report trouble.
What should you do in practice? Match your symptom to a specific incident ID, leave affected contacts alone, and expect another update from Microsoft on November 24.
References
- Microsoft Outlook Down? Users Report Problems Friday as Microsoft Rolls Out Fix for Missing Contacts in Teams - International Business Times Australia International Business Times Australia · 2026-11-20T16:55:14+00:00
- Microsoft 365 MO1489432 Teams Outlook contacts still blank after recovery — Daily Outage Brief, 5 November 2026 morning - Chasms Blog chasms.com
- MO1489432: Users may be unable to view contacts… | M365 status flowbotics.ai