Frequently Asked Questions: Provisioning Lync Server for Skype Connectivity
Topic Last Modified: 2013-11-07
Q: What features are supported between Microsoft Lync and Skype?
A: With Skype now part of the Microsoft family, new possibilities open up for extending unified communications scenarios to the hundreds of millions of people who use Skype. This combination will enable Lync customers to connect and collaborate with suppliers, customers, and partners, relying on the richness of Lync and the reach of Skype.
Instant Message and Audio Calls—Federated audio calling and instant messaging between Lync and Skype users
Presence Sharing— Exchange presence information between federated contacts
Simple Administration—Settings and controls to configure federated communications in accordance with your organization’s policies and standards
Q: How do I qualify to connect my Lync deployment with Skype?
A: You are licensed for Skype connectivity if you have either:
Lync Server (2010 or 2013) plus Lync Server Standard Client Access Licenses (“CALs”; 2010 or 2013) for the users and/or devices in your organization that will connect to Skype.
Lync Online (as standalone licenses or as part of an Office 365 suite). However, this service (pic.lync.com) is only for provisioning Lync Server and hybrid Lync Server and Lync Online deployments. Lync Online PIC provisioning is done in Lync Online Control Panel (LOCP).
Q: What must Lync end users do to connect to Skype contacts?
A: After a domain is activated and the features are enabled by an organization’s Lync administrator, Lync users can add Skype contacts to their contact lists within the Lync client.
Q: What must Skype end users do to connect to Lync contacts?
A: All Skype users wishing to connect to a Lync user must have a Microsoft Account associated with their Skype IDs and sign in using the Microsoft Account. This can be enabled within the Skype client.
Q: Is federation with Windows Live still available?
A: Beginning in October, 2012, Microsoft started helping Windows Live Messenger (WLM) users move to Skype, en route to eventually retiring WLM. Lync will continue to support federation with WLM as long as WLM is in market, but no additional Windows Live domain activations will be allowed. The movement of WLM users is enabled by the Skype 6.0 for Mac and Windows (released October 25, 2012) which allows signing in with a Microsoft Account (i.e., the same credentials as WLM). After simply signing in to Skype, WLM buddy lists automatically populate into Skype, and users can take advantage of Skype’s expanded communication capabilities such as calling landlines and mobiles, screen sharing, group video calling, and support for a wide variety of devices. Moreover, WLM users’ federated Lync contacts follow the transition into Skype with the rest of their buddy lists, and IM between Skype and Lync for these contacts will be available immediately. Lync customers do not need to do anything to enable this continuity of service.
Q: Is federation with Yahoo! or AOL still available?
A: Federation with Yahoo! and AOL are both on a path toward end-of-life for customers of Lync and Office Communications Server. Microsoft’s ability to provide each of these services has been contingent upon support from Yahoo! and AOL, and the underlying agreements of these are winding down. For both Yahoo! and AOL, service will continue through June 2014.
Yahoo: Service will continue through June 2014, and customers continue to need to be licensed with the Microsoft Lync Public IM Connectivity User Subscription License (“PIC USL”). As of September 1st, 2012, the PIC USL, is no longer available for purchase for new or renewing agreements. Customers with licenses purchased prior to this date will be able to continue to federate with Yahoo! until the earlier of the service shut down date or their license expiration. Customers who have PIC licenses on agreements that extend past June 30, 2014 will receive a credit in proportion to the amount of the payments covering the time period following June 30, 2014.
AOL: On June 30, 2014, Lync's IM connectivity ("PIC") service will no longer be available. In order to limit customer disruption when the service ends, we have discontinued the provisioning of additional customer domains. Until June 30, 2014, customers do not need to do anything to continue to support federated communications with AIM. Beyond this date (or for customers that would like to provision additional domains in the meantime), a substitute service is available directly from AOL. For more information on AOL's new service, see http://aimenterprise.aol.com/pic.php (opens new page on AOL.com).
Q: Can I trial Skype connectivity before purchasing Lync?
A: Skype connectivity is not offered on a trial basis. In place of a trial, Lync customers with eligible licenses are encouraged to simply sign up for the service to test.
Q: What information is required for provisioning?
A: To submit a provisioning request under a qualified license, you need the following:
Microsoft agreement number:
Microsoft Volume Licensing Support: Microsoft Volume Licensing Agreement number
Microsoft Partner Network: Headquarter partner ID
Service Provider Licensing Agreement: Initial enrollment number
High Volume Services: Product enrollment number
- Microsoft Volume Licensing Support: Microsoft Volume Licensing Agreement number
Fully qualified domain names (FQDNs) for the Access Edge service.
FQDN for at least one Access Edge service is required.
If your organization has more than one server running the Access Edge service, specify the FQDNs for each additional Access Edge service.Important: If you previously specified an FQDN for the Access Edge service and want to change it, provisioning for the change can take several days to complete and can result in a disruption in service. To prevent service disruption, we recommend that you maintain the previously specified FQDN of the Access Edge service.
- FQDN for at least one Access Edge service is required.
Session Initiation Protocol (SIP) domain(s). This is the domain suffix of the SIP URI that users currently use for instant messaging. If your organization has more than one SIP domain, specify the domain suffix for each domain used for instant messaging. For example, for firstname.lastname@example.org, specify contoso.com for the SIP domain; for email@example.com, specify example.fabrikam.com as the SIP domain.
Note: Specify only the domain suffix for the SIP domain. Do not specify any FQDNs, including the FQDN for the Access Edge service, for the SIP domain.
Contact information. Specify an e-mail address for the administrator of each SIP domain that you specify.
Q: How do I enable Lync-Skype Connectivity in a split-domain scenario?
A:If you have a Lync Online 2013 and Lync Server on-premise split-domain scenario (with users on both online and on-premise using the same SIP domain), enable Lync-Skype Connectivity by doing these two steps in the following order
Set up on-premise Lync-Skype Connectivity as explained in the PIC Provisioning Guide.
Wait until you see confirmation that your domain has been provisioned by Microsoft.
After you see the confirmation, use the Lync admin center to turn on “external communications”. For more information, see http://office.microsoft.com/en-us/support/configure-external-communications-HA102817865.aspx?CTT=5&origin=HA102817356
This order is important. You must set up the on-premise connectivity before you enable the communications in Lync Online. If the order is reversed, the information entered for on-premise in https://pic.lync.com will not go through. If you have already set up Lync Online for external communications with this domain, you must turn it off, wait for 24 hours, and start again, first by entering your on-premise information at https://pic.lync.com and then turning on external communications for Lync Online.
Q: Can I provision multiple Access Edge service FQDNs for Skype connectivity?
A: You can provision up to ten Access Edge service FQDNs with each provisioning request.
Q: Can I obtain the list of Microsoft Account e-mail addresses that you find for the organization requesting provisioning?
A: No. These addresses are considered personally identifiable information and are not shared.
Q: How do I add a Windows Live Messenger contact that has an ID containing a domain other than those supported by Windows Live?
A: If you are adding a Windows Live Messenger user with an account or ID with a non-Windows Live domain, enter the address in the following format: <user name>(<domain name>)@msn.com, where <domain name> is the domain name in the e-mail address of the user. For example, if you wanted to add firstname.lastname@example.org, you would use the following format: ted(contoso.com)@msn.com. For a list of domains that are administered by Windows Live, see the Supported Domains section in “Known Issues That Occur with Public Instant Messaging After You Install Live Communications Server Service Pack 1” at http://support.microsoft.com/?kbid=897567.
Q: How long does the provisioning process take?
A: Provisioning can take up to 30 days.
Q: How will I know when provisioning is complete?
A: Microsoft will send e-mail notification when provisioning is complete.
Q: How can I update the configuration or contact details that I submit?
A: You can update your information at the same web site that you used to request provisioning, after provisioning is complete. Enter your agreement number, and then click Update service.