TLS- Deprecation-ReportReport results appear to be incorrect

%3CLINGO-SUB%20id%3D%22lingo-sub-826489%22%20slang%3D%22en-US%22%3ETLS-%20Deprecation-ReportReport%20results%20appear%20to%20be%20incorrect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826489%22%20slang%3D%22en-US%22%3E%3CP%3EBased%20on%20the%20announcement%20of%20MC186218%2C%20%3CBR%20%2F%3Ewe%20are%20considering%20checking%20the%20TLS%20version%20in%20use%20with%20securescore%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EDespite%20accessing%20OotW%20and%20ODfB%20and%20SPO%20with%20a%20browser%20using%20TLS%201.1%20for%20several%20days%20ago%2C%3CBR%20%2F%3E%22Remove%20TLS%201.0%20%2F%201.1%20and%203DES%20dependencies%E2%80%9D%20is%20complete%20(score%205%2F5)%2C%20and%20%3CBR%20%2F%3E%22TLS-%20Deprecation-Report%20.csv%22%20was%20also%20empty.%20%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20this%20function%20not%20working%20properly%3F%20%3CBR%20%2F%3EIsn't%20there%20any%20way%20for%20end%20users%20to%20verify%20that%20old%20TLS%20like%20TLS%201.0%20%2F%201.1%20is%20not%20used%20for%20browser%20access%3F%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3ESecureScore%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsecurescore.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsecurescore.microsoft.com%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3ETLS-%20Deprecation-Report%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fservicetrust.microsoft.com%2FAdminPage%2FTlsDeprecationReport%2FDownload%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fservicetrust.microsoft.com%2FAdminPage%2FTlsDeprecationReport%2FDownload%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%E2%80%BBI%20know%20that%20the%20TLS%20version%20used%20in%20SMTP%20can%20be%20confirmed%20by%20the%20following%20link%20method.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EInvestigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FInvestigating-TLS-usage-for-SMTP-in-Exchange-Online%2Fba-p%2F609278%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FExchange-Team-Blog%2FInvestigating-TLS-usage-for-SMTP-in-Exchange-Online%2Fba-p%2F609278%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-912540%22%20slang%3D%22en-US%22%3ERe%3A%20TLS-%20Deprecation-ReportReport%20results%20appear%20to%20be%20incorrect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-912540%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20anyone%20have%20information%20about%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Based on the announcement of MC186218,
we are considering checking the TLS version in use with securescore


Despite accessing OotW and ODfB and SPO with a browser using TLS 1.1 for several days ago,
"Remove TLS 1.0 / 1.1 and 3DES dependencies” is complete (score 5/5), and
"TLS- Deprecation-Report .csv" was also empty.

Is this function not working properly?
Isn't there any way for end users to verify that old TLS like TLS 1.0 / 1.1 is not used for browser access?


SecureScore
https://securescore.microsoft.com/


TLS- Deprecation-Report
https://servicetrust.microsoft.com/AdminPage/TlsDeprecationReport/Download


※I know that the TLS version used in SMTP can be confirmed by the following link method.

Investigating TLS usage for SMTP in Exchange Online
https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Investigating-TLS-usage-for-SMTP-in-Exchan...

1 Reply

Does anyone have information about this?