Office 365 Workflow (Business to Business via Expressway)
The IM and Presence Service supports interdomain SIP federation with Office 365 via Cisco Expressway session classification in a business to business configuration. With this integration, Office 365 hosts the Skype for Business deployment.
Note |
For interdomain federation with Skype for Business without Office 365, see Skype for Business Workflow. |
IM and Presence Service Configuration
-
Start Federation services. See Turn on Federation Services.
-
Configure a public DNS SRV record for the IM and Presence domain. The SRV should resolve to the Expressway-E IP address. See Add DNS SRV Record for the IM and Presence Service.
-
In the IM and Presence Service, add the Office 365 domain entry. See Add Office 365 Domain to IM and Presence Service.
-
In the IM and Presence Service, configure a TLS static route to Expressway-C. See Configure Static Route to Office 365.
-
In the IM and Presence Service, assign Expressway-C as a TLS peer. See Add Expressway as TLS Peer.
-
In the IM and Presence Service, add the Expressway-E server to the inbound access control list. See Add Expressway to Access Control List.
-
Restart the Cisco XCP Router on all IM and Presence Service nodes. See Restart Cisco XCP Router.
-
Exchange certificates between the servers in your deployment. For the IM and Presence Service, you will need to upload the Expressway-C certificate chain to the cup-trust store. See Exchange Certificates.
Cisco Expressway Configuration
After interdomain federation is configured on the IM and Presence Service, set up Cisco Expressway for interdomain federation with Office 365. For Expressway configuration details, see Chat and Presence XMPP Federation and Microsoft SIP Federation using IM and Presence or Expressway at: