SharePoint Online, Chrome, and "Insecure" sites

%3CLINGO-SUB%20id%3D%22lingo-sub-39624%22%20slang%3D%22en-US%22%3ESharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39624%22%20slang%3D%22en-US%22%3E%3CP%3EAn%20update%20to%20SharePoint%20Online%20for%20some%20Office%20365%20tenants%20clashed%20with%20Google%E2%80%99s%20determination%20to%20move%20from%20SHA-1%20to%20SHA-2%20as%20the%20basis%20for%20securing%20web%20sites.%20The%20symptom%20is%20that%20Chrome%20flags%20SharePoint%20sites%20as%20%E2%80%9CNot%20Secure%E2%80%9D%2C%20which%20is%20a%20pretty%20worrying%20thing%20for%20an%20Office%20365%20administrator%20to%20see.%20Fortunately%2C%20Microsoft%20is%20reversing%20the%20update%20out%20to%20fix%20the%20problem.%20%3CA%20href%3D%22https%3A%2F%2Fwww.petri.com%2Fchrome-makes-sharepoint-look-insecure%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.petri.com%2Fchrome-makes-sharepoint-look-insecure%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-39624%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177502%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177502%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3BLooks%20like%20this%20is%20happening%20again.%20Any%20update%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177507%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177507%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F332069%22%20target%3D%22_blank%22%3E%40Maridee26%3C%2FA%3E%26nbsp%3BPossibly%20due%20to%20the%20recent%20Chrome%2080%20release.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2020%2F01%2F27%2Foffice-365-ok-chrome-80-samesite-update%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2020%2F01%2F27%2Foffice-365-ok-chrome-80-samesite-update%2F%3C%2FA%3E%26nbsp%3B%20I%20haven't%20seen%20any%20problems.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177527%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177527%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3BMy%20site%20is%20marked%20%22Not%20secure%22.%20Is%20there%20anything%20I%20can%20do%20about%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221.png%22%20style%3D%22width%3A%20542px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F171484i2C73493FFB0F1826%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%221.png%22%20alt%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177534%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177534%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F332069%22%20target%3D%22_blank%22%3E%40Maridee26%3C%2FA%3E%26nbsp%3B%20Sure.%20File%20a%20support%20ticket%20with%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177537%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177537%22%20slang%3D%22en-US%22%3EDarn%20I%20was%20trying%20to%20avoid%20that%20%3A(%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177608%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177608%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3BAfter%20talking%20to%20support%20(who%20was%20of%20no%20help)%2C%20I%20realized%20that%20the%20issue%20is%20due%20to%20having%20installed%20Chrome%20Beta%20according%20to%20Microsoft%20instructions%20when%20I%20tested%20for%20the%20new%20Chrome%20release%20earlier%20this%20month.%20If%20anyone%20else%20is%20having%20this%20issue%2C%20this%20may%20be%20why.%20Resolution%20is%20to%20uninstall%20Chrome%20Beta%20and%20reinstall%20Chrome.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F171487iAEC18FFFF996EC4D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%221.png%22%20alt%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1177610%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%2C%20Chrome%2C%20and%20%22Insecure%22%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177610%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F332069%22%20target%3D%22_blank%22%3E%40Maridee26%3C%2FA%3E%26nbsp%3BThat's%20reasonable.%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

An update to SharePoint Online for some Office 365 tenants clashed with Google’s determination to move from SHA-1 to SHA-2 as the basis for securing web sites. The symptom is that Chrome flags SharePoint sites as “Not Secure”, which is a pretty worrying thing for an Office 365 administrator to see. Fortunately, Microsoft is reversing the update out to fix the problem. https://www.petri.com/chrome-makes-sharepoint-look-insecure

7 Replies

 @Tony Redmond Looks like this is happening again. Any update?

@Maridee26 Possibly due to the recent Chrome 80 release. https://office365itpros.com/2020/01/27/office-365-ok-chrome-80-samesite-update/  I haven't seen any problems.

@Tony Redmond My site is marked "Not secure". Is there anything I can do about it?

 

1.png

@Maridee26  Sure. File a support ticket with Microsoft.

Darn I was trying to avoid that :(

@Tony Redmond After talking to support (who was of no help), I realized that the issue is due to having installed Chrome Beta according to Microsoft instructions when I tested for the new Chrome release earlier this month. If anyone else is having this issue, this may be why. Resolution is to uninstall Chrome Beta and reinstall Chrome.

1.png

@Maridee26 That's reasonable.