Home
%3CLINGO-SUB%20id%3D%22lingo-sub-763614%22%20slang%3D%22en-US%22%3ESkype%20for%20Business%20Server%20Public%20IM%20Federation%20is%20changing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763614%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20currently%20have%20connected%20you%20Skype%20for%20Business%20Server%20to%20consumer%20IM%20federation%2C%20you%20will%20want%20to%20read%20this%20and%20insure%20you%20are%20configured%20for%20the%20future.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFederation%20between%20Skype%20for%20Business%20on-premise%20deployments%20and%20Skype%20(Consumer)%20will%20change%20on%208%2F15%2F2019%20to%20use%20federated%20partner%20discovery%2C%20which%20is%20the%20same%20mechanism%20required%20for%20federation%20with%20Skype%20for%20Business%20Online.%20The%20pic.lync.com%20website%20that%20was%20formerly%20used%20to%20manually%20provision%20on-premise%20deployments%20for%20public%20IM%20connectivity%20will%20be%20shut%20down%20due%20to%20end%20of%20life.%20Communication%20between%20any%20on-premise%20Skype%20for%20Business%20deployment%20and%20Skype%20users%20via%20the%20existing%20Public%20IM%20infrastructure%20now%20requires%20the%20on-premise%20edge%20server%20configuration%20to%20be%20compatible%20with%20Skype%20for%20Business%20Online.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EIf%20the%20customer%E2%80%99s%20SfB%20deployment%20is%20currently%20using%20public%20IM%20connectivity%20but%20is%20not%20able%20to%20federate%20with%20Skype%20for%20Business%20Online%20due%20to%20their%20edge%20proxy%20FQDN%20configuration%20and%2For%20their%20certificate%20is%20incompatible%20with%20federated%20partner%20discovery%2C%20they%20will%20need%20to%20update%20their%20deployment%20configuration%20by%208%2F15%2F2019.%20Failure%20to%20do%20so%20could%20lead%20to%20an%20interruption%20to%20public%20IM%20connectivity.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EPlease%20note%20this%20change%20may%20require%20the%20purchase%20of%20a%20new%20certificate.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EPlease%20visit%20our%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fskypeforbusiness%252Fdeploy%252Fdeploy-skype-connectivity%2523the-skype-for-business-server-public-im-connectivity-provisioning-site-is-no-longer-available%26amp%3Bdata%3D02%257C01%257Cpaulcan%2540microsoft.com%257C5a09f79ac276426b9fb208d70b962fd1%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636990611987498415%26amp%3Bsdata%3D%252B9zDWS%252FUP0t0ISsuAb2Kt5H%252BeTQo6lNgQuagK6ZZ0WU%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edocumentation%3C%2FA%3Eon%20this%20issue%20to%20learn%20more.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-763614%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-764168%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20for%20Business%20Server%20Public%20IM%20Federation%20is%20changing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-764168%22%20slang%3D%22en-US%22%3EThank%20you%20for%20removing%20the%20manually%20provisioning%2C%20for%20some%20customers%20it%20was%20hard%20because%20they%20did%20not%20now%20what%20the%20agreement%20number%20is%20etc.%3C%2FLINGO-BODY%3E
Microsoft

If you currently have connected you Skype for Business Server to consumer IM federation, you will want to read this and insure you are configured for the future.

 

Federation between Skype for Business on-premise deployments and Skype (Consumer) will change on 8/15/2019 to use federated partner discovery, which is the same mechanism required for federation with Skype for Business Online. The pic.lync.com website that was formerly used to manually provision on-premise deployments for public IM connectivity will be shut down due to end of life. Communication between any on-premise Skype for Business deployment and Skype users via the existing Public IM infrastructure now requires the on-premise edge server configuration to be compatible with Skype for Business Online.


If the customer’s SfB deployment is currently using public IM connectivity but is not able to federate with Skype for Business Online due to their edge proxy FQDN configuration and/or their certificate is incompatible with federated partner discovery, they will need to update their deployment configuration by 8/15/2019. Failure to do so could lead to an interruption to public IM connectivity.


Please note this change may require the purchase of a new certificate.


Please visit our documentation on this issue to learn more.

 

1 Comment
Occasional Contributor
Thank you for removing the manually provisioning, for some customers it was hard because they did not now what the agreement number is etc.