Prepare for Support of Public IM Connectivity

[This is preliminary content that is currently being developed, reviewed, and updated for the latest release of Lync Server. As a result, it may be incomplete or out of date. Blank topics are included as placeholders. Please send us your feedback, including what content you hoped to find or would find most useful.]  

Topic Last Modified: 2012-06-20

Supporting connectivity with public IM users in your organization requires that the appropriate licensing is in place and that the provisioning process for the public IM services that you want to support is complete. Provisioning can take up to thirty days, so allow sufficient time to complete the process prior to the date on which you want to implement support. For details about licensing requirements and how to complete the provisioning process, see the "Public IM Connectivity Provisioning Guide for Microsoft Lync Server, Office Communications Server, and Live Communications Server" at

If you are implementing audio/video (A/V) federation with Windows Live Messenger, there are two parameters that you need to modify: the Lync Server encryption level and the EnablePublicCloudAccess policy. By default, the encryption level is set to Required. You must change this setting to Supported. The EnablePublicCloudAccess policy is set to false, this needs to be set to true You can do this from the Lync Server Management Shell.

  1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013 Preview, and then click Lync Server Management Shell.

  2. From the command prompt, type the following commands:

    Set-CsMediaConfiguration -EncryptionLevel SupportEncryption
    Set-CsExternalAccessPolicy Global -EnablePublicCloudAccess $true -EnablePublicCloudAudioVideoAccess $true
    This example modifies the global policy. Change this to the appropriate policy in your environment.