What Will Happen On July 31, 2021, and the Day After? We’ll also show you the benefits of moving your Skype for Business Server users to Teams sooner. And if you have Skype for Business Server-which will not retire on July 31, 2021-we will discuss the implication of the Skype for Business Online retirement on your hybrid environment.

We can help you plan your last-minute move. However, if you haven’t moved your users yet, it’s not the end of the world. In our last blog about Skype end of life, we talked extensively about the need for moving users to Teams sooner rather than later. I haven't seen any issue arise from this yet and I don't want to fix something that isn't broke unless I have a good reason.Skype for Business Online goes end of life on July 31, 2021. Something like that I would like to know what the potential issues of ignoring these warnings may be. I wouldīe willing to at least consider either getting hairpinning from Exchange to that public IP set up or to create hosts file entries on my Exchange servers to point the external web services requests to the internal IP's of my FE servers, but before I even consider My question is, what exactly is Exchange trying to do here that it needs to connect to SKype web services? I can see why Skype connects to Exchange Web Services, but I'm not sure why Exchange would connect to Skype in this manner (over web services). So since Exchange is also in that same data center, when it queries DNS for the webexternal address and sees the public IP address of the same data center it lives on, it tries to connect to that public IP and fails because Public) to point all traffic to the public IP addresses of our edge servers/reverse proxy at our data center (I have everyone going external because we do not use any kind of MPLS, we use all IPSec VPN tunnels between about a dozen sites and pointing externalĬuts down on the video latency). Right now our firewall isn't really doing any kind of hairpinning and all of our Skype services except the actual internal pool fqdn are set in DNS (both private and Now I will say - I knowĮXACTLY what is causing this. In my Exchange server, I see the following error periodically:įYI is the fqdn of my external Skype web services. I have my Skype for Business installation integrated with my Exchange environment for archiving and server side conversation history.