Configure integration between on-premises Skype for Business Server and Exchange Online - this is for OWA
Topic Last Modified: 2015-03-23
Customers who are using on-premises Skype for Business Server 2015 deployments can configure interoperability with Microsoft Outlook Web App in Microsoft Exchange Online in a hybrid deployment mode. Interoperability features include single sign on and instant messaging (IM) and presence integration with the Outlook Web App interface. To enable this integration, you must configure the Edge Server in your on-premises Skype for Business Server deployment by completing the following tasks:
Configure a shared SIP address space
Configure a hosting provider on the Edge Server
Verify replication of the updated Central Management store
To integrate on-premises Skype for Business Server 2015 with Exchange Online, you must configure a shared SIP address space. The same SIP domain address space is supported by both Skype for Business Server and the Exchange Online service.
Using the Skype for Business Server Management Shell, configure the Edge Server for federation by running the Set-CSAccessEdgeConfiguration cmdlet, using the parameters displayed in the following example:
Set-CsAccessEdgeConfiguration -AllowFederatedUsers $True
AllowFederatedUsers parameter specifies whether internal users are allowed to communicate with users from federated domains. This property also determines whether internal users can communicate with users in a shared SIP address space scenario with Skype for Business Server and Exchange Online.
For details about using the Skype for Business Server Management Shell, see Skype for Business Server 2015 Management Shell.
Using the Skype for Business Server Management Shell, configure a hosting provider on the Edge Server by running the New-CsHostingProvider cmdlet, using the parameters in the following example:
New-CsHostingProvider -Identity "Exchange Online" -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn "exap.um.outlook.com" -IsLocal $False -VerificationLevel UseSourceVerification
|If you are using Office 365 operated by 21Vianet in China, replace the value for the ProxyFqdn parameter in this example ("exap.um.outlook.com") with the FQDN for the service operated by 21Vianet: "exap.um.partner.outlook.cn".|
Identity specifies a unique string value identifier for the hosting provider that you are creating (for example, "Exchange Online"). Values that contain spaces must be in double quotes.
Enabled indicates whether the network connection between your domain and the hosting provider is enabled. This must be set to True.
EnabledSharedAddressSpace indicates whether the hosting provider will be used in a shared SIP address space scenario. This must be set to True.
HostsOCSUsers indicates whether the hosting provider is used to host Office Communications Server or Skype for Business Server. This must be set to False.
ProxyFQDN specifies the fully qualified domain name (FQDN) for the proxy server used by the hosting provider. For Exchange Online, the FQDN is exap.um.outlook.com.
IsLocal indicates whether the proxy server used by the hosting provider is contained within your Skype for Business Server topology. This must be set to False.
VerificationLevel Indicates the verification level allowed for messages that are sent to and from the hosted provider. Specify UseSourceVerification, which relies on the verification level included in messages sent from the hosting provider. If this level is not specified, the message will be rejected as being unverifiable.
The changes you made by using the cmdlets in the preceding sections are automatically applied to the Edge Server, and generally take less than a minute to replicate. You can validate replication status, and then confirm that the changes were applied to your Edge Server by using the following cmdlets.
To verify replication updates, on a server internal in your Skype for Business Server deployment, run the following cmdlet:
To confirm that the changes were applied, on the Edge Server, run the following cmdlet: