O365 - Email/Outlook
2025-08-14 | Status | Description |
---|---|---|
03:35 PM |
![]() |
EXCHANGE NOTICE Users may be unable to open or preview PDF attachments in the new Outlook desktop experience and Outlook on the web Service Restored More info: Impact manifested when previewing and downloading the PDF file. Some users may have seen an error message in Outlook that stated, "Something went wrong while the document preview was being created. Please try again later," or an error message when the attachment was attempting to open through Edge that stated, "We couldn't open this file. Something went wrong." Users could avoid this issue by accessing the PDF files through the classic Outlook desktop experience. Final status: The service provider's deployment of the fix to bypass the offline caching of attachments is complete, and they've monitored their service health telemetry to confirm that the impact is remediated. Start time: Sunday, July 20, 2025, at 9:00 PM AST End time: Tuesday, August 12, 2025, at 2:30 PM AST |
2025-08-08 | Status | Description |
---|---|---|
03:30 PM |
![]() |
EXCHANGE NOTICE Users may be unable to open or preview PDF attachments in the new Outlook desktop experience Service Degradation More info: Impact can manifest when previewing and downloading the PDF file. Some users may see a "Something went wrong while the document preview was being created. Please try again later." error message in Outlook, or a "We can't open this file. Something went wrong." error message when the attachment is attempting to open through Edge. Users can avoid this issue by accessing the PDF files through the classic Outlook desktop experience. Current status: The service provider received reports of an issue where users on the New Outlook desktop experience may be unable to open PDF attachments. They confirmed that some portions of a recent service update, intended to implement a new PDF viewer, aren't compatible with the offline caching of attachments. They've developed a fix to bypass this caching and initiated the deployment to resolve this issue. |