UPDATE: The dates for disabling of TLS1.0 and TLS1.1 in Office 365 have been set. As things stand, the date for Office 365 WW and GCC customers is June 2020. More information can be found here. The d...
Updated Aug 06, 2019
Version 4.0
Blog Post
Tips for troubleshooting:
If you go to the report details (per their instructions or the help of others, the chart view doesn't help much on the troubleshooting side) you can see the users affected.
The most common sources would be printers, desktop CRMs sending customer communications, or scanners. Once you know the user(s) affected it may trigger the memory to which application uses it. If not, login to the account using the web portal and go to their sent items. The communications inside will point you directly to the culprit.
For scanners and printers you should be able to login to their associated web portal to change the TLS settings (very simple on Xerox). If a desktop app is causing your headache you will likely need to install an update on your application server, though I highly suggest contacting your application support before doing so. Your application may need code updates to support the TLS update. The more notice you can give your providers, the better. No one wants to miss customer communications and potential revenue.
Good Luck!