Still an internal deployment guide exists here Therefor we understand a CN identifier as FQDN of the Server or the Pool is RECOMMENDED!Ī valid SAN Wildcard certificate could look like this:Ī dedicated article to Skype for Business does not exits yet, you have to refer to: Environmental requirements for Skype for Business Server 2015.
Only if a server with in the Topology or for Federation purposes presents a valid certificate with its matching Common Name (CN) the entire traffic can be used with TLS/MTLS. Skype for Business is using the Common Name CN for authentication/ validation trusts. In Skype for Business the main reason for certificate use is TLS/MTLS data encryption and the other point it the server authentication/ validation. Coming back to the most common question about certificates in Skype for Business and Lync Server.Ĭan we use Wildcard Certificates in Skype for Business or Lync Server?įirst lets have a look into a certificate: A Certificate has a Common Name (CN) and Subject Alternative Names (SAN)Ī classic wildcard certificate is a certificate where the CN look like: CN=*.
