More about Open Federation at the end of this post.īut after configuring Skype for Business Hybrid, external contacts in my Skype for Business desktop client appears with Updating … and finally ends in P resence unknown status. If you do not select this option, federated user access is enabled only for users in the domains that you include in the allowed domains list. In my production environment I have configured O pen Federation which allows to communicate with each external SIP domain, so called SIP Federated Domains.
Skype for Business Hybrid configuration will break Open Federation I suppose this was due to some Office 365 synchronisation delays. So no clue why the Hybrid Setup wizard now runs without issues.
#Skype for business with office 365 how to#
You will see later how to determine this tenant specific URLs. Autodiscover/AutodiscoverService.svc/rootĪnd the Hybrid Setup wizard can determine this specific URL at logon to the Office 365 tenant. The reason for this different Autodiscover URL is tenant specific!
You will see below that also the Skype for Business Online admin center is running under this FQDN. Trying to run the Hybrid Setup wizard the next day will run fine without the Federation with Office 365 is not configured error message.įurther I discovered that the Hybrid Setup wizard in my version is setting a different new AutodiscoveryUrl and FQDN for the Hosting Provider as in the actual documentation from Microsoft under So finally I configured Skype for Business hybrid with the PowerShell Cmdlets described in Part 5 …
The Hybrid Setup wizard is setting IsLocal to False and deletes the AutodiscoverUrl. Under the following Federation requirements, they say that the Blocked domains and Allowed domains list in the on-premise deployment must exactly match with the online tenant.Īfter finishing the Hybrid configuration with PowerShell as described in Part 5 …, you will get the following entries for the Hosting Provider.Īfter running the Hybrid Setup wizard again, I get the same error with Federation with Office 365 was not configured by the wizard.įurther after checking it again with the Skype for Business Server Management Shell and the Get-CSHostingProvider Cmdlet, I will get the following output. In my case I didn’t configured any allowed or blocked domains and there were no entries in my environment, on-premise and online. You will find hints in the web, that the reason for this error will result from entries in the CSAllowedDomains or CSBlockedDomains list. Hmmm, the Federation with Office 365 was not configured by the wizard. The Hybrid Setup wizard tells me that Federation with Office 365 and Shared SIP address space is not configured.įurther he kindly tells us, that if we select Next, he will configure our Skype for Business Server and Office 365 tenant with these required setting, so click on Next.
#Skype for business with office 365 license#
0 kommentar(er)
