dns requirements for skype for business on prem

How was this possible given that there were no record with the host of ? Once again, surprise! While the test failed, it showed that had resolved to two IP-addresses that did not respond to further requests. I still went ahead and ran the Skype for Business Autodiscover Web Service test. I started looking into the domain itself and sure enough no services were enabled in O365 and no SfB related DNS records were present. Using PowerShell I verified that there were indeed no users tied to the domain. The domain simply existed in Office 365 because of it being a verified domain used for Azure only. Even more surprising, the domain mentioned in the error had never been used in this context. Users can be individually upgraded to TeamsOnly using either Move-CsUser (if the user has an on-premises Skype for Business account) or Grant-CsTeamsUpgradePolicy (if the user is homed in Skype for Business online).Īs the on-premise Skype for Business environment was decommissioned years ago knew that the statement simply wasn’t true. This organization cannot be upgraded to TeamsOnly at the tenant level because there is an on-premise deployment of Skype for Business detected in 1 or more of it sip domains,. Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Global

Dns requirements for skype for business on prem