Provisioning Guide for Lync-Skype Connectivity

Now and after having the Lync-Skype Connectivity officially released,  you can download the Provisioning Guide for Lync-Skype Connectivity at this location.

few things to note. in order to make lync-skype connectivity available, if your organization is already provisioned for MSN

1 – You don’t have to reprovision or initiate a provisioning request for  skype so you can skip the provisioning part and jump directly to the Lync Server configuration, which consists of the following.

1 – Remove the existing Public Provider for Messenger

Remove-CsPublicProvider -Identity Messenger
2 – add a New Public Provider  for Skype

New-CsPublicProvider -Identity Skype -ProxyFqdn -IconUrl “” -VerificationLevel 2 -Enabled 1

you will notice that the Proxy Server  and even the icon URL for the Messenger and skype providers are the same, however they have verification levels.

once the Server configuration changes are applied, Lync users can start adding skype users to their contact list using skype MSA accounts which means skype users must sign in to skype with a Microsoft account formely known by Windows Live ID in order to communicate with Lync contacts.


Experienced Consultant Team Lead with a demonstrated history of working in the information technology and services industry. Skilled in Azure, Skype for Business, SQL Server, Iaas, Saas, PaaS, ITIL, Microsoft Solutions, and Servers. Strong information technology professional, technology passionate.

Posted in Messaging & Collaboration Tagged with: , , , ,
2 comments on “Provisioning Guide for Lync-Skype Connectivity
  1. Ted Dasher says:

    Thanks for the condensed version. It took me less than five minutes to get things going. One minor note, if you are using Lync 2010 you need to skip the -IconUrl switch when adding Skype.

  2. Charbel Hanna says:

    Thank you Ted,
    Regarding the iconrul configuration, you can leave it and if using lync 2010 clients this setting will be ignored.

Leave a Reply

Your email address will not be published. Required fields are marked *