TLS certificate changes to Microsoft 365 services including Microsoft Teams

Published Mar 09 2022 08:00 AM 11.7K Views
Microsoft

Microsoft 365 is updating services powering messaging, meetings, telephony, voice, and video to use TLS certificates from a different set of Root Certificate Authorities (CAs). This change is being made because the current Root CA will expire in May 2025.


Affected products include:

  • Microsoft Teams
  • Skype
  • Skype for Business Online
  • Microsoft Dynamics 365
  • GroupMe
  • Kaizala
  • Azure Communication Services

Affected endpoints include (but are not limited to):

  • *.teams.microsoft.com
  • *.skype.com
  • *.skypeforbusiness.com
  • *.groupme.com
  • *.communication.azure.com
  • *.operatorconnect.microsoft.com

Additionally, Teams and Skype for Business Online endpoints in US Government national cloud instances of Microsoft 365 will make the same change, affecting endpoints such as:

  • *.gcc.teams.microsoft.com
  • *.dod.teams.microsoft.us
  • *.gov.teams.microsoft.us
  • *.online.dod.skypeforbusiness.us
  • *.online.gov.skypeforbusiness.us
  • *.um-dod.office365.us
  • *.um.office365.us

Services began transitioning to the new Root CAs beginning in January 2022 and will continue through October 2022.


The new Root CA "DigiCert Global Root G2" is widely trusted by operating systems including Windows, macOS, Android, and iOS and by browsers such as Microsoft Edge, Chrome, Safari, and Firefox. We expect that most Microsoft 365 customers will not be impacted.


However, your application may be impacted if it explicitly specifies a list of acceptable CAs. This practice is known as "certificate pinning". Customers who do not have the new Root CAs in their list of acceptable CAs will receive certificate validation errors, which may impact the availability or function of your application.


For more details on how to determine if you are affected by this change as well as the details of the new Root CAs, please refer to the technical guidance at Office TLS Certificate Changes.

13 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-3249676%22%20slang%3D%22en-US%22%3ETLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3249676%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20365%20is%20updating%20services%20powering%20messaging%2C%20meetings%2C%20telephony%2C%20voice%2C%20and%20video%20to%20use%20TLS%20certificates%20from%20a%20different%20set%20of%20Root%20Certificate%20Authorities%20(CAs).%20This%20change%20is%20being%20made%20because%20the%20current%20Root%20CA%20will%20expire%20in%20May%202025.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EAffected%20products%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EMicrosoft%20Teams%3C%2FLI%3E%0A%3CLI%3ESkype%3C%2FLI%3E%0A%3CLI%3ESkype%20for%20Business%20Online%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20Dynamics%20365%3C%2FLI%3E%0A%3CLI%3EGroupMe%3C%2FLI%3E%0A%3CLI%3EKaizala%3C%2FLI%3E%0A%3CLI%3EAzure%20Communication%20Services%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EAffected%20endpoints%20include%20(but%20are%20not%20limited%20to)%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E*.teams.microsoft.com%3C%2FLI%3E%0A%3CLI%3E*.skype.com%3C%2FLI%3E%0A%3CLI%3E*.skypeforbusiness.com%3C%2FLI%3E%0A%3CLI%3E*.groupme.com%3C%2FLI%3E%0A%3CLI%3E*.communication.azure.com%3C%2FLI%3E%0A%3CLI%3E*.operatorconnect.microsoft.com%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EAdditionally%2C%20Teams%20and%20Skype%20for%20Business%20Online%20endpoints%20in%20US%20Government%20national%20cloud%20instances%20of%20Microsoft%20365%20will%20make%20the%20same%20change%2C%20affecting%20endpoints%20such%20as%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E*.gcc.teams.microsoft.com%3C%2FLI%3E%0A%3CLI%3E*.dod.teams.microsoft.us%3C%2FLI%3E%0A%3CLI%3E*.gov.teams.microsoft.us%3C%2FLI%3E%0A%3CLI%3E*.online.dod.skypeforbusiness.us%3C%2FLI%3E%0A%3CLI%3E*.online.gov.skypeforbusiness.us%3C%2FLI%3E%0A%3CLI%3E*.um-dod.office365.us%3C%2FLI%3E%0A%3CLI%3E*.um.office365.us%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EServices%20began%20transitioning%20to%20the%20new%20Root%20CAs%20beginning%20in%20January%202022%20and%20will%20continue%20through%20October%202022.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EThe%20new%20Root%20CA%20%22DigiCert%20Global%20Root%20G2%22%20is%20widely%20trusted%20by%20operating%20systems%20including%20Windows%2C%20macOS%2C%20Android%2C%20and%20iOS%20and%20by%20browsers%20such%20as%20Microsoft%20Edge%2C%20Chrome%2C%20Safari%2C%20and%20Firefox.%20We%20expect%20that%20%3CSTRONG%3Emost%20Microsoft%20365%20customers%20will%20not%20be%20impacted%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EHowever%2C%20%3CSTRONG%3Eyour%20application%20may%20be%20impacted%20if%20it%20explicitly%20specifies%20a%20list%20of%20acceptable%20CAs%3C%2FSTRONG%3E.%20This%20practice%20is%20known%20as%20%22certificate%20pinning%22.%20Customers%20who%20do%20not%20have%20the%20new%20Root%20CAs%20in%20their%20list%20of%20acceptable%20CAs%20will%20receive%20certificate%20validation%20errors%2C%20which%20may%20impact%20the%20availability%20or%20function%20of%20your%20application.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EFor%20more%20details%20on%20how%20to%20determine%20if%20you%20are%20affected%20by%20this%20change%20as%20well%20as%20the%20details%20of%20the%20new%20Root%20CAs%2C%20please%20refer%20to%20the%20technical%20guidance%20at%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fcompliance%2Fencryption-office-365-tls-certificates-changes%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EOffice%20TLS%20Certificate%20Changes%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-3249676%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20365%20is%20updating%20the%20Root%20Certificate%20Authorities%20for%20TLS%20certificates.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22MSC21_PICHA_remoteWorkplace_84197.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F354241i8EFF5C07F5D70EA9%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22MSC21_PICHA_remoteWorkplace_84197.jpg%22%20alt%3D%22MSC21_PICHA_remoteWorkplace_84197.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3249676%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3253355%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3253355%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1124444%22%20target%3D%22_blank%22%3E%40Parker_Shelton%3C%2FA%3E%26nbsp%3B%20-%20thanks%20for%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20page%20linked%20says%20that%20certificates%20that%20chain%20to%20the%20Baltimore%20certificate%20will%20be%20replaced%20to%20certificates%20that%20chain%20to%20one%20of%20three%20possible%20options%2C%20but%20you've%20only%20mentioned%20one%20on%20your%20blog%20post%20-%20is%20that%20confirmation%20that%20all%20of%20the%20Teams-related%20things%20will%20be%20using%20certificates%20that%20chain%20back%20to%20the%20%22DigiCert%20Global%20Root%20G2%22%20cert%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMore%20specifically%20-%20I%20maintain%20a%20lot%20of%20SBCs%20that%20connect%20to%20Teams%20for%20direct%20routing%20that%20currently%20have%20the%20Baltimore%20cert%20manually%20imported%20so%20they%20trust%20all%20the%20sip*.pstnhub.microsoft.com%20endpoints%3B%20do%20you%20know%20which%20certificate%20I%20will%20need%20to%20import%20in%20addition%2C%20and%20when%20by%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ERich%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3254164%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3254164%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1329129%22%20target%3D%22_blank%22%3E%40RichHall%3C%2FA%3E.%20Our%20team%20is%20working%20to%20reach%20out%20to%20all%20SBC%20vendors%20to%20communicate%20the%20upcoming%20changes%20and%20help%20them%20provide%20firmware%20updates%2C%20testing%20tools%2C%20and%20documentation%20changes%20for%20their%20customers.%20Microsoft%20is%20working%20to%20provide%20a%20dedicated%20SIP%2FTLS%20endpoint%20that%20will%20serve%20a%20certificate%20signed%20by%20the%20new%20CA%20that%20can%20be%20used%20to%20verify%20connectivity%20from%20SBCs%20using%20SIP%20OPTIONS%20pinging.%20Given%20the%20complexity%20of%20this%20piece%20of%20the%20migration%2C%20we%20don't%20expect%20SBCs%20to%20need%20to%20trust%20the%20new%20Root%20CAs%20until%20Sept%20or%20Oct%202022.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20new%20Intermediate%20CAs%20are%20%22cross-signed%22%20and%20should%20be%20considered%20valid%20if%20any%20of%20the%20three%20Root%20CA%20certificates%20are%20trusted.%20We%20would%20recommend%20installing%20all%20three%20but%20expect%20the%20%22DigiCert%20Global%20Root%20G2%22%20Root%20CA%20to%20be%20pre-installed%20in%20a%20number%20of%20OSes%20and%20devices%20and%20to%20be%20the%20simplest%20and%20most%20popular%20Root%20CA.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3256651%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3256651%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1124444%22%20target%3D%22_blank%22%3E%40Parker_Shelton%3C%2FA%3E%26nbsp%3B%20-%20that's%20great%2C%20thanks%20for%20the%20extra%20info.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20I'll%20play%20it%20safe%20and%20start%20adding%20all%20three%20certificates%20into%20the%20trusted%20store%20of%20the%20various%20SBCs%20I%20deploy%2Fmaintain%20next%20time%20I%20log%20on%20to%20each%20one%2C%26nbsp%3B%20to%20make%20sure%20I%20don't%20get%20caught%20out%20later%20on%20if%20I%20don't%20get%20a%20window%20to%20update%20to%20the%20latest%20firmware!%20(TBH%2C%20I%20don't%20think%20Ribbon%20have%20historically%20included%20any%20certs%20in%20their%20firmware%2C%20so%20it%20may%20end%20up%20being%20manual%20anyway).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3280083%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3280083%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20ref.%20to%20the%20above%20article%2C%20we%20understand%20that%20the%20impact%20is%20only%20if%20we%20you%20use%20an%20application%20that%20integrates%20with%20Microsoft%20Teams%2C%20Skype%2C%20Skype%20for%20Business%20Online%2C%20or%20Microsoft%20Dynamics%20APIs%20and%20also%20if%20it%20explicitly%20specifies%20a%20list%20of%20acceptable%20CAs.%3C%2FP%3E%3CP%3EIt%20will%20not%20affect%20the%20normal%20Microsoft%20Teams%20application.%3C%2FP%3E%3CP%3EPlease%20let%20us%20know%20if%20our%20understanding%20is%20correct.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3280315%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3280315%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1357769%22%20target%3D%22_blank%22%3E%40Bala159545%3C%2FA%3E.%20Your%20understanding%20is%20correct.%20No%20changes%20are%20required%20for%20normal%20users%20of%20the%20Skype%2C%20Teams%2C%20or%20Skype%20for%20Business%20applications.%20Microsoft's%20applications%20have%20already%20been%20updated%20to%20trust%20the%20list%20of%20new%20Root%20CAs.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3332162%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3332162%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20appears%20the%20root%20certificates%20were%20updated%20on%20April%2029th.%20We%20leverage%20the%20Cisco%20Cube%20SBC%20solution%20and%20it%20took%20us%20a%20bit%20to%20stumble%20upon%20the%20issue.%20It%20would%20be%20nice%20if%20a%20notice%20directly%20related%20to%20SBC%20was%20issued.%20A%20worked%20around%20existed%2C%20(disabling%20the%20CRL%20check%20on%20the%20router)%2C%20but%20this%20could%20have%20been%20avoided%20with%20proper%20notification.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3334565%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3334565%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20to%20hear%20about%20your%20issue%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82598%22%20target%3D%22_blank%22%3E%40James%20Oryszczyn%3C%2FA%3E.%20I'm%20not%20aware%20that%20anything%20changed%20yet%20in%20regard%20to%20SBC%20connectivity.%20Can%20you%20share%20the%20URL%20that%20you're%20connecting%20to%20so%20I%20can%20double-check%20with%20the%20team%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3336075%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3336075%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20was%20the%20URL%20causing%20issues%2C%26nbsp%3B%3C%2FP%3E%3CP%3E768%20Reason%20%3A%20Received%20400%20(Bad%20Request)%20from%20cdp%20%3A%3CA%20href%3D%22http%3A%2F%2Fcrl3.digicert.com%2FOmniroot2025.crl%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fcrl3.digicert.com%2FOmniroot2025.crl%3C%2FA%3E%3C%2FP%3E%3CP%3E%25PKI-3-CRL_FETCH_FAIL%3A%20CRL%20fetch%20for%20trustpoint%20baltimore%20failed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3339133%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3339133%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82598%22%20target%3D%22_blank%22%3E%40James%20Oryszczyn%3C%2FA%3E.%20I%20confirmed%20with%20the%20team%20that%20no%20root%20certificate%20changes%20have%20been%20made%20in%20the%20PSTN%20infrastructure.%20In%20fact%2C%20the%20error%20message%20you%20provided%20is%20related%20to%20the%20availability%20of%20the%20revocation%20information%20for%20the%20current%20root%20certificate%20from%20our%20third-party%20Certificate%20Authority%2C%20DigiCert.%20Please%20feel%20free%20to%20file%20a%20support%20request%20if%20we%20can%20help%20with%20any%20follow-up%20questions%20or%20concerns.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3361005%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3361005%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82598%22%20target%3D%22_blank%22%3E%40James%20Oryszczyn%3C%2FA%3E%26nbsp%3BWe%20are%20experiencing%20the%20exact%20same%20issue%20on%20Cisco%20CUBEs.%26nbsp%3B%20Thank%20you%20for%20posting%20this.%26nbsp%3B%20Is%20disabling%20the%20CRL%20check%20the%20only%20solution%20you've%20found%20that%20works%20or%20can%20we%20install%20the%20new%20roots%20to%20resolve%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3372016%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3372016%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20affected%20by%20this%20issue%20on%20our%20Cisco%20CUBE.%20We've%20tried%20to%20install%20the%203%20new%20root%20certificates%2C%20but%20the%20only%20way%20to%20work%20around%20this%20was%20to%20disable%20revocation-check%20in%20the%20trustpoint.%20If%20DigiCert%20is%20not%20providing%20the%20revocation%20information%20anymore%20for%20the%20Baltimore%20root%20CA%20it%20would%20be%20nice%20if%20Microsoft%20start%20using%20the%20new%20certificate%20authorities%20for%20SBC%20connections.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3372068%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3372068%22%20slang%3D%22en-US%22%3E%3CP%3ETyler%2C%20we%20did%20have%20chance%20yet%20to%20update%20the%20new%20root%20certs.%20It%20appears%20that%20is%20not%20a%20fix.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%2C%20we%20need%20a%20better%20answer%20to%20solve%20this%20issue.%26nbsp%3B%20I%20can%20tell%20you%20this%20stopped%20working%20on%20April%2025th%2C%20so%20something%20had%20to%20change%20in%20your%20environment..%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3372212%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%20certificate%20changes%20to%20Microsoft%20365%20services%20including%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3372212%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82598%22%20target%3D%22_blank%22%3E%40James%20Oryszczyn%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1389711%22%20target%3D%22_blank%22%3E%40rodarmbrust%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1387569%22%20target%3D%22_blank%22%3E%40Tyler_McCabe%3C%2FA%3E%26nbsp%3B-%20please%20file%20a%20support%20ticket%20so%20that%20we%20can%20collect%20the%20appropriate%20details%20about%20your%20setup%20and%20root-cause%20the%20issue%20with%20DigiCert.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Mar 09 2022 01:52 AM
Updated by: