Home
%3CLINGO-SUB%20id%3D%22lingo-sub-758420%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758420%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Fmailflow%2Fdashboard%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fprotection.office.com%2Fmailflow%2Fdashboard%3C%2FA%3E%26nbsp%3B--%26gt%3B%26nbsp%3BOutbound%20and%20Inbound%20mail%20flow%20--%26gt%3B%20View%20Details%20--%26gt%3B%20Connector%20Report.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758770%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758770%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20update%2C%20however%20I%20do%20not%20see%20the%20link%20for%20the%20connector%20report%20here.%20I%20believe%20it%20was%20orignaly%20a%20link%20in%20this%20block%20of%20text%2C%20as%20seen%20in%20this%20link%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fmfi-outbound-and-inbound-mail-flow%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fmfi-outbound-and-inbound-mail-flow%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20the%20image%20below%20is%20what%20I%20see%20now%2C%20I'd%20be%20intrested%20to%20know%20if%20this%20is%20isolated%20to%20us%2C%20or%20if%20other%20people%20are%20having%20similar%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20does%20anyone%20know%20if%20anything%20needs%20to%20be%20configured%20before%20this%20link%20becomes%20avalable%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758993%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758993%22%20slang%3D%22en-US%22%3E%3CP%3Ewe%20have%20download%20the%20secure%20trust%20portal%20and%20even%20it%20shows%20Tls1.2%20machine%20in%20the%20report.%20we%20have%20opened%20many%20tickets%20with%20your%20support%20team%20and%20it%20is%20not%20worth....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Erelated%20to%20smtp%20client%20auth%20report.%20can%20you%20please%20tell%20us%20whether%20they%20access%20the%20smtp%20connections%20through%20application%20or%20mobile%20device.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759057%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759057%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353684%22%20target%3D%22_blank%22%3E%40hobbssj%3C%2FA%3EI%20am%20having%20the%20same%20issue.%20The%20connector%20report%20link%20is%20missing%20for%20us%20as%20well.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759066%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759066%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20information%20on%20how%20to%20go%20about%20resolving%20these%20issues%20would%20be%20great.%20Even%20if%20its%20just%20a%20few%20links%20to%20get%20us%20started.%20Also%2C%20could%20you%20not%20also%20capture%20the%20IP%20address%20%2F%20hostname%20of%20the%20device(s)%20to%20show%20in%20that%20report.%20Some%20of%20our%20users%20have%20quite%20a%20few%20devices%20and%20its%20not%20always%20clear%20which%20one%20is%20the%20culprit%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759448%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759448%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20opened%20a%20Support%20ticket%20for%20what%20its%20worth%2C%20I%20post%20the%20results%20afterword's.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-762732%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-762732%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353684%22%20target%3D%22_blank%22%3E%40hobbssj%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F377693%22%20target%3D%22_blank%22%3E%40mikeh1974%3C%2FA%3E%26nbsp%3Bgo%20to%20reports%20and%20select%20the%20connector%20report%20from%20there%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-762747%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-762747%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20that%20seem%20to%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-762873%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-762873%22%20slang%3D%22en-US%22%3EThank%20you%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763085%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763085%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159325%22%20target%3D%22_blank%22%3E%40Eric%20Bostrom%3C%2FA%3Eyou%20can%20see%20more%20details%20when%20you%20request%20the%20report.%20The%20report%20you%20receive%20in%20your%20email%20will%20have%20that%20information.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763087%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763087%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20figured%20that%20out%20after%20posting%20but%20can't%20delete%20comment%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763074%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763074%22%20slang%3D%22en-US%22%3E%3CP%3E%22%3CSPAN%3EYou%20can%20use%20these%20reports%20to%20help%20determine%3CSTRONG%3Ewhich%20clients%20and%20servers%3C%2FSTRONG%3Eare%20still%20using%20TLS1.0%20and%20TLS1.1%20to%20connect%20to%20the%20various%20email%20protocol%20endpoints%20in%20Exchange%20Online.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit1%3A%20Click%20'Request%20Report'%20to%20get%20the%20level%20of%20detail%20you%20need%20to%20identify%20hosts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit2%3A%20%3CA%20href%3D%22https%3A%2F%2Fdba.stackexchange.com%2Fquestions%2F213608%2Fenable-tls-1-2-for-sql-server-2016-database-mail%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EThis%20worked%20great%3C%2FA%3Eto%20get%20tls1.2%20working%20on%20server16%2Fsql16sp2.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763624%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763624%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20link%20provided%20here%20working%20for%20any%20one%20else%3F%3C%2FP%3E%3CP%3E%22This%20will%20take%20you%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fservicetrust.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESecure%20Trust%20Portal%3C%2FA%3Ewhere%20you%20can%20download%20your%20TLS%201.0%2F1.1%20and%203DES%20reports.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20just%20shows%20up%20with%20the%20my%20Office%26nbsp%3B%20365%20banner%20across%20the%20top%20but%20no%20content.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763759%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763759%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20can't%20get%20to%20the%26nbsp%3BSmtp%20Client%20Submission%20Report%20ussing%20the%20dashboard%2C%20try%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Freportv2%3Fid%3DSmtpClientSubmissionReport%26amp%3Bpivot%3DSenderDomain%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fprotection.office.com%2Freportv2%3Fid%3DSmtpClientSubmissionReport%26amp%3Bpivot%3DSenderDomain%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763929%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763929%22%20slang%3D%22en-US%22%3E%3CP%3EBeing%20a%20complete%20IT%20luddite%2C%20I'd%20like%20to%20know%20exactly%20how%20to%20do%20the%20update%20-%20we%20have%20just%20lost%20our%20IT%20support%20which%20has%20now%20left%20us%20with%20a%20bit%20of%20a%20problem%20as%20half%20the%20team%20(in%20a%20remote%20location)%20are%20on%20TLS1%20(from%20the%20report%20I%20just%20obtained)%20and%20bearing%20in%20mind%20the%20update%20from%20Office%20Centre%20re%20moving%20to%20TLS1.2%20asap%2C%20I'd%20like%20to%20know%20how%20I%20achieve%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-764558%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-764558%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20as%20clear%20as%20mud.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPrey%20tell%2C%20Microsoft%2C%20just%20what%20exactly%20do%20I%20need%20to%20do%20to%20ensure%20the%20mail%20continues%20to%20flow%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-764622%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-764622%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F378965%22%20target%3D%22_blank%22%3E%40JohnnyReaction%3C%2FA%3E%26nbsp%3BAgreed.%20I%20have%20an%20MFP%20that%20sends%20scans%20to%20users%20that%20I'm%20confident%20isn't%20going%20to%20be%20compromised%2C%20and%20the%20other%20account%20is%20for%20sending%20password%20reminders%20to%20users%20who%20don't%20have%20domain%20joined%20computers%20that%20get%20a%20change%20password%20pop-up.%20Again%2C%20I'm%20confident%20that%20account%20won't%20be%20compromised.%20It's%20all%20well%20and%20good%20for%20MS%20to%20tell%20us%20what%20accounts%20are%20using%20the%20older%20TLS%20module.%20But%20they%20don't%20provide%20any%20fix%20or%20solution%20to%20allow%20it%20to%20continue%20for%20those%20handful%20of%20accounts%20that%20we%20want%20to%20continue%20using%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-764760%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-764760%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20a%20way%20to%20view%20the%20connector%20report.%26nbsp%3B%20MS%20likes%20to%20hide%20things%20and%20not%20update%20documentation%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20324px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F123846i750BDC43F96A2A40%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-07-19%2008_56_30-Dashboard%20-%20Security%20%26amp%3B%20Compliance.png%22%20title%3D%222019-07-19%2008_56_30-Dashboard%20-%20Security%20%26amp%3B%20Compliance.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F123847iC8A7830755A0477C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-07-19%2008_58_03-Report%20Viewer%20-%20Security%20%26amp%3B%20Compliance.png%22%20title%3D%222019-07-19%2008_58_03-Report%20Viewer%20-%20Security%20%26amp%3B%20Compliance.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-764789%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-764789%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228742%22%20target%3D%22_blank%22%3E%40Shawn%20Housler%3C%2FA%3E%26nbsp%3BDon't%20worry%20that%20will%20change%20in%20the%20re-design%20that%20will%20be%20introduced%20next%20week%20with%20a%20re-design%20again%20two%20weeks%20after%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-765446%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-765446%22%20slang%3D%22en-US%22%3E%3CP%3ETips%20for%20troubleshooting%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20go%20to%20the%20report%20details%20(per%20their%20instructions%20or%20the%20help%20of%20others%2C%20the%20chart%20view%20doesn't%20help%20much%20on%20the%20troubleshooting%20side)%20you%20can%20see%20the%20users%20affected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20most%20common%20sources%20would%20be%20printers%2C%20desktop%20CRMs%20sending%20customer%20communications%2C%20or%20scanners.%26nbsp%3B%20Once%20you%20know%20the%20user(s)%20affected%20it%20may%20trigger%20the%20memory%20to%20which%20application%20uses%20it.%26nbsp%3B%20If%20not%2C%20login%20to%20the%20account%20using%20the%20web%20portal%20and%20go%20to%20their%20sent%20items.%26nbsp%3B%20The%20communications%20inside%20will%20point%20you%20directly%20to%20the%20culprit.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20scanners%20and%20printers%20you%20should%20be%20able%20to%20login%20to%20their%20associated%20web%20portal%20to%20change%20the%20TLS%20settings%20(very%20simple%20on%20Xerox).%26nbsp%3B%20If%20a%20desktop%20app%20is%20causing%20your%20headache%20you%20will%20likely%20need%20to%20install%20an%20update%20on%20your%20application%20server%2C%20though%20I%20highly%20suggest%20contacting%20your%20application%20support%20before%20doing%20so.%26nbsp%3B%20Your%20application%20may%20need%20code%20updates%20to%20support%20the%20TLS%20update.%26nbsp%3B%20The%20more%20notice%20you%20can%20give%20your%20providers%2C%20the%20better.%26nbsp%3B%20No%20one%20wants%20to%20miss%20customer%20communications%20and%20potential%20revenue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20Luck!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772426%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772426%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20any%20one%20found%20a%20way%20to%20trace%20a%20smtp%20message%20when%20it%20shows%20a%20smtp%20message%20was%20sent%20on%20a%20certain%20date%20with%20TLS1.0%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20we%20go%20about%20getting%20reports%20for%20older%20dates%2C%20I%20was%20trying%20to%20request%20the%20SMTP%20Auth%20Clients%20Report%20but%20only%20allows%20me%20to%20go%20back%20to%20June%2029th.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20identified%20an%20smtp%20event%20on%20June%2028th%20using%20an%20older%20TLS%20but%20we%20are%20having%20trouble%20tracking%20down%20that%20actual%20message%2C%20when%20I%20pull%20detailed%20reports%20they%20all%20shows%20TLS%201.2.%26nbsp%3B%20What%20other%20reports%20are%20people%20using%20to%20help%20identify%20messages%20sent%20with%20older%20TLS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772520%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772520%22%20slang%3D%22en-US%22%3E%3CP%3EFrom%20what%20I%20can%20see%20from%20our%20environment%20there%20are%20emails%20being%20sent%20in%20two%20ways%3A%3C%2FP%3E%3COL%3E%3CLI%3E%26nbsp%3BSMTP%20Auth%20-%20Authenticated%26nbsp%3B%3C%2FLI%3E%3CLI%3EUnauthenticated%3C%2FLI%3E%3C%2FOL%3E%3CP%3EThese%20emails%20can%20either%20use%20No%20TLS%2C%20TLS%201.0%2C%20TLS%201.1%2C%20or%20TLS%201.2.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20think%20I%20got%20from%20the%20above%20is%20that%20any%20devices%20or%20applications%20that%20authenticate%20but%20don't%20use%20TLS%201.2%20will%20fail%20beginning%20June%201%2C%202020.%20It%20also%20looks%20like%20any%20devices%20that%20send%20mail%20using%20the%20Office%20365%20SMTP%20server%20that%20don't%20authenticate%20will%20continue%20to%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20it%20to%20mean%20the%20following%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20605px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F124386i9DAFC0A85A4F91F8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22TLS.JPG%22%20title%3D%22TLS.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20that%20is%20the%20case%20then%20the%20short%20answer%20is%20that%20we%20must%20upgrade%20or%20replace%20any%20devices%20and%20applications%20that%20authenticate%20to%20the%20SMTP%20server%20that%20don't%20use%20TLS%201.2%20and%20we%20don't%20have%20to%20worry%20about%20any%20devices%20or%20applications%20that%20don't%20authenticate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20that%20how%20other%20see%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-778560%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-778560%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353684%22%20target%3D%22_blank%22%3E%40hobbssj%3C%2FA%3EThe%20Connector%20report%20link%20is%20not%20displayed%20is%20your%20tenant%20does%20not%20have%20any%20mail%20flow%20connectors.%20As%20mentioned%20above%2C%20you%20can%20still%20find%20it%20via%20the%20Reports%20dashboard%20although%20there%20is%20little%20action%20for%20you%20to%20take%20if%20you%20have%20no%20connectors.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F378601%22%20target%3D%22_blank%22%3E%40BGCBates%3C%2FA%3EThe%20Secure%20Trust%20Portal%20should%20be%20accessed%20via%20the%20Secure%20Score%20site%20so%20I'll%20have%20the%20blog%20edited%20to%20remove%20the%20portal%20link.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F378706%22%20target%3D%22_blank%22%3E%40Hong_Kong_Techpro_GM%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F378965%22%20target%3D%22_blank%22%3E%40JohnnyReaction%3C%2FA%3EAs%20a%20service%20accepting%20connections%2C%20we%20have%20limited%20insights%20into%20what%20servers%2C%20applications%2C%20or%20devices%20you%20are%20using%20to%20connect%20to%20us.%20This%20blog%20and%20reports%20can%20only%20help%20you%20identify%20which%20of%20your%20mail%20flow%20connectors%20or%20mailboxes%20are%20associated%20with%20non-TLS1.2%20usage.%20You%20need%20to%20determine%20which%20servers%20are%20associated%20with%20that%20connector%20or%20which%20clients%20or%20devices%20are%20associated%20with%20sending%20from%20that%20mailbox.%20We%20also%20do%20not%20produce%20most%20of%20those%20devices%20or%20software%20connecting%20to%20us%20so%20the%20instructions%20and%20steps%20to%20upgrade%20them%20to%20start%20using%20TLS1.2%20are%20not%20known%20by%20us.%20The%20onus%20is%20on%20you%20to%20contact%20those%20manufacturers%20if%20you%20do%20not%20know%20how%20to%20upgrade%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376993%22%20target%3D%22_blank%22%3E%40Deezu%3C%2FA%3EIf%20you%20do%20not%20want%20to%20or%20cannot%20upgrade%20a%20device%20or%20software%20that%20is%20not%20using%20TLS1.2%2C%20then%20you%20will%20need%20to%20set%20up%20your%20own%20local%20Exchange%20server%20or%20other%20mail%20server%20on-premises%20that%20supports%20TLS1.0%20and%20TLS1.2.%20You%20devices%20would%20connect%20to%20it%20locally%20on%20your%20network%20using%20TLS1.0%20and%20then%20it%20would%20connect%20to%20Office%20365%20using%20TLS1.2.%20You%20should%20be%20able%20to%20find%20instructions%20on%20how%20to%20set%20up%20an%20Exchange%20Server%20with%20Office%20365%20very%20easily%20online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4770%22%20target%3D%22_blank%22%3E%40John%20Twohig%3C%2FA%3EMail%20flow%20between%20email%20servers%20uses%20%22plain%22%20SMTP%20instead%20of%20SMTP%20AUTH.%20However%20there%20still%20may%20be%20authentication%20involved%20such%20as%20when%20mail%20flow%20connectors%20are%20used.%20for%20example%2C%20if%20you%20have%20a%20connector%20that%20forces%20the%20use%20of%20TLS%20and%20is%20currently%20using%20TLS1.0%2C%20then%20when%20TLS1.0%20is%20disabled%20by%20us%2C%20emails%20will%20fail%20to%20send.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783724%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783724%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhether%20this%20report%20will%20update%20everyday%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783815%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783815%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20report%20is%20giving%20me%20contradictory%20information%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReport%20shows%203%20clients%20still%20%22not%22%20using%20TLS1.2%20in%20the%20last%207%20days.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20go%20to%20details%20and%20download%20the%20custom%20report%20to%20show%20the%20TLS%20versions%20and%20ciphers%20-%20which%20incidentally%20I've%20just%20spent%20a%20few%20hours%20updating%20to%20TLS1.2%20earlier%20this%20week%20-%20and%20lo%20and%20behold%20it%20shows%20that%20ALL%20THREE%20clients%20are%20ACTUALLY%20using%20TLS1.2.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20explain%20what%20else%20should%20be%20done%20or%20what%20I'm%20missing.%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-609278%22%20slang%3D%22en-US%22%3EInvestigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-609278%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EUPDATE%3A%3C%2FSTRONG%3E%26nbsp%3BThe%20dates%20for%20disabling%20of%20TLS1.0%20and%20TLS1.1%20in%20Office%20365%20have%20been%20set.%20As%20things%20stand%2C%20the%20date%20for%20Office%20365%20WW%20and%20GCC%20customers%20is%20June%202020.%20More%20information%20can%20be%20found%20here.%20The%20date%20for%20Office%20365%20GCC-High%20and%20DOD%20customers%20is%20January%202020%20and%20more%20information%20can%20be%20found%20here.%20These%20dates%20are%20subject%20to%20change%20so%20please%20consult%20the%20links%20above%20for%20the%20latest%20information.%3C%2FP%3E%0A%3CP%3EMicrosoft%20is%20committed%20to%20enforcing%20the%20best%20security%20for%20our%20services.%20As%20a%20result%2C%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4057306%2Fpreparing-for-tls-1-2-in-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETLS1.0%2C%20TLS1.1%2C%20and%203DES%20were%20deprecated%3CI%3E%20%3C%2FI%3Ein%20the%20Office%20365%20service%3C%2FA%3E.%20While%203DES%20is%20currently%20in%20the%20process%20of%20being%20disabled%2C%20there%20is%20no%20date%20set%20for%20disabling%20TLS1.0%20and%20TLS1.1.%20That%20said%2C%20we%20are%20working%20towards%20disabling%20these%20TLS%20versions%20for%20Exchange%20Online%20endpoints.%20Should%20TLS1.0%20be%20compromised%2C%20we%20will%20have%20to%20act%20quickly%20to%20disable%20it%20in%20our%20service%20to%20protect%20our%20customers.%20In%20the%20case%20of%20SSL3.0%2C%20we%20disabled%20it%20in%20the%20service%20just%20over%20a%20month%20after%20the%20compromise%20was%20disclosed.%20Therefore%2C%20we%20urge%20you%20to%20be%20proactive%20by%20verifying%20TLS1.2%20support%20for%20all%20of%20your%20email%20clients%20and%20servers%20as%20soon%20as%20possible.%20For%20inbound%20and%20outbound%20connections%20with%20email%20servers%20and%20devices%20that%20are%20exposed%20to%20the%20internet%2C%20TLS1.0%20usage%20is%20still%20around%205%25.%20In%20most%20cases%2C%20TLS%20usage%20is%20optional%20for%20messages%20that%20are%20sent%20and%20received%20on%20the%20internet.%20There%20are%20certain%20scenarios%20where%20TLS%20is%20mandatory%2C%20and%20if%20TLS1.0%20is%20turned%20off%20in%20Exchange%20Online%2C%20mail%20flow%20will%20be%20affected.%20For%20example%2C%20over%2010%25%20of%20connections%20from%20customer%20on-premises%20email%20servers%20and%20devices%20still%20use%20TLS1.0.%20Even%20worse%20are%20the%20legacy%20SMTP%20Auth%20client%20submissions%20that%20are%20used%20by%20multi-function%20printers%20and%20applications%20that%20need%20to%20send%20email.%20For%20the%20SMTP%20Auth%20protocol%2C%20just%20less%20than%2050%25%20of%20connections%20are%20still%20using%20TLS1.0.%20These%20are%20likely%20old%20printers%20or%20legacy%20applications%20that%20either%20have%20not%20or%20cannot%20be%20updated%20to%20use%20TLS1.2.%20To%20help%20you%20identify%20if%20your%20organization%20is%20contributing%20to%20those%20numbers%2C%20we%20have%20developed%20several%20reports%20for%20Exchange%20Online.%20You%20can%20use%20these%20reports%20to%20help%20determine%20which%20clients%20and%20servers%20are%20still%20using%20TLS1.0%20and%20TLS1.1%20to%20connect%20to%20the%20various%20email%20protocol%20endpoints%20in%20Exchange%20Online.%20These%20reports%20can%20be%20found%20in%20the%20Security%20and%20Compliance%20Center%20under%20the%20Mail%20Flow%20Dashboard.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1760056127%22%20id%3D%22toc-hId-1760056127%22%20id%3D%22toc-hId-1760056127%22%20id%3D%22toc-hId-1760056127%22%3EEmails%20between%20your%20on-premises%20or%20partner%20email%20servers%20and%20Exchange%20Online%3C%2FH2%3E%0A%3CP%3EThird-party%20email%20servers%20sending%20and%20receiving%20email%20to%20and%20from%20our%20customers%20are%20normally%20beyond%20our%20control%20(or%20even%20the%20control%20of%20our%20customers).%20However%2C%20your%20on-premises%20or%20partner%20email%20servers%20are%20easily%20identified%20because%20their%20connections%20to%20and%20from%20Exchange%20Online%20use%20mail%20flow%20connectors.%20Exchange%20Online%20relies%20on%20successful%20TLS%20negotiations%20and%20certificates%20to%20identify%20and%20use%20the%20correct%20inbound%20connector.%20You%20can%20also%20configure%20outbound%20connectors%20to%20force%20the%20use%20of%20TLS.%20If%20a%20connector%20with%20forced%20TLS%20uses%20TLS1.0%20today%2C%20messages%20will%20fail%20to%20send%20when%20TLS1.0%20is%20disabled%20in%20Exchange%20Online.%20To%20help%20identify%20servers%20that%20require%20updating%20to%20TLS1.2%2C%20we%20have%20developed%20the%20Connector%20Report%2C%20which%20is%20available%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2F%23%2Fmailflow%2Fdashboard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMail%20Flow%20Dashboard%3C%2FA%3E%20in%20the%20Security%20and%20Compliance%20Center.%20To%20access%20the%20report%2C%20click%20%3CSTRONG%3EView%20Details%3C%2FSTRONG%3E%20and%20then%20the%20%3CSTRONG%3EConnector%20Report%3C%2FSTRONG%3E%20link.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F03%2FTLSreport1.png%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20class%3D%22%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F03%2FTLSreport1_thumb.png%22%20border%3D%220%22%20alt%3D%22TLSreport1%22%20title%3D%22TLSreport1%22%20width%3D%22891%22%20height%3D%22440%22%20%2F%3E%3C%2FA%3E%20The%20Connector%20Report%20allows%20you%20to%20review%20mail%20flow%20volume%20or%20TLS%20usage%20for%20a%20specific%20connector%2C%20or%20traffic%20to%20and%20from%20the%20internet%20that%20does%20not%20use%20a%20connector.%26nbsp%3B%20The%20numbers%20behind%20the%20charts%20are%20available%20in%20the%20Details%20Table.%20For%20detailed%20information%20on%20the%20messages%20involved%20(including%20if%203DES%20is%20being%20used)%2C%20you%20can%20download%20the%20data%20using%20the%20%3CSTRONG%3ERequest%20report%3C%2FSTRONG%3E%20feature.%20From%20that%20data%2C%20you%20can%20identify%20the%20exact%20server%20or%20device%2C%20and%20you%20can%20attempt%20to%20upgrade%20the%20server%20or%20device%20to%20TLS1.2.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--792100834%22%20id%3D%22toc-hId--792100834%22%20id%3D%22toc-hId--792100834%22%20id%3D%22toc-hId--792100834%22%3EEmail%20submitted%20using%20the%20legacy%20SMTP%20Auth%20client%20submission%20protocol%3C%2FH2%3E%0A%3CP%3EEmail%20clients%20can%20submit%20email%20messages%20using%20several%20different%20protocols.%20The%20SMTP%20Auth%20protocol%20is%20a%20widely%20supported%20protocol%20that%E2%80%99s%20used%20primarily%20by%20devices%20and%20applications%20that%20send%20automated%20messages%20on%20behalf%20of%20customers.%20Examples%20include%20scanner%20to%20email%20devices%2C%20or%20applications%20that%20send%20out%20alerts%20or%20notifications.%20SMTP%20Auth%20is%20identified%20by%20its%20endpoint%20%3CSTRONG%3Esmtp.office365.com%3C%2FSTRONG%3E.%20To%20protect%20against%20the%20disclosure%20of%20credentials%2C%20TLS%20is%20mandatory%20for%20SMTP%20Auth.%20This%20means%20that%20when%20TLS1.0%20is%20disabled%2C%20no%20messages%20can%20be%20sent%20from%20devices%20or%20clients%20that%20do%20not%20support%20TLS1.2.%20To%20help%20identify%20which%20of%20your%20devices%20and%20applications%20are%20still%20using%20TLS1.0%2C%20we%20have%20created%20the%20SMTP%20Auth%20Clients%20report.%20This%20report%20is%20available%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2F%23%2Fmailflow%2Fdashboard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMail%20Flow%20Dashboard%3C%2FA%3E%20where%20its%20widget%20displays%20the%20number%20of%20mailboxes%20that%20have%20used%20SMTP%20Auth%20in%20the%20last%20week.%20The%20report%20displays%20pivots%20for%20sending%20volume%20and%20TLS%20version%20usage.%20The%20details%20table%20provides%20the%20individual%20users%20or%20system%20accounts%20and%20their%20volume%20or%20TLS%20usage.%20You%20can%20also%20download%20the%20data%20using%20the%20%3CSTRONG%3ERequest%20report%3C%2FSTRONG%3E%20feature%2C%20which%20includes%20information%20about%20whether%20or%20not%203DES%20is%20being%20used.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F03%2FTLSreport2.png%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20class%3D%22%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F03%2FTLSreport2_thumb.png%22%20border%3D%220%22%20alt%3D%22TLSreport2%22%20title%3D%22TLSreport2%22%20width%3D%22876%22%20height%3D%22474%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3ESean%20Stevenson%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-609278%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETips%20'n%20Tricks%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Etransport%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-820826%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-820826%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F381708%22%20target%3D%22_blank%22%3E%40CTI_Support%3C%2FA%3E%26nbsp%3B-%20I'm%20in%20the%20same%20boat%20as%20you.%20We%20have%20an%20application%20that%20show%20they%20are%20sending%20as%20TLS%201.0%20and%20TLS%201.2.%20There's%20no%20details%20as%20to%20what%20message%20are%20sent%20using%20what%20protocol.%20It's%20hard%20to%20find%20out%20why%20the%20system%20delivers%20as%20either%20protocol.%20I%20even%20looked%20at%20the%20message%20trace%20and%20found%20all%20the%20ones%20sent%20by%20this%20system%20and%20it%20shows%20it%20was%20delivered%20with%20TLS%201.2.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20clue%20how%20to%20identify%20which%20emails%20were%20sent%20with%20TLS%201.0.%20This%20needs%20some%20improvement%20to%20help%20us%20track%20this%20down.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-926483%22%20slang%3D%22en-US%22%3ERe%3A%20Investigating%20TLS%20usage%20for%20SMTP%20in%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-926483%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20same%20problem%20with%20the%20report.%26nbsp%3BWe%20have%20an%20account%20in%20office%20365%2C%20it%20is%20used%20to%20send%20mail%20from%20Power%20BI%20(with%20password).%20The%20report%20shows%20that%201.2%20and%201.0%20are%20used.%20The%20same%20problem%20is%20with%20another%20account%20that%20is%20used%20in%20sql%202017.%3C%2FP%3E%3C%2FLINGO-BODY%3E

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 date for Office 365 GCC-High and DOD customers is January 2020 and more information can be found here. These dates are subject to change so please consult the links above for the latest information.

Microsoft is committed to enforcing the best security for our services. As a result, TLS1.0, TLS1.1, and 3DES were deprecated in the Office 365 service. While 3DES is currently in the process of being disabled, there is no date set for disabling TLS1.0 and TLS1.1. That said, we are working towards disabling these TLS versions for Exchange Online endpoints. Should TLS1.0 be compromised, we will have to act quickly to disable it in our service to protect our customers. In the case of SSL3.0, we disabled it in the service just over a month after the compromise was disclosed. Therefore, we urge you to be proactive by verifying TLS1.2 support for all of your email clients and servers as soon as possible. For inbound and outbound connections with email servers and devices that are exposed to the internet, TLS1.0 usage is still around 5%. In most cases, TLS usage is optional for messages that are sent and received on the internet. There are certain scenarios where TLS is mandatory, and if TLS1.0 is turned off in Exchange Online, mail flow will be affected. For example, over 10% of connections from customer on-premises email servers and devices still use TLS1.0. Even worse are the legacy SMTP Auth client submissions that are used by multi-function printers and applications that need to send email. For the SMTP Auth protocol, just less than 50% of connections are still using TLS1.0. These are likely old printers or legacy applications that either have not or cannot be updated to use TLS1.2. To help you identify if your organization is contributing to those numbers, we have developed several reports for Exchange Online. You can use these reports to help determine which clients and servers are still using TLS1.0 and TLS1.1 to connect to the various email protocol endpoints in Exchange Online. These reports can be found in the Security and Compliance Center under the Mail Flow Dashboard.

Emails between your on-premises or partner email servers and Exchange Online

Third-party email servers sending and receiving email to and from our customers are normally beyond our control (or even the control of our customers). However, your on-premises or partner email servers are easily identified because their connections to and from Exchange Online use mail flow connectors. Exchange Online relies on successful TLS negotiations and certificates to identify and use the correct inbound connector. You can also configure outbound connectors to force the use of TLS. If a connector with forced TLS uses TLS1.0 today, messages will fail to send when TLS1.0 is disabled in Exchange Online. To help identify servers that require updating to TLS1.2, we have developed the Connector Report, which is available in our Mail Flow Dashboard in the Security and Compliance Center. To access the report, click View Details and then the Connector Report link. TLSreport1 The Connector Report allows you to review mail flow volume or TLS usage for a specific connector, or traffic to and from the internet that does not use a connector.  The numbers behind the charts are available in the Details Table. For detailed information on the messages involved (including if 3DES is being used), you can download the data using the Request report feature. From that data, you can identify the exact server or device, and you can attempt to upgrade the server or device to TLS1.2.

Email submitted using the legacy SMTP Auth client submission protocol

Email clients can submit email messages using several different protocols. The SMTP Auth protocol is a widely supported protocol that’s used primarily by devices and applications that send automated messages on behalf of customers. Examples include scanner to email devices, or applications that send out alerts or notifications. SMTP Auth is identified by its endpoint smtp.office365.com. To protect against the disclosure of credentials, TLS is mandatory for SMTP Auth. This means that when TLS1.0 is disabled, no messages can be sent from devices or clients that do not support TLS1.2. To help identify which of your devices and applications are still using TLS1.0, we have created the SMTP Auth Clients report. This report is available in the Mail Flow Dashboard where its widget displays the number of mailboxes that have used SMTP Auth in the last week. The report displays pivots for sending volume and TLS version usage. The details table provides the individual users or system accounts and their volume or TLS usage. You can also download the data using the Request report feature, which includes information about whether or not 3DES is being used. TLSreport2

 

Sean Stevenson

31 Comments
Not applicable
Thanks
New Contributor

Does this Connected Report still exist, I cannot seem to find it anywhere?

Senior Member

https://protection.office.com/mailflow/dashboard --> Outbound and Inbound mail flow --> View Details --> Connector Report.

New Contributor

Thanks for the update, however I do not see the link for the connector report here. I believe it was orignaly a link in this block of text, as seen in this link

https://docs.microsoft.com/en-us/office365/securitycompliance/mfi-outbound-and-inbound-mail-flow

 

but the image below is what I see now, I'd be intrested to know if this is isolated to us, or if other people are having similar issues.

 

Also does anyone know if anything needs to be configured before this link becomes avalable?

 

 

2019-07-17_8-22-27.jpg

Established Member

we have download the secure trust portal and even it shows Tls1.2 machine in the report. we have opened many tickets with your support team and it is not worth....

 

related to smtp client auth report. can you please tell us whether they access the smtp connections through application or mobile device.

Senior Member
@hobbssj I am having the same issue. The connector report link is missing for us as well.
Visitor

Some information on how to go about resolving these issues would be great. Even if its just a few links to get us started. Also, could you not also capture the IP address / hostname of the device(s) to show in that report. Some of our users have quite a few devices and its not always clear which one is the culprit

New Contributor

I have opened a Support ticket for what its worth, I post the results afterword's.

Frequent Visitor

"Even worse are the legacy SMTP Auth client submissions that are used by multi-function printers and applications that need to send email" 

 

What is the solution here? We have several MFP that are nowhere near EOL.

Occasional Contributor

Eric Bostrom for legacy applications you can follow this article: To start addressing weak TLS use by removing TLS 1.0 and 1.1 dependencies, see TLS 1.2 support at Microsoft.

 

for MFP you can use their Multifunction: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-dev...

 

Occasional Visitor

@hobbssj @mikeh1974 go to reports and select the connector report from there

New Contributor

Thanks that seem to work. 

 

Senior Member
Thank you
Frequent Visitor

"You can use these reports to help determine which clients and servers are still using TLS1.0 and TLS1.1 to connect to the various email protocol endpoints in Exchange Online."

 

Edit1: Click 'Request Report' to get the level of detail you need to identify hosts.

 

Edit2: This worked great to get tls1.2 working on server16/sql16sp2.

Senior Member
@Eric Bostrom you can see more details when you request the report. The report you receive in your email will have that information.
Frequent Visitor

Thanks, figured that out after posting but can't delete comment ;)

Visitor

Is the link provided here working for any one else?

"This will take you to the Secure Trust Portal where you can download your TLS 1.0/1.1 and 3DES reports."

 

It just shows up with the my Office  365 banner across the top but no content.

New Contributor

If you can't get to the Smtp Client Submission Report ussing the dashboard, try:

https://protection.office.com/reportv2?id=SmtpClientSubmissionReport&pivot=SenderDomain

 

Cheers.

Occasional Visitor

Being a complete IT luddite, I'd like to know exactly how to do the update - we have just lost our IT support which has now left us with a bit of a problem as half the team (in a remote location) are on TLS1 (from the report I just obtained) and bearing in mind the update from Office Centre re moving to TLS1.2 asap, I'd like to know how I achieve that.

Occasional Visitor

This is as clear as mud.

 

Prey tell, Microsoft, just what exactly do I need to do to ensure the mail continues to flow?

Occasional Visitor

@JohnnyReaction Agreed. I have an MFP that sends scans to users that I'm confident isn't going to be compromised, and the other account is for sending password reminders to users who don't have domain joined computers that get a change password pop-up. Again, I'm confident that account won't be compromised. It's all well and good for MS to tell us what accounts are using the older TLS module. But they don't provide any fix or solution to allow it to continue for those handful of accounts that we want to continue using this.

Regular Visitor

Here is a way to view the connector report.  MS likes to hide things and not update documentation:

2019-07-19 08_56_30-Dashboard - Security & Compliance.png2019-07-19 08_58_03-Report Viewer - Security & Compliance.png

Visitor

@Shawn Housler Don't worry that will change in the re-design that will be introduced next week with a re-design again two weeks after that.

Regular Visitor

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!

Occasional Visitor

Has any one found a way to trace a smtp message when it shows a smtp message was sent on a certain date with TLS1.0? 

 

How do we go about getting reports for older dates, I was trying to request the SMTP Auth Clients Report but only allows me to go back to June 29th.

 

We have identified an smtp event on June 28th using an older TLS but we are having trouble tracking down that actual message, when I pull detailed reports they all shows TLS 1.2.  What other reports are people using to help identify messages sent with older TLS?

Contributor

From what I can see from our environment there are emails being sent in two ways:

  1.  SMTP Auth - Authenticated 
  2. Unauthenticated

These emails can either use No TLS, TLS 1.0, TLS 1.1, or TLS 1.2.

 

What I think I got from the above is that any devices or applications that authenticate but don't use TLS 1.2 will fail beginning June 1, 2020. It also looks like any devices that send mail using the Office 365 SMTP server that don't authenticate will continue to work. 

 

I understand it to mean the following:

TLS.JPG

 

If that is the case then the short answer is that we must upgrade or replace any devices and applications that authenticate to the SMTP server that don't use TLS 1.2 and we don't have to worry about any devices or applications that don't authenticate.

 

Is that how other see it?

Regular Visitor

@hobbssjThe Connector report link is not displayed is your tenant does not have any mail flow connectors. As mentioned above, you can still find it via the Reports dashboard although there is little action for you to take if you have no connectors.

 

@BGCBatesThe Secure Trust Portal should be accessed via the Secure Score site so I'll have the blog edited to remove the portal link.

 

@Hong_Kong_Techpro_GM@JohnnyReactionAs a service accepting connections, we have limited insights into what servers, applications, or devices you are using to connect to us. This blog and reports can only help you identify which of your mail flow connectors or mailboxes are associated with non-TLS1.2 usage. You need to determine which servers are associated with that connector or which clients or devices are associated with sending from that mailbox. We also do not produce most of those devices or software connecting to us so the instructions and steps to upgrade them to start using TLS1.2 are not known by us. The onus is on you to contact those manufacturers if you do not know how to upgrade them.

 

@DeezuIf you do not want to or cannot upgrade a device or software that is not using TLS1.2, then you will need to set up your own local Exchange server or other mail server on-premises that supports TLS1.0 and TLS1.2. You devices would connect to it locally on your network using TLS1.0 and then it would connect to Office 365 using TLS1.2. You should be able to find instructions on how to set up an Exchange Server with Office 365 very easily online.

 

@John TwohigMail flow between email servers uses "plain" SMTP instead of SMTP AUTH. However there still may be authentication involved such as when mail flow connectors are used. for example, if you have a connector that forces the use of TLS and is currently using TLS1.0, then when TLS1.0 is disabled by us, emails will fail to send.

Established Member

Hi,

 

whether this report will update everyday

Occasional Visitor

The report is giving me contradictory information:

 

Report shows 3 clients still "not" using TLS1.2 in the last 7 days.

 

I go to details and download the custom report to show the TLS versions and ciphers - which incidentally I've just spent a few hours updating to TLS1.2 earlier this week - and lo and behold it shows that ALL THREE clients are ACTUALLY using TLS1.2.

 

Please explain what else should be done or what I'm missing.

Thanks.

New Contributor

@CTI_Support - I'm in the same boat as you. We have an application that show they are sending as TLS 1.0 and TLS 1.2. There's no details as to what message are sent using what protocol. It's hard to find out why the system delivers as either protocol. I even looked at the message trace and found all the ones sent by this system and it shows it was delivered with TLS 1.2. 

 

I have no clue how to identify which emails were sent with TLS 1.0. This needs some improvement to help us track this down. 

Occasional Visitor

The same problem with the report. We have an account in office 365, it is used to send mail from Power BI (with password). The report shows that 1.2 and 1.0 are used. The same problem is with another account that is used in sql 2017.