A new problem with New Outlook
retained text
This has got to be the worst one so far, as it is costing them actual customers and missing vendor deadlines. Somehow a user snuck past us and is using New Outlook. A report came in that the first time he emails someone new, it fails. The 2nd time or any reply, it works. Turns out yep, that's a thing. And it "silently" fails so no outbox entry, sent item, or message trace. I think they show up in all 3 places as successes, but it never actually sends. Or it shows local but not in Trace. I don't remember. Here's AI's version of what happens because I'm too busy to write up my own summary today. * **Auto-Complete Entry Generation:** When a user types a brand-new address into the `To:` field, standard email clients create a temporary "Suggested Contact" or cache entry. In New Outlook, if a recipient isn't in Exchange/Outlook Contacts or the Auto-Complete cache, the initial submission occasionally drops off the queue during the background synchronization token handoff between the client and Exchange Online. * **"Silent Failure":** Because New Outlook operates as a web app wrapper (OWA interface), it doesn't utilize a traditional offline Outbox like Classic Outlook (`.pst`/`.ost` based). Emails render instantly as sent in the UI, but if the back-end handoff fails validation on an unverified/uncached address, Exchange drops the message without generating a Non-Delivery Report (NDR) back to the client. * **Why the 2nd email works:** The moment the first email is initiated, Microsoft 365 automatically writes that recipient's email address to the user's **Suggested Contacts / Auto-Complete cache**. By the time the user sends the 2nd email or a reply, the system recognizes the address as an existing object in their profile, allowing normal transit. There is no fix btw except "reinstall Outlook, clear app data cache, cross your fingers, etc." My fix: 1. uninstall it 2. set up Outlook Classic 3. complain about it on Reddit.
document fetched 2026-10-08 00:38 · canonical https://reddit.com/r/sysadmin/comments/1x02l0i/a_new_problem_with_new_outlook