Update April 28

Here is the email sent internally to those of us registered as the Microsoft contact for a customer federation.

CUTOVER

Lync Federation changes will take effect on Saturday May 9th and the new IP’s and ports will need to be implemented by your customers and partners on their firewall to continue your Lync connections with Microsoft. 

 Action required By TAMs, TSPs and Lync Federation Sponsors:

  1. Notify your contact with the external company that the IP address for the sipfed.microsoft.com SIP domain is changing to 131.107.255.86 on Friday, May 8, 2014.

  2. Set expectations that federation with Microsoft may not work going forward if they do not add the below mentioned IP addresses and ports to their firewall rules.

Action Required by Customers and Partners:

Update Firewall Settings – Many of your customers and partners will need to add the following IP’s and ports to their firewall exceptions to ensure Lync Federation with Microsoft will work.  Firewalls must be configured to allow-all Bi-directional traffic to Microsoft's Lync deployment.

The list of required firewall rules for federation with Microsoft are below:

Description

IP

TCP Ports

UDP Ports

Status

Current SipFed Address

65.55.30.130

5061

N/A

Existing

Future SipFed Address

131.107.255.86

5061

N/A

Required to Add

Notify your contact with the external company that the IP address for the sipfed.microsoft.com SIP domain is changing to 131.107.255.86 on Friday, May 8, 2014.  Depending on how their infrastructure is configured, they may need to make one of the following changes:

  1. Companies configured as direct federations using IP address (not sipfed.microsoft.com) will need to update their configuration to the new IP address
  2. Companies using their firewall(s) to filter by IP address will need to update their Access Control List (ACL) to the new IP address

 Why we are making these changes:

By adding these additional IP, we will be adding resiliency to allow Microsoft to support Lync federation without a large impact when subsequent changes are made in the future. The majority of federated companies will have additional rules in place; please do not have our federated companies remove anything as this is an “add-to” action

 --------------------------------------------------------------------------------------------------------------------------------------------

Original post

Most customers should get this communication due to the data we have for federations, however there is always a chance someone will be missed or the contact has changed.

Microsoft is scheduling a change May 9 at 8pm for the SIPFED.MICROSOFT.COM IP address, the new IP address will be 131.107.255.86

While on the topic of change, here are two helpful resources finding customer federations

http://lyncdirectory.com/

http://windowspbx.blogspot.com/2011/09/usa-microsoft-lync-federation-directory_02.html