Forum Discussion
SharePoint/Excel - This content presents a potential security issue. Do you trust this content?
Hi All
The service health dashboard showed the error as closed this morning. I was still experiencing issues so was about to reopen a support call and noticed that MS have indeed reopened a new incident advisory. See text below. So yes they know it is still not resolved.
Some users may incorrectly receive a security warning prompt when opening some Office files in OneDrive for Business
Issue ID: OD861567
Affected services: OneDrive for Business
Status: Service degradation
Issue type: Advisory
Start time: 31 Jul 2024, 05:30 BST
User impact
Users may incorrectly receive a security warning prompt when opening some Office files in OneDrive for Business.
More info
More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
Scope of impact
Impact is specific to some users who are served through the affected infrastructure, attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Current status
14 Aug 2024, 10:11 BST
We've received reports that impact associated with OD843843 persists. We've resumed our investigation of the issue and are currently reviewing service telemetry to isolate the root cause and determine our next troubleshooting steps.
Next update by:
Wednesday, 14 August 2024 at 19:00 BST
Where did you took this? "Current status 14 Aug 2024, 10:11 BST"
On my side the portal indicate Service Restored and yesterday update is the final update for the event.(Issue still running here too)
- in 365 admin portal, service health
- The case number changed...
Here is the new link for all:
https://admin.microsoft.com/#/servicehealth/:/alerts/OD861567
- Thanks for the update. Yes, this issue is still ongoing. Like many have said in this thread, adding a Trusted Site does seem to resolve the issue. Personally, since Microsoft introduced the issues, I would prefer to wait for them to push a solution to the issue rather than going in and changing configurations on my end. Sure, it is not much work to implement the Trusted Site via Group Policy, but again, Microsoft should be resolving the issue since they introduced it. This was never a problem until the end of July 2024, same time this thread was created and when my users began reporting the issue.
