Microsoft's advice is to use another Outlook client for now. Classic Outlook and Outlook on the web are not affected.
What Microsoft has confirmed
The first acknowledgment came from the Microsoft 365 Status account on X. The post said Microsoft was "investigating reports of issues uploading attachments in New Outlook. Uploading attachments in Outlook on the web and Outlook classic are unaffected."
A later post narrowed it down. Microsoft said it had found "a potential issue affecting how attachments are processed in the new Outlook client", and added that it was further reviewing the impacting code path to determine next steps, and encourage users to leverage Outlook on the web or Outlook classic as a workaround in the interim.
Microsoft called it a "potential" issue. That is investigation language, not a confirmed diagnosis. Microsoft has not identified a bad build, a broken service component or the actual cause.
It affects opening attachments too, not just sending
The X posts and many headlines focus on uploads, because a message stuck at "Please wait to send" is hard to miss. The formal service health advisory covers more than that. It is titled "Some users may be unable to open or upload attachments in the Outlook new client", and it says some users attempting to open or upload attachments in email messages may be impacted.
So if a received PDF won't open in new Outlook, it may be the same incident, even if the send button works fine.
How the incident has developed so far
According to the service health timeline archived by the tracker serv365.ai:
| Time (UTC, Nov 20) | Status |
|---|---|
| 13:51 | Incident start time |
| 13:52 | First post: Microsoft received reports and began reviewing service monitoring telemetry |
| 15:40 | Microsoft still reviewing telemetry to isolate the root cause |
| 16:19 | Microsoft reproduced the issue internally and began analyzing diagnostic data |
A Microsoft Q&A community answer lists the advisory as Exchange Online, status "Service degradation," type Advisory Start time: Nov 20, 2026, 7:51 AM CST, which matches 13:51 UTC. Cybersecurity News reported that the available updates did not identify affected regions, say how many users were impacted, or provide a timeline for a fix.
Reproducing a bug in-house is a real step forward. Engineers no longer depend on telemetry from customer machines. It is still not a fix. The archived 16:19 update gave 17:00 UTC as the time of the next update, not a time for a resolution.
Summary: Only the new Outlook client is affected. Both opening and uploading attachments can fail. Microsoft has reproduced the bug but hasn't named a cause or an ETA.
Microsoft's workaround: use another client
Microsoft recommends switching to a different client until the fix arrives. Cybersecurity News put the steps simply: if a file will not upload in New Outlook, open the same mailbox in Outlook on the web or switch to classic Outlook if it is installed. Attach the file there and check that it appears in the message before sending.
- Outlook on the web. Sign in through your browser with the same account. Personal accounts use Outlook.com. Work and school accounts should use their organization's usual web sign-in, not a personal Outlook.com login.
- Classic Outlook. If the classic desktop app is still installed, open it, write or reply to the message and attach the file there.
- Check before you send. Make sure the attachment appears in full on the message. Don't assume the upload finished.
Drafts sync through Exchange Online, so you can usually start a message in one client and finish it in another. If a draft is stuck in new Outlook, though, recreating it in the working client is the safer choice.
The offline mode workaround (not from Microsoft)
Windows Report later updated its story with a second option. It said some users have also reported seeing an error saying attachments are still loading. One reported workaround involves disabling offline mode in the new Outlook settings, although Microsoft has not officially recommended this fix. Some sysadmins in community discussions have also said that turning off new Outlook's offline setting helped.
Some caveats:
- This advice comes from users, not Microsoft. Microsoft's advisory doesn't mention offline mode.
- It isn't guaranteed to work. A few people reporting success doesn't prove it fixes every case, and it may do nothing for the "can't open attachments" side of the bug.
- Turning off offline mode changes how new Outlook keeps mail locally, so you lose offline access. Try it as a temporary test, note what you changed and turn it back on after Microsoft fixes the bug.
If you just need one attachment sent before the end of the day, Microsoft's workaround of switching clients is the more dependable option.
What IT admins should do
The help desk calls have probably already started, so here's a short list:
- Check your own tenant. Cybersecurity News says IT teams can follow Microsoft's service health guide, then open Health → Service health in the admin center and look for EX1561765. Public trackers and the X account show Microsoft's general updates. Only your admin center shows whether your organization is listed as affected.
- Use the incident ID to sort tickets. In the same publication's words, help desks can use the incident ID to group matching reports while noting cases that also fail in the browser or classic Outlook. If a user can't upload in Outlook on the web either, the cause is probably something else, such as a file-size limit, a DLP policy or a network problem, and it needs separate troubleshooting.
- Record version details for unusual cases. A Microsoft Q&A community answer suggests going to Settings → General → About Outlook. Record the Outlook, client, and WebView2 versions. That information helps if you open a support case.
- Warn users about phishing. Outages attract fake "fix your mailbox" emails. Cybersecurity News advises that staff should verify any emailed recovery instructions with their help desk rather than follow sign-in links.
- Don't hold back the workaround. If your organization has pushed users to new Outlook but classic Outlook is still installed, tell people they can use it for the day.
Why this matters
The timing is unfortunate. About a week earlier, Microsoft had a much larger Exchange Online outage (EX1550543 and MO1550821). Cybersecurity News notes that the current issue is narrower than the November 12–13 Microsoft 365 outage, which blocked mailbox access across several Outlook clients, and that the company has not publicly linked the attachment issue to the earlier outage. Don't assume the two are related.
The more important point is about the new Outlook itself. Microsoft has spent a long time moving Windows users from classic Outlook to the new app. In this incident, the new client is broken while classic Outlook and Outlook on the web work normally. The new Outlook is largely built on web technology, so you might expect it to fail when Outlook on the web does. This time it failed on its own. Microsoft's wording also points to the new client's handling of attachments, not to Exchange Online as a whole.
That doesn't mean new Outlook is a lost cause. Every client has bugs, and a code-path problem found and reproduced within a few hours is fairly ordinary. It does show why admins who kept classic Outlook installed as a fallback were right to do so.
Bottom line: If new Outlook won't attach or open a file, use Outlook on the web or classic Outlook for now. Treat the offline-mode tweak as a user-reported trick that Microsoft hasn't endorsed. Admins should keep watching EX1561765 in Service health for the actual fix.
References
- EX1561765 · Some users may be unable to open or upload attachments in the Outlook new client · serv365.ai serv365.ai
- Microsoft 365 Status on X: "We're investigating reports of issues uploading attachments in New Outlook. Uploading attachments in Outlook on the web and Outlook classic are unaffected. For more information, see EX1561765 in the Microsoft 365 admin center." / X x.com
- Cannot open or save email attachments on new outlook - Microsoft Q&A learn.microsoft.com