Forum Discussion
SharePoint/Excel - This content presents a potential security issue. Do you trust this content?
Since this morning several client versions of excel that have a pointing to sharepoint (our tenant) give the following message; does this happen to anyone else?
I don't understand why so many are unwilling to make the change to Trusted Sites either via Group Policy, Intune, or other management software. Adding sites to Trusted sites (both in Office Trust Center and Internet Options) should be considered best practice for managing security. Sure, it's something like four different URLs you need to add, but it isn't hard and is well documented on how to control this.
And no, I won't respond to the people who think they shouldn't have to manage their security.
And no, I won't respond to the people who think they shouldn't have to manage their security.
Good day CKennedy. People have their reasons. Of course it is easy to setup a trusted site, but the wrongful security message was never an issue for anyone until Microsoft seemingly made it an issue around the end of July (or when this thread was opened). That is why I wasn't too concerned and preferred Microsoft to resolve their issue without having to make a "permanent" implementation for a "temporary" issue. We knew these files were not a security risk since they were from our own SharePoint site(s) using files we created.
Waiting was beneficial for my situation because Microsoft was able to resolve the issue with an update to O365 (at least it seems that way). Any of my users who still experienced the issue after the update (only 1), I simply used GPO to add the trusted site. It really isn't a big deal like you're making it out sound. I do agree that it is good practice for managing security with Trusted Sites, but it isn't the only way to implement good security practices.
I do find it interesting that it only affected a small subset of my users. Almost everyone uses a SharePoint site within their own team, but not everyone had this issue. Very weird nonetheless!
Waiting was beneficial for my situation because Microsoft was able to resolve the issue with an update to O365 (at least it seems that way). Any of my users who still experienced the issue after the update (only 1), I simply used GPO to add the trusted site. It really isn't a big deal like you're making it out sound. I do agree that it is good practice for managing security with Trusted Sites, but it isn't the only way to implement good security practices.
I do find it interesting that it only affected a small subset of my users. Almost everyone uses a SharePoint site within their own team, but not everyone had this issue. Very weird nonetheless!