As Microsoft has announced it was moving to TLS 1.2, the 3DES cipher support is going to be removed by February 28, 2019.
If you are not sure if this cipher is still being used by your organization to connect and access Office 365 services you can go to the Secure Score website (http://securescore.microsoft.com) and use the “Remove TLS 1.0/1.1 and 3DES Dependencies” option
By clicking the Learn More button you will then be able to access the Services and Trust site to download the TLS report to identify who is still connecting to your Office 365 tenant using 3DES (and TLS 1.0/1.1) (or you can use the direct URL to this report https://servicetrust.microsoft.com/AdminPage/TlsDeprecationReport/Download)
The report contains the username, agent (aka the client connecting) and the number of time it has connected
2 thoughts on “Office 365 – 3DES cipher support is being retired by Feb 28, 2019”
How can you identity which client side software is being used to connect? I have a few users that on listed int he remote, however, they are all running Office 365 desktop apps and are updated automatically with the most recent version of office.
I’m sorry but I don’t get your question
In the report you have the user agent of the application which is using this protocol, with this information you then should be able to identify the application using it