Topic Last Modified: 2013-10-07

Federation, public instant messaging connectivity and Extensible Messaging and Presence Protocol (XMPP) define a different class of external users – Federated users. Users of a federated Lync Server deployment or XMPP deployment have access to a limited set of services and are authenticated by the external deployment. Remote users are members of your Lync Server deployment and have access to all services offered by your deployment.

An end of life date of June 2014 for AOL and Yahoo! has been announced. For details, see Support for public instant messenger connectivity.

Public instant messaging connectivity is a special type of federation that allows a Lync Server client to access configured public Instant Messaging partners using the Lync 2013. The current public instant messaging connectivity partners are:

A public instant messaging connectivity configuration allows Lync users access to public instant messaging connectivity users by:

Lync Server federation defines an agreement between your Lync Server deployment and other Office Communications Server 2007 R2 or Lync Server deployments. A Lync Server federated configuration allows Lync users access to federated users by:

XMPP federation defines an external deployment based on the eXtensible Messaging and Presence Protocol. An XMPP configuration allows Lync users access to allowed XMPP domain users by:

The XMPP capability of Lync Server 2013 is tested and supported by Microsoft for instant messaging federation with Google Talk. For any other XMPP systems contact the third-party vendor to verify that they support federation with Lync Server 2013, and for any deployment or troubleshooting recommendations.

Edge Server External Federation, Public Instant Messaging Connectivity and XMPP Users Deployment Process

Phase Steps Permissions Documentation

Determine the options to add to the existing Edge deployment

Run Topology Builder to edit Edge Server settings and create and publish the topology. Your existing Edge topology will replicate changes from the Central Management store to the Edge Server.

Domain Admins group and RTCUniversalServerAdmins group

You can edit a topology using an account that is a member of the local users group, but publishing a topology requires an account that is a member of the Domain Admins group and the RTCUniversalServerAdmins group

Building an Edge and Director Topology

Prepare for setup

  1. Ensure that system prerequisites are met.

  2. Configure internal and external DNS records, to support public instant messaging connectivity, Lync Federation and XMPP Federation

  3. Configure ports and protocols at the firewall to support the types of federation that you are deploying

  4. Obtain and install public certificates. The time required to obtain certificates depends on which certification authority (CA) issues the certificate. This step is optional at this point in the deployment. If you do not perform this step at this point, you must do it during Edge Server configuration. The Edge Server service cannot be started until certificates are obtained

As appropriate to your organization, as these roles are typically split amongst numerous work groups

Planning for SIP, XMPP Federation and Public Instant Messaging

Set up Edge Servers for Federation Scenarios

  1. Transport the exported topology configuration file to each Edge Server or allow replication to complete

  2. Re-Run the Deployment Wizard to install supporting components for Federation

  3. Configure the Edge Servers

  4. Request and install certificates for each Edge Server

  5. Restart the Edge Server services

Administrators group

Setting Up Lync Federation

Setting Up Public Instant Messaging Connectivity

Setting Up XMPP Federation

Configure support for external user access.

  1. Use the Lync Server Control Panel External User Access

  2. Configure External Access Policy to enable Communications with federated users or public users

  3. Configure SIP Federated Domains to Allow or Block domains

  4. Enable SIP Federated Providers for public instant messaging connectivity providers

  5. Configure XMPP Federated Partners per XMPP domain

RTCUniversalServerAdmins group or user account that is assigned to the CSAdministrator role

Configuring Support for External User Access

Configure Media Encryption for Public Providers

Verify your Edge Server configuration

Verify server connectivity and replication of configuration data from internal servers

For verification of replication, RTCUniversalServerAdmins group or user account that is assigned to the CSAdministrator roleFor verification of user connectivity, a user for each type of Federated user

Verifying Your Edge Deployment

Example XMPP Configuration – XMPP Federation with Google Talk