Deploy Expressway Calendar Connector for a Hybrid Exchange Environment
This chapter describes setting up the Calendar Connector on Expressway to handle both Office 365 and Microsoft Exchange in a Hybrid Exchange deployment. With the release of the cloud-based service for Office 365 users, you can now choose whether to deploy only the Expressway-based Calendar Connector, as described in this section, or a combination of the Calendar Connector and the cloud-based service.
The cloud-based service can scale beyond the 1000 user limit for Office 365 users and is simpler to deploy and maintain. It does not service Microsoft Exchange users. If you deploy it alongside the Calendar Connector, your Office 365 users automatically move to the cloud-based service (unless they are in resource groups).
Before you decide which service to deploy for your Office 365 users, read the Prepare Your Environment chapter of the Office 365 with Cloud-Based Hybrid Calendar Service part of this guide, to understand the requirements for that option.
Before you begin
If your deployment meets all of the following criteria, you can use a simplified Exchange configuration, by following all of the steps in Deploy Expressway Calendar Connector for Microsoft Exchange, instead of this procedure.
Your Expressway-C connects to both the on-premises Exchange environment and the Office 365 cloud through the same proxy method (either neither connects through a proxy, or both do).
Your deployment met all of the conditions for using a simplified configuration with a single impersonation account (in Set Up an Impersonation Account for Office 365).
If your deployment does not meet these criteria, follow all of the steps in this procedure to set up two separate Exchange configurations on the Expressway-C -- one for the on-premises mailboxes, and one for the Office 365 mailboxes.
Deploy Expressway Calendar Connector for Microsoft Exchange by adding an Exchange configuration to Expressway.
Enable Hybrid Calendar Service for users who have mailboxes in on-premises Exchange.
Start Calendar Connector and ensure that the activated users are subscribed.
As a test, in a meeting invitation in Outlook, OWA, or your calendar client, add a space scheduling keyword (such as @webex:space or @meet) to the Location field; verify that this step creates a Cisco Webex Teams space for an activated user.
Stop the Calendar Connector. Do not proceed until you see that it fully stopped.
Deploy Expressway Calendar Connector with Office 365 by adding a new Exchange configuration to Expressway, for Office 365.
For the authentication type, you should check both NTLM and Basic authentication types. If one method fails, then the other method is used.
Enable Hybrid Calendar Service for users who have mailboxes in Office 365.
Start Calendar Connector and ensure that activated users in both on-premises and Office 365 are subscribed.
As a test, in an Outlook invitation, add a space scheduling keyword to the Location field; verify that this step creates a Webex Teams space for both on-premises Exchange and Office 365 users.
Users with either on-premises Exchange or Office 365 mailboxes can now schedule meetings using the scheduling keywords.