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)
We are using shared reports from a sharepoint having the convenience of accessing these reports via browser. But a few days ago, certain users are having problems with these reports, because when they access them, they see gibberish rather than normal text. This does not happen when its opened on the desktop app, only when its opened on the browser.
How can I fix this?
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
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.
Please contact your admin/IT department create a support ticket via Microsoft 365 Admin Center> Support> New service request.
None of these suggestions has helped.
Changing font, magnification level, double clicking on a single cell.
Our clients are experiencing the same issue with some users opening excel sharepoint files. What's the progress on a fix?
It seems service incident related. It will be resolved soon.
This is happening in my organization as well. The issue only occurs in OWA. In some instances, it will change to the appropriate text when the magnification level is changed, or some other property is changed. And I cannot replicate the issue in that moment, once it changes back to normal.
My entire organization uses OWA and very commonly previews files in-browser. This will be very confusing for them. We did not change any settings in our admin/org portal. Is it possible that something in this month's Microsoft Patch Tuesday has resulted in this issue?