Hello,
Perhaps this might assist:
Microsoft's Engineering Improvements to eliminate TLS 1.0 dependencies
- IIS custom logging to correlate client IP/user agent string, service URI, TLS protocol version and cipher suite.
- With this logging, admins can finally quantify their customers' exposure to weak TLS.
- SecureScore - To help Office 365 tenant admins identify their own weak TLS usage, the SecureScore portal has been built to share this information as TLS 1.0 exited support in Office 365 in October 2018.
- This portal provides Office 365 tenant admins with the valuable information they need to reach out to their own customers who may be unaware of their own TLS 1.0 dependencies.
- Please visit https://securescore.microsoft.com/ for more information.
- This portal provides Office 365 tenant admins with the valuable information they need to reach out to their own customers who may be unaware of their own TLS 1.0 dependencies.
Finding and fixing TLS 1.0 dependencies in code
If this is helpful please accept answer.