locked
Skype for Business 2015 Edge External Certificate Common Name RRS feed

  • Question

  • Hi,

    Can we use "access.sipdomain.com" as subject name for SFB Edge External Certificate or we must use "sip.sipdomain.com"?

    any suggestion will be appreciated.

    Monday, March 25, 2019 6:01 PM

Answers

  • Hi Faisal.Sharif,

    Agree with Thiago, the Edge external certificate’s Subject Name should be the Access Edge Service FQDN you defined in the SFB Topology Builder, and you could customer the Access Edge Service FQDN. Normally, sip.sipdomain.com is the most used. 

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, March 26, 2019 2:45 AM

All replies

  • Hello!

    At the topology builder you can change the name, it is not a requisite, but generally is the most used.

    https://social.technet.microsoft.com/Forums/lync/en-US/ceb635b0-348f-4fdc-b26f-6127d97d595b/what-is-my-edge-servers-access-edge-external-interface-fully-qualified-domain-name-fqdn?forum=ocscertificates

    https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-edge-server/deploy-edge-server


    “Vote As Helpful” and/or “Mark As Answered” - MCSA - MCSE - http://www.ucsteps.com/

    Monday, March 25, 2019 10:51 PM
  • Hi Faisal.Sharif,

    Agree with Thiago, the Edge external certificate’s Subject Name should be the Access Edge Service FQDN you defined in the SFB Topology Builder, and you could customer the Access Edge Service FQDN. Normally, sip.sipdomain.com is the most used. 

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, March 26, 2019 2:45 AM