This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi all,
Have been trying to deal with this issue for the last day and cannot get in touch with microsoft support on call.
Specifically users across our tenant cannot view pdf attachments and images on the online version of outlook that are emailed to them.
The weird thing is that if the user logs out and logs back in they have no issue for approx 20 min but after that it completely blanks and the issue persists.
We had recently implemented MFA over the weekend and initially looked and adjusted the policies to roll it back but there was no change to the issue.
I have gone through and checked the OWA policies and they allow for direct file access.
I have done the standard clear cache, use multiple browsers, incognito and the issue persists.
I inspected the issue via console and am getting a cascade of errors trying to connect to attachments.outlook.com see below:
owa.705956.m.4c01543c.js:1 GET https://attachments.office.net/owa/******@domain.site/service.svc/s/…er=20240322005.09&clientId=E2F529BB6BD8425CB651300572D2929A&animation=true net::ERR_CONNECTION_RESET owa.705956.m.4c01543c.js:1 GET https://attachments.office.net/owa/******@domain.site/service.svc/s/…er=20240322005.09&clientId=E2F529BB6BD8425CB651300572D2929A&animation=true net::ERR_CONNECTION_RESETowa.mailindex.27ae40ae.js:1 POST https://outlook.office.com/api/v2.0/me/signals?n=218&cv=xDmwfzfCa03hhsu0LSoIa2.239 400 (Bad Request)owa.327465.m.44692cb8.js:1 POST https://outlook.office.com/search/api/v1/recommendations 404 (Not Found)owa.mailindex.27ae40ae.js:1 GET https://outlook.office.com/imageB2/v1.0/users/******@domain.site/image/resize(width=120,height=120,allowResizeUp=true) 404 (Not Found)owa.327465.m.44692cb8.js:1 POST https://outlook.office.com/search/api/v1/recommendations 404 (Not Found)owa.mailindex.27ae40ae.js:1 POST https://outlook.office.com/api/v2.0/me/signals?n=221&cv=xDmwfzfCa03hhsu0LSoIa2.243 400 (Bad Request)owa.mailindex.27ae40ae.js:1 POST https://outlook.office.com/api/v2.0/me/signals?n=230&cv=xDmwfzfCa03hhsu0LSoIa2.252 400 (Bad Request)owa.mailindex.27ae40ae.js:1 POST https://outlook.office.com/api/v2.0/me/signals?n=232&cv=xDmwfzfCa03hhsu0LSoIa2.254 400 (Bad Request) Additionally the most telling issue i see is the get filerequest which seems to be appending a continuous series of xcf to the end of the file request Request URI and returning a URI to long error. https://attachments.office.net/owa/******@domain.site/service.svc/s/GetFileAttachment?id=AAMkAGYyNTQ3NzJhLTUzMTktNDU1Ni1hN2U0LTc5YzVmMzQ4YjNiNQBGAAAAAAAighs5TJb%2FSbFQisrJyOrGBwC1DoqZ%2FvWnRqTfkMXDodRvAAAAAAEMAAC1DoqZ%2FvWnRqTfkMXDodRvAACmtXuGAAABEgAQAF4YChW%2F6QhHtzucBvSHpTE%3D&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkU1RDJGMEY4REE5M0I2NzA5QzQzQTlFOEE2MTQzQzAzRDYyRjlBODAiLCJ0eXAiOiJKV1QiLCJ4NXQiOiI1ZEx3LU5xVHRuQ2NRNm5vcGhROEE5WXZtb0EifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiMTRlNDJiOGUzMDFiNDIwNWI5Zjk5NWJmNjhiZjAwZmYiLCJzaWduaW5fc3RhdGUiOiJbXCJbXFxcIltcXFxcXFxcIltcXFxcXFxcXFxcXFxcXFwiW1xcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFwiW1xcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXCJbXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFxcXFx***...(cXFx)\*1000...***cXFwiXVxcXFxcXFxcXFxcXFxcXCJdXFxcXFxcXCJdXFxcIl1cIl0iLCJ2ZXIiOiJFeGNoYW5nZS5DYWxsYmFjay5WMSIsImFwcGN0eHNlbmRlciI6Ik93YURvd25sb2FkQGQyNzcyMDE0LTUwYmUtNGI5OS05Y2U4LTVhY2E0N2ZhZTUzZSIsImlzc3JpbmciOiJXVyIsImFwcGN0eCI6IntcIm1zZXhjaHByb3RcIjpcIm93YVwiLFwicHVpZFwiOlwiMTE1MzgwMTEyNTg4ODEwMzQxOFwiLFwic2NvcGVcIjpcIk93YURvd25sb2FkXCIsXCJvaWRcIjpcImYzODk0Njk2LTBkMjEtNDYzYy1hMWQyLTgyNWE4NWI4MGM1Y1wiLFwicHJpbWFyeXNpZFwiOlwiUy0xLTUtMjEtMzE5MTE0ODc0NC0zNDk3Nzg3NjUwLTM1NTU4ODcwOS0xOTA0MDgzNFwifSIsIm5iZiI6MTcxMjA0MDQ4MywiZXhwIjoxNzEyMDQwNzgzLCJpc3MiOiIwMDAwMDAwMi0wMDAwLTBmZjEtY2UwMC0wMDAwMDAwMDAwMDBAZDI3NzIwMTQtNTBiZS00Yjk5LTljZTgtNWFjYTQ3ZmFlNTNlIiwiYXVkIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwL2F0dGFjaG1lbnRzLm9mZmljZS5uZXRAZDI3NzIwMTQtNTBiZS00Yjk5LTljZTgtNWFjYTQ3ZmFlNTNlIiwiaGFwcCI6Im93YSJ9.J80acmasuhESrbNqg-64ZkKXIGc4HeJRB5R\_ifeHwKHi76vNlk5iskv9pCJNe2ZLwgMn-sjLQbpuAaYfgG7iJ4WiGzbgyWlPPBDuLqdivxKaCt27OvbUApWlRcOUCYF6-j4PAEYRnAjYghUtU6zocevn9ZrF-wGBibwktQLk\_sL6qjaOpsHlzivs7dGPTKJIkGGIJijR0VzaGD0DBppRxhYpR3rYwp3b0q-u7FNJqN3F71-a9UnRtocwxsil7nWyp3ikYa4wnH03waZG6W9FcqPHeAlp5D2aTwGrzptKr6cD5UjJo\_OKV\_VP8P6Szf\_8EmiXtjbrAnojwhvdNcXGBQ&X-OWA-CANARY=bdvoVygDEHQAAAAAAAAAAGA4\_lbhUtwYol0MED9ByCstgxu48ai1iptZFH4RCa7CHE14\_AWgkNY.&owa=outlook.office.com&scriptVer=20240322005.09&clientId=E2F529BB6BD8425CB651300572D2929A&isDownload=true&animation=true&isDocumentPreview=True
Referrer Policy:no-referrer
One work around is that it is possible to save the file to one drive and then view it there but it is not a long term fix.
The final aspect I noticed is when I go to outlook.cloud.microsoft for the new domain, the ability to download files directly is availabel but the preview function still does not work.
Would really appreciate any help resolving this!
Thank you
Nafaa
Sending, receiving, and organizing email in Outlook on the web for business
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I am also having this same issue. This should be a priority as these temporary fixes do not last very long and having to log on and off.
At least put it back to the old version until you all can figure it out. This is crippling businesses who rely on outlook.
There has been an update from Microsoft.
We've completed the development of the fix and have begun our internal validation process. We expect this will complete by our next scheduled update on Monday, April 8, 2024 at 5:00 PM EDT . At this time we'll begin deploying the fix to the affected environment to remediate impact. Next update by:Monday, April 8, 2024 at 5:00 PM EDT Hope it fixes the issues we've all been experiencing since April Fools Day.
As a temp fix (since logging out and in did not work) If I remove all site data from Edge chrome the issue reoccurs eventually but staff can get some work done.
This is also affecting the images within an email as well (they can't be viewed, just an empty box is visible)
Removing all site data from settings on Edge chrome works (for a little bit of time).
This issue only occurs for us in a regular edge window. If using an InPrivate window the issue doesn't occur. Also using another browser (Google chrome) the issue doesn't occur either.
I am having the same issue!! It has completely stalled my work. I cannot view or download PDF, jpeg - really anything!!
Had a couple of work arounds for the time being. But this is painful snd theres compounding issues with users not be recognized: they try to sign in and they are being shown an error that the account does not exist when in fact it does as well as super slow loading if it is accessed.
For work arounds:
Issue does not affect the old desktop client.
The new desktop client however is experiencing super slow loading and usability.
If the users dont have office downloaded locally, have them access portal.office.com and install office from there.
If you dont have the request # of licenses for staff you can get away with starting a 1 month trail for m365 standard and or office 365 business apps. Can get 25 trial licenses each and allows for the downloading of the desktop apps.
If that doesnt work for you, users can select save to drive. Once it’s in one drive users can download and view normally.
Finally, haven’t fleshed it out completely but accessing outlook via outlook.cloud.microsoft allows for downloading but the preview part of the issue still persists.
End of the day still have to rely on Microsoft to fix this issue but hopefully this may help.