Deployment guide for Hybrid Calendar

In this article

Feedback?

Architecture: Office 365 with cloud-based Hybrid Calendar

Cloud-based Hybrid Calendar with Office 365: Scheduling flow

A user creates a meeting in the Office 365 calendar, putting a scheduling keyword or video address in the Location field.
Exchange Online sends a notification to the Hybrid Calendar.
The Hybrid Calendar requests and receives the encryption key, and then uses it to encrypt the meeting information.
The Hybrid Calendar validates meeting creation and recipients, and then creates a Webex team space, if applicable.
The Hybrid Calendar calls the API service and, if applicable, maps the meeting to the space.
The Hybrid Calendar retrieves the meeting join information, including the Webex Personal Room if applicable.
The Hybrid Calendar updates the meeting invite with the meeting join information and, if applicable, the space ID.
The invitees and the organizer get the updated meeting invitation.

For more information on how the cloud-based Hybrid Calendar integrates with Office 365, see the Hybrid Calendar Service with Microsoft 365 integration reference.

Prepare your environment

How the Hybrid Calendar accesses user calendars

When you first set up the Hybrid Calendar, you need to grant it permission to access Office 365 on behalf of your users. Use an account that can authorize multi-tenant apps (like Global Administrator or Privileged Role Administrator) to grant the permission.

The Hybrid Calendar needs these permissions to do the following actions:

When the administrator grants permission for the Hybrid Calendar on behalf of the Office 365 tenant, Webex is notified. This permission enables the Hybrid Calendar to get access tokens from Azure Active Directory (Azure AD) using OAuth 2.0, to authenticate and access user calendars. The Webex cloud does not see or store the administrator login credentials at any point in the process. For more information, see https://docs.microsoft.com/en-us/graph/auth-v2-service.

The Hybrid Calendar uses the Microsoft Graph API to subscribe to changes in users’ calendars, receive notifications for changes made in subscribed users’ calendars, and update meeting invitations with scheduling information when the meeting location field contains keywords such as @webex or @meet, or the meeting body contains a supported video address. The Hybrid Calendar accesses only the calendars of the users that you enable for Hybrid Calendar in the Control Hub.

Webex App follows industry-standard best practices to securely store the Private Key for the application. All meeting details that the service stores are encrypted using Webex App end-to-end encryption. This ensures that only those who are invited to the meeting can see the details. For more information on Webex App encryption, see the Cisco Webex Security and Privacy white paper.

If needed, your Exchange administrator can revoke the Hybrid Calendar access to your Office 365 tenant user calendars from Enterprise Applications in the Azure AD management portal.

Deploying alongside an existing Expressway-based Calendar Connector

If you have already deployed the Expressway-based Calendar Connector to serve Microsoft Exchange users, Office 365 users or a hybrid of Microsoft Exchange and Office 365 users, you can add the cloud-based Hybrid Calendar with Office 365, running both at the same time. Once you enable the cloud-based service, any Office 365 users who are not a part of a resource group automatically migrate from your Calendar Connector to the new cloud-based service within 24 hours. (The Hybrid Calendar checks for Office 365 users to migrate from Calendar Connectors once a day.)

The Expressway-based Calendar Connector that you deploy with the Hybrid Calendar for Microsoft Exchange or Office 365 has a capacity limit of 1,000 Office 365 users, and requires on-premises equipment. The cloud-based service allows you to scale past the capacity limit.

Both options (Calendar Connector and cloud-based service) can be enabled at the same time.
All Office 365 users NOT in a resource group migrate to the cloud-based service automatically.
To enable some users on the cloud service first for testing, put other users who must stay homed on the on-premises Connector into a resource group before turning on the cloud-based service.

Change processing timeframes

When you activate the Hybrid Calendar for Office 365 and enable users or move mailboxes, the service processes these changes periodically.

Table 1. Processing frequency for activations and changes
Administrator action	Processing behavior	Expected completion timeframe
Activation
Enable the Hybrid Calendar for the organization.	Once the setup is successful, the Hybrid Calendar tries to subscribe to calendars of users that are listed in "Not activated" or "Error" states.	Depending on volume, immediate to minutes.
Enable individual users (toggle on Calendar or bulk enable).	Hybrid Calendar attempts to subscribe to the user's calendar. If the activation fails, the user is in "Error" state and the Hybrid Calendar retries in 60 minutes. If the activation fails multiple times, the Hybrid Calendar retries in 24 hours.	If everything goes well, immediately. Otherwise, up to 24 hours. If it takes longer than this, check the user account.
Mailbox migration
Move user mailbox from on-premises Exchange to Office 365.	Once Office 365 has completed the mailbox migration, it takes up to 40 minutes for the Hybrid Calendar to put the user in "Error" state. As above, the Hybrid Calendar attempts to reprocess users in "Error" state every 60 minutes.	If everything goes well, up to 100 minutes. Otherwise, up to 24 hours. If it takes longer than this, check the user account.
Move user mailbox from Office 365 to on-premises Exchange.	Once a day, the Hybrid Calendar runs a watch refresh that detects missing mailboxes and puts them in "Error" state. Another cloud service then reassigns the user to an Expressway-based Calendar Connector.	Up to 24 hours to detect the change, plus a few minutes of reassignment time.

Requirements for Hybrid Calendar with Microsoft Office 365

A Microsoft 365 tenant with Exchange online accounts for users in the organization. During setup, you must sign in with an account that can authorize multi-tenant apps (like Global Administrator or Privileged Role Administrator) to grant the appropriate permission.

Note the following considerations for your Microsoft 365 tenant:
- The commercial version of Webex only supports the Worldwide instance of Office 365. (Webex doesn't support USGovDoD, USGovGCCHigh, China, and Germany instances.)
- Webex for Government supports the Worldwide instance of Office 365 through a tenant in GCC and the USGovGCCHigh instance. (Webex for Government doesn't support the USGovDoD, China, and Germany instances.)
- Office 365 includes Multi-Geo Capabilities that enable your tenants to store data in a chosen geography. But, Webex stores data according to its own data residency specifications based on the country designated for the customer organization. For more information, see https://www.cisco.com/go/webex-teams-locality.
For @webex scheduling, any supported Webex Meetings release.

You must enable the Personal Room feature for the Webex site and for the individual users.
A Webex organization with a paid subscription.

We don’t currently support deploying both Google Calendar and Office 365 with the cloud-based Hybrid Calendar in the same Webex organization.
Users must have activated Webex accounts, with email addresses that are exact matches in Webex Meetings, Webex App, and Exchange online (the Primary Email Address).

Each Webex App user can only have one email address associated with only one Hybrid Calendar integration. In other words, the Hybrid Calendar will only process meetings from a single address for creating spaces, decorating meetings, showing the meetings list and join button, and sending the Join button to video devices.

Deploy cloud-based Hybrid Calendar with Office 365

Hybrid Calendar with Office 365 deployment task flow

To deploy Hybrid Calendar with your Office 365 organization, perform the following tasks.

Before you begin

Prepare your environment

1	Prepare your Webex Meetings site If you have a Webex Meetings site, make sure it's ready for integration with @webex.
2	Enable and configure Hybrid Calendar with Microsoft 365 Register your Office 365 environment to the Webex cloud with an initial tenant, authorize write permission, test the connection, and set the default Webex site.
3	(Optional) Add an additional tenant to Hybrid Calendar with Office 365 Add a tenant to the Webex cloud, authorize write permission, test the connection, and set the default Webex site.
4	(Optional) Modify a tenant of Hybrid Calendar with Office 365 Modify a tenant's configuration to the Webex cloud, to authorize read/write permissions, deactivate the Hybrid Calendar, and identify the Workspace organizer.
5	(Optional) Choose how Hybrid Calendar localizes meeting join details To override how the Hybrid Calendar localizes meeting join details for your entire organization, set the Default Language setting in https://admin.webex.com.
6	(Optional) Configure @webex and @meet keywords To change the action that the Hybrid Calendar takes when users enter @webex or @meet, set the Keywords settings in https://admin.webex.com.
7	(Optional) Customize email templates Choose what the Hybrid Calendar adds to meeting invitations, including audio or video join details and a localized header and footer in any language that the service supports.
8	Enable Hybrid Calendar with Office 365 for users
9	(Optional) Add Hybrid Calendar to workspaces with Board, Desk, and Room series If you want One Button to Push (OBTP) functionality to be provided to cloud-registered room and desk devices and Webex Boards, toggle on the calendar service for the devices, and configure the room mailbox email address.
10	(Optional) Associate Webex personal rooms with Webex App For OBTP on Webex room and desk devices and Webex Boards, make sure that meeting schedulers have their Personal Rooms associated with their Webex App accounts.
11	Test the Office 365 and Hybrid Calendar integration
12	(Optional) Move a user from an Expressway-based connector

Prepare your Webex Meetings site

In order to provide full @webex functionality, the Hybrid Calendar needs access to user scheduling information from your Webex Meetings site.

If your Webex site is managed in Control Hub, you do not need do anything to make the information available. Otherwise, the preferred method for making this information available is to have an administrator link the site to Webex Teams.

If you have not yet linked the sites, your users can associate their Cisco Webex Personal Rooms with Cisco Webex Teams themselves in the app.

Enable and configure Hybrid Calendar with Microsoft 365

Follow these steps to register your Microsoft 365 environment to the Webex cloud, add the initital tenant, test the connection, and set the default Webex site. The setup wizard in https://admin.webex.com guides you through the process.

Before you begin

Use an account that can authorize multi-tenant apps (like Global Administrator or Privileged Role Administrator) to grant permission for the setup process.

1	Sign in to the customer view of https://admin.webex.com.
2	In the left-hand navigation pane, under Services click Hybrid.
3	On the hybrid calendar card with the Microsoft 365 logo, click Edit settings.
4	On the Hybrid Calendar (Microsoft 365) page, click Add tenant.
5	Follow the steps to authorize Webex cloud access on the appropriate Microsoft 365 administrator account. Follow the steps to choose your Microsoft 365 instance and authorize Webex cloud access on the appropriate Microsoft 365 administrator account. The browser should redirect you to https://admin.webex.com when you've finished the authorization steps. If it does not, try these steps again.
6	Follow the step to accept the read permissions requested for your tenant.
7	Chose from the following associated with testing the connection with Microsoft 365 and defining a workspace. Type an email address to test the connection with Microsoft 365 for the new tenant. Check the box to indicate that your organization needs to be able to schedule meetings from Workspaces and enter the email address of the organizer for meetings scheduled from Workspaces.
8	Click Test. When the connection is successful the browser redirects you to the Services page on https://admin.webex.com when you've finished the test step. When a connection is not created, verify that the user name you are using has a license on the Microsoft account and try these steps again
9	Choose or type the Webex Meetings site to use for @webex scheduling. Save your changes.
10	If there are users with error status, click User Status Report to view the error details.

Add an additional tenant to Hybrid Calendar with Office 365

Use this procedure to add a new tenant to an existing Hybrid Calendar with Microsfot 365.

Before you begin

You should have added an organization with Enable and configure Hybrid Calendar with Microsoft 365.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid. You can use the search function to narrow down the list of users.
3	On the hybrid calendar card with the Microsoft 365 logo, click Edit settings.
4	On the Hybrid Calendar (Microsoft 365) page, click Add tenant.
5	Follow the steps to authorize Webex cloud access on an appropriate Micrsoft 365 administrator account. Follow the steps to choose your Microsoft 365 instance and authorize Webex cloud access on an appropriate Microsoft 365 administrator account.
6	Follow the step to accept the read permissions requested for your tenant.
7	Chose from the following associated with testing the connection with Microsoft 365 and defining a workspace. Type an email address to test the connection with Microsoft 365 for the new tenant. Check the box to indicate that your organization needs to be able to schedule meetings from Workspaces and enter the email address of the organizer for meetings scheduled from Workspaces.
8	Click Test.

When the connection is successful the browser redirects you to the Services page on https://admin.webex.com when you've finished the test step. When a connection is not created, verify that the user name you are using has a license on the Microsoft account and try these steps again.

Related Information

Disable User Email Notifications

Steps to update users in bulk

Steps to update users in a directory synchronized organization

Modify a tenant of Hybrid Calendar with Office 365

Use this procedure to modify a tenant for Webex App users for Hybrid Calendar with Microsoft 365.

Before you begin

Add a tenant to Hybrid Calendar.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid .
3	On the hybrid calendar card with the Microsoft 365 logo, click Edit settings.
4	On the Hybrid Calendar (Microsoft 365) page, on the default tenant domain of the tenant to configure. The Microsoft 365 integration panel displays in the right-hand panel.
5	To authorize the tenant, click Authorize. If you removed Control Hub authorization from your Microsoft 365 tenant, click Authorize to reset the read and write permissions. Also, if you've just switched from a single tenant to multiple tenants, the previous tenant appears as an "Unknown" domain. Reauthorize this tenant to reinitialize it so that it can have full functionality.
6	To deactivate Hybrid Calendar (Microsoft 365) from this tenant, click Deactivate.
7	To establish an organizer for meetings scheduled fromWorkspaces, enter the Microsoft 365 account email address.

Choose how Hybrid Calendar localizes meeting join details

In Control Hub, the Default Language setting controls the language of the join details that the Hybrid Calendar adds to invitations. If you leave the setting at its default, the service uses the language in the "language":{"locale"} setting from the scheduler's mailbox settings.

To override choosing languages based on meeting schedulers' settings, choose a specific language to use for join details for all meetings across your organization.

1	Sign in to the customer view of https://admin.webex.com.
2	In the left-hand navigation pane, under Services click Hybrid.
3	On the hybrid calendar card with the Office 365 logo, click Edit settings. The Hybrid Calendar (Microsoft 365) displays a list of tenants included in this organization.
4	Select the tenant to configure.
5	Click the Settings tab.
6	In the Meeting Invitations section, choose a language from the Default Language drop-down list, and click Save. After you save the change, the Hybrid Calendar uses the language you choose each time it adds join to details a meeting. It doesn’t change the language for existing join details.

Configure @webex and @meet keywords

By default, when users add @webex to a meeting location, the calendar service updates the meeting with their Webex Personal Room details. When users add @meet, by default the service updates the meeting with Webex App space details. As an administrator, you can change these default actions for either keyword.

Regardless of how you set these actions, power users can add the modifier :space, :myroom or :onetime to specify the action for either keyword. For example, adding @webex:space causes the service to update the meeting with Webex App space details. As well, @webex:onetime creates a one-time Webex meeting.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for your calendar environment, click Edit settings. If you have the Hybrid Calendar set up for multiple calendar environments, you can access the keywords settings from multiple pages in Control Hub, but the values that you set apply to all environments. The Hybrid Calendar (Microsoft 365) displays a list of tenants included in this organization.
4	Select the tenant to configure.
5	Click the Settings tab.
6	In the Keywords section, select the default action that you want for each keyword.
7	Click Save.

Customize email templates

Choose which meeting join details the calendar service includes in meeting invitations.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Meeting > Settings.
3	Locate the Meeting Join Customization section.
4	Choose whether to show Join by Phone details. When you include the dial-in details, you can also choose to add a link to global call-in numbers, a link to toll-free calling restrictions, or both.
5	Show or hide details on joining from an application or video conferencing device. When you include the video dialing details, you can also choose to include an IVR IP address, a Skype for Business join link, or both.
6	Click Add a Language and then select the language from the drop-down menu to create a custom header and footer for any of the languages that the Hybrid Calendar Service supports. When you've got the header and footer text that you want, click Save. The header and footer values have a maximum of 1024 characters each (including spaces).
7	Once you've added a custom header and footer for a language, you can choose that language as a default for any other language that doesn't have a custom header and footer defined. Your default language choice saves automatically.

Enable Hybrid Calendar with Office 365 for users

Use this procedure to enable individual Webex App users for Hybrid Calendar with Office 365.

See the links below for ways to enable services for your Webex users in bulk or in a directory synchronized organization.

Any of these methods requires that users have signed in to the Webex App app to be fully activated. To enable @webex for users who have never signed in to the app, add and verify the users' domain using the Manage your domains process. (You must own a domain for it to be verifiable. You do not need to claim the domain.)

Before you begin

Users must have licensed Exchange Online mailboxes.
Users must have activated Webex accounts, with email addresses that are exact matches in Webex Meetings, Webex App, and Exchange online (the Primary Email Address).

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Users and then choose a specific user from the list. You can use the search function to narrow down the list of users.
3	Click the row to open an overview of the user.
4	In the Hybrid Services area, click Calendar Service.
5	Toggle on Calendar, ensure that Microsoft Exchange/Office 365 is selected, and save your changes. After you activate the service, the user's calendar service status changes to Pending Activation and then to Activated. The length of time for this change depends on the number of users that you're enabling for the service. Users receive an email that indicates the feature is enabled. See the documentation below if you want to disable email notifications.

Related Information

Disable User Email Notifications

Steps to update users in bulk

Steps to update users in a directory synchronized organization

Add Hybrid Calendar to workspaces with Board, Desk, and Room series

Before you begin

This task assumes that you've already created places for the Board, Desk, and Room devices. If you need to create the workspace, see Add shared devices and services to a workspace.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Workspaces and select the workspace to modify.
3	Go to Scheduling and select Calendar so that users can use One Button to Push (OBTP) on their devices.
4	Select the calendar provider.
5	Enter the email address of the room mailbox. (For help locating this email address, see " Create and manage room mailboxes" on the Microsoft Docs website.) This is the email address that will be used to schedule meetings.
6	Click Save.

Associate Webex personal rooms with Webex App

To provide the join button to devices when scheduling Webex Personal Room meetings, users must have their Personal Room associated with their Webex App account. This can happen in one of the following ways:

The users on your Webex site have been Webex App linked. (For site linking steps, see Link Webex sites to Control Hub.)
Users change their own preferred Webex site from the Webex App settings or preferences, see Change your default meeting site
For a comprehensive approach, use the bulk CSV import process from Control Hub to set users’ preferredWebExSite in the steps that follow.

1	Sign in to the customer view in https://admin.webex.com.
2	In the left-hand navigation pane, under Management click Users.
3	Click Manage Users.
4	See this article for the detailed CSV import/export procedure.
5	Use a CSV editor to change the `preferredWebExSite` attribute for all or some users.
6	Import the CSV file.

Test the Office 365 and Hybrid Calendar integration

Use these steps to set up a test meeting and verify the Office 365 integration. Direct users to the documentation below for how to schedule meetings.

1	Sign in to Outlook, Outlook Web Access, or https://mail.office365.com with one of the test Office 365 user accounts enabled for Hybrid Calendar.
2	Test the team space scheduling keyword (such as @webex:space or @meet): Create a new meeting, and then add the keyword to the Location field. To create a new Webex team space for the meeting, invite at least two other people. To test One Button to Push on a video device, go to the Scheduling Assistant and click Add room, and choose the device you want to add. Fill out other meeting information, as needed, and then click Save. Open https://teams.webex.com, and sign in with the test user account. Verify whether a new space was created (if you added two or more other invitees) and contains the calendar invite card. If you only invited one other invitee, the calendar invite card will appear in the conversation space between your test account and the invitee. Verify that the meeting invitation is updated with the details to join the meeting with Webex App. If you're testing One Button to Push on a video device, when the meeting is scheduled to begin, verify that the Join button appears on the device.
3	To test out-of-office status, turn on automatic replies in Office 365. Within 20 minutes, you should see the test account's profile picture display an out-of-office overlay in Webex Teams, like this: The display picture update is triggered when others see your presence in a space. If the test user does not interact with other active users, you may need to use another account to verify the update.
4	Test the Personal Room scheduling keyword (such as @webex): Create a new meeting, and then add the keyword to the Location field. To test One Button to Push on a video device, go to the Scheduling Assistant and click Add room, and choose the device you want to add. Fill out other meeting information, as needed, and then click Save. Verify that the meeting invitation is updated with the details to join the meeting . If you're testing One Button to Push on a video device, when the meeting is scheduled to begin, verify that the Join button appears on the device.

Related Information

Schedule a Cisco Webex Meeting from Your Calendar

Show When You're Out of Office

Move a user from an Expressway-based connector

Hybrid Calendar automatically moves any Office 365 users who are not part of a resource group from your Expressway-based calendar connector to the cloud-based service. This process can take up to an hour, because the service checks for users to move once an hour. (If you're also moving the user's mailbox from Microsoft Exchange to Office 365, it can take up to 40 minutes longer.) If you want to have users activated faster, use the following procedure to toggle Hybrid Calendar for users, thereby forcing the activation within minutes.

You must remove Office 365 users from a resource group in order for them to move off of the Calendar Connector. This procedure also covers that process.

1	If applicable, move the user mailbox from Microsoft Exchange to Office 365.
2	Sign in to the customer view of https://admin.webex.com/login.
3	In the left-hand navigation pane, under Management click Users.
4	To modify an individual user, do the following sub-steps: Search for the user in the list and click the row for that user. In the panel that opens on the right, click Calendar Service. From the Resource Group drop-down list, click None. Next to Calendar, toggle the service off. Wait a minute, and then toggle the service back on. The user should be activated within a few minutes.
5	To modify users in bulk, do the following sub-steps: Click Manage Users, and choose CSV Add or Modify User. Click Export to download the file. Edit the exported_users.csv file. For any users that you want to move, delete the value in the Hybrid Calendar Resource Group column. Save a first copy of the file in this state, for use later. To speed the move, set Hybrid Calendar (Exchange) to `FALSE`. Save a second copy of the file. Click Import, select the second file copy that you saved, and click Open. Choose Add and remove services, and click Submit. If you also add new users in this process and don't suppress admin invite emails, new users receive activation emails. Wait several minutes, and then re-import the first copy of the file. The users should be activated within a few minutes.

Architecture: Google Calendar with cloud-based Hybrid Calendar

Hybrid Calendar with Google Calendar: Scheduling flow

A user creates a meeting in Google Calendar, putting a scheduling keyword or video address in the location field.
Google sends a notification to the Hybrid Calendar.
The Hybrid Calendar requests and receives the encryption key, and then uses it to encrypt the meeting information.
The Hybrid Calendar validates meeting creation and recipients, and then creates a Webex team space, if applicable.
The Hybrid Calendar calls the API service and maps the meeting to the space.
The Hybrid Calendar retrieves the meeting join information, including the Personal Room if applicable.
The Hybrid Calendar updates the meeting invite with the meeting join information and, if applicable, the space ID.
The updated meeting information appears in Google Calendar.

For more information on how the Hybrid Calendar Service integrates with Google's G Suite Calendar, see the Hybrid Calendar with Google Calendar integration reference.

Prepare your environment

Requirements for Hybrid Calendar Service With Google Calendar

A Webex organization with one of the offers documented for the Hybrid Calendar in License Requirements for Cisco Webex Hybrid Services.

We do not currently support deploying both Google Calendar and Office 365 with the cloud-based Hybrid Calendar Service in the same Webex organization.
A Google G Suite organization (formerly Google Apps for Work) with Google accounts for all users in your Webex organization:

Each user in your Webex organization can only have one email address associated with only one Hybrid Calendar Service integration. In other words, the Hybrid Calendar Service will only process meetings from a single address for creating spaces, decorating meetings, showing the meetings list and join button, and sending One Button to Push (OTBP) to video devices.
- For Webex Teams scheduling:
  - Each user's Google account email address must match their Webex App login address.
- For Cisco Webex Personal Room scheduling with a Webex Meetings site:
  - You must enable the Personal Room feature for the Webex site and for the individual users.
  - The Google account email address should also match the user's Webex account address. If it does not, users must associate their Webex Personal Room with Webex Teams in the app in order to use @webex.
- To provide the meetings list and One-Button-to-Push Join button on room resources:
  - During setup, you need an administrator account which has permissions to manage access control lists on meeting room resources.
    
    In addition, you must verify the domain of the email address of this account.
  - Webex room devices must have email addresses that match the Google room resource format, @resource.calendar.google.com.
    
    If your room device email format uses a domain prefix, you must verify the domain in the prefix. For example, verify company.com (if you didn't already do so when verifying the domain of the account that manages access control lists) for devices that have email addresses such as:
```
company.com__3130313639353739333032@resource.calendar.google.com
```
    Newer resource email addresses may not include a domain prefix, as in the following example:
```
c_0803348627605091471198@resource.calendar.google.com
```

Remove Google Hangouts information in meeting events

In your G Suite Calendar settings, consider removing the video calls that are automatically added to events. This step ensures that meeting events contain just Webex join links when your users send them out.

This step prevents Google Calendar from including video event details in the meeting invitation that would conflict with the join details that the Hybrid Calendar Service adds. Suppressing this information does not disable Google Hangouts for your organization.

1	From https://admin.google.com, go to > Apps > G Suite > Calendar.
2	Click Sharing settings.
3	Under Video Calls, uncheck Automatically add video calls to events created by a user.

Deploy Hybrid Calendar with Google Calendar

Hybrid Calendar with Google Calendar deployment task flow

To deploy Hybrid Calendar with your Google Calendar environment, perform the following tasks.

Before you begin

Prepare Your Environment

1	Enable and configure Hybrid Calendar with Google Calendar Register your Google Calendar environment to the Webex cloud, test the connection, and set the default Webex site.
2	(Optional) Localize meeting join details To override how the Hybrid Calendar localizes meeting join details for your entire organization, set the Default Language setting in https://admin.webex.com.
3	(Optional) Configure @webex and @meet keywords To change the action that the Hybrid Calendar takes when users enter @webex or @meet, set the Keywords settings in https://admin.webex.com.
4	(Optional) Customize email templates Choose what the Hybrid Calendar adds to meeting invitations, including audio or video join details and a localized header and footer in any language that the service supports.
5	Enable the Hybrid Calendar with Google for users After successfully provisioning the service, you must explicitly activate users to allow the service to access their respective G suite calendars.
6	(Optional) Add Hybrid Calendar to workspaces with Board, Desk, and Room series If you want One Button to Push (OBTP) functionality to be provided to cloud-registered room and desk devices and Webex Boards, toggle on the calendar service for the devices, and configure the resource email address.
7	(Optional) Associate personal rooms with Webex App For OBTP on Webex room and desk devices and Webex Boards, make sure that meeting schedulers have their Personal Rooms associated with their Webex App accounts.
8	Test the Google Calendar and Hybrid Calendar integration

Enable and configure Hybrid Calendar with Google Calendar

Follow these steps to register your Google Calendar environment to the Webex cloud. The setup wizard in Control Hub guides you through the process.

1	Sign in to Control Hub.
2	Under Services, select Hybrid > Hybrid Calendar (Google) > Set Up. Domain-wide Delegation: Choose this option if you want to give Webex access to all rooms and calendars. Workspaces Only: Choose this option if you don't want to give domain-wide access, but still require Hybrid Calendar for workspaces. In the following steps, specify a workspace Admin account that has Google super-admin rights. This authorization expires every 180 days, per Google security policy. Reauthorize this every 180 days by following steps a—c in the Workspaces Only section and clicking Reauthorize. If you selected Domain-wide Delegation, proceed to step 3. If you selected Workspaces Only, proceed to step 4.
3	For Domain-wide Delegation, complete the following steps. In a new browser tab, open your G Suite account dashboard. From the Google Admin console, go to Security > Access and data control > API controls. In the Domain-wide delegation section, click MANAGE DOMAIN WIDE DELEGATION. Click Add New to add an API client. Copy the value for Client ID to the clipboard from the Control Hub tab you have open, and paste it into the corresponding field in your G Suite settings tab. Copy the text for Scope to the clipboard from the Control Hub tab you have open, and paste it into the corresponding field in your G Suite settings tab. Click Authorize, then return to this page and click Next. Enter the address of a test email account that already has a G Suite license, then click Next. This is used to test the connection with Google Calendar. (Optional) To enable Hybrid Calendar for Workspaces, provide a workspace Admin account that has Google super admin rights for all Google rooms that will be enabled with Hybrid Calendar. (Optional) To enable Room Scheduling from Workspaces, configure a Room scheduling account. This account requires Google super admin rights for all Google rooms that require in-room scheduling. You can reuse the workspace Admin account from the previous step. After the set up completed prompt appears, click Done. From the Hybrid Calendar card, go to the Google Calendar Settings. Choose or type the default Webex Meetings site that you want to use for @webex scheduling, and save your changes. The default site is used for @webex unless the user has a different site configured in their My Personal Room setting in the Webex App app (either because the user's Webex site has been linked to Control Hub by an administrator, or because the user configured the setting with a different site).
4	For Workspaces Only, complete the following steps. Click Workspaces Only, then click Next. Enter the Google account email address you want Hybrid Calendar to use to access Google room calendars. Make sure this account has Google super admin rights for all Google rooms that will be enabled with Hybrid Calendar. To use this Workspace Admin account for in-room scheduling, select Also use this account for in-room scheduling. Click Next. When prompted to choose a Google account, choose the same account you entered in step c. Click Finish. Once your authorization is complete, you can change it. Click Settings, then in the Authorization section, click Edit Authorization.

Localize meeting join details

In Control Hub, the Default Language setting controls the language of the join details that the Hybrid Calendar adds to invitations. If you leave the setting at its default, the service uses the language from the locale setting from scheduler's calendar settings.

To override choosing languages based on meeting schedulers' settings, choose a specific language to use for join details for all meetings across your organization.

1	Sign in to the customer view of https://admin.webex.com.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for Google, click Edit settings.
4	In the Meeting Invitations section, choose a language from the Default Language drop-down list, and click Save. After you save the change, the Hybrid Calendar uses the language you choose each time it adds join to details a meeting. It doesn’t change the language for existing join details.

Configure @webex and @meet keywords

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for your calendar environment, click Edit settings. If you have the Hybrid Calendar set up for multiple calendar environments, you can access the keywords settings from multiple pages in Control Hub, but the values that you set apply to all environments. The Hybrid Calendar (Microsoft 365) displays a list of tenants included in this organization.
4	Select the tenant to configure.
5	Click the Settings tab.
6	In the Keywords section, select the default action that you want for each keyword.
7	Click Save.

Customize email templates

Choose which meeting join details the calendar service includes in meeting invitations.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Meeting > Settings.
3	Locate the Meeting Join Customization section.
4	Choose whether to show Join by Phone details. When you include the dial-in details, you can also choose to add a link to global call-in numbers, a link to toll-free calling restrictions, or both.
5	Show or hide details on joining from an application or video conferencing device. When you include the video dialing details, you can also choose to include an IVR IP address, a Skype for Business join link, or both.
6	Click Add a Language and then select the language from the drop-down menu to create a custom header and footer for any of the languages that the Hybrid Calendar Service supports. When you've got the header and footer text that you want, click Save. The header and footer values have a maximum of 1024 characters each (including spaces).
7	Once you've added a custom header and footer for a language, you can choose that language as a default for any other language that doesn't have a custom header and footer defined. Your default language choice saves automatically.

Enable the Hybrid Calendar with Google for users

Use this procedure to enable a small number of Webex App users for Hybrid Calendar with Google Calendar.

See Ways to add and manage users in Control Hub for other methods, such as using a bulk CSV template.

Any of these methods requires that users have signed in to the Webex App to be fully activated. To enable @webex for users who have never signed in to the app, add and verify the users' domain using the Add, verify, and claim domains process. (You must own a domain for it to be verifiable. You do not need to claim the domain.)

Before you begin

To successfully activate a user for calendar access, the following conditions must be met:

Successful validation is a requirement for using the Hybrid Calendar functionality. If the service can't validate a user, it puts the user in error state. The service enforces a policy to access only the calendars of successfully activated users for ongoing processing.

1	Sign in to the customer view in https://admin.webex.com.
2	In the left-hand navigation pane, under Management click Users and then choose a specific user from the list. You can use the search function to narrow down the list of users.
3	Click the row to open an overview of the user.
4	Choose one and then save your changes: In a new environment, click Calendar Service, toggle on Calendar, and ensure that the Google Calendar is selected. In an existing environment with Exchange, click Calendar Service, and under calendar type, ensure that the Google Calendar is selected. After you activate the service, the Webex App user status changes from Pending Activation to Activated. The length of time for this change depends on the number of users that you're enabling for the service. Users receive an email that indicates the feature is enabled. See the documentation below if you want to disable email notifications.

What to do next

Test the calendar features

Schedule a Webex Meeting from Your Calendar.

Related Information

Disable User Email Notifications

Add Hybrid Calendar to workspaces with Board, Desk, and Room series

This task assumes that you've already created places for the Board, Desk, and Room devices. If you need to create the workspace, see Add shared devices and services to a workspace.

Before you begin

Webex room devices must have email addresses that match the Google room resource format, @resource.calendar.google.com.

If your room device email format uses a domain prefix, you must verify the domain in the prefix. For example, verify company.com (if you didn't already do so when verifying the domain of the account that manages access control lists) for devices that have email addresses such as:
```
company.com__3130313639353739333032@resource.calendar.google.com
```
Newer resource email addresses may not include a domain prefix, as in the following example:
```
c_0803348627605091471198@resource.calendar.google.com
```

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Workspaces.
3	Go to Scheduling and select Calendar so that users can use One Button to Push (OBTP) on their devices.
4	Select the calendar provider.
5	Enter or paste the Google resource email address from G Suite (Calendar > Resources). This is the email address that will be used to schedule meetings.
6	Click Save.

Associate personal rooms with Webex App

The users on your Webex site have been Webex App linked. (For site linking steps, see Link Webex sites to Control Hub.)
Users change their own preferred Webex site from the Webex App settings or preferences, see Change your default meeting site
For a comprehensive approach, use the bulk CSV import process from Control Hub to set users’ preferredWebExSite in the steps that follow.

1	Sign in to the customer view in https://admin.webex.com.
2	In the left-hand navigation pane, under Management click Users.
3	Click Manage Users.
4	See this article for the detailed CSV import/export procedure.
5	Use a CSV editor to change the `preferredWebExSite` attribute for all or some users.
6	Import the CSV file.

Test the Google Calendar and Hybrid Calendar integration

Use these steps to set up a test meeting and verify the Google Calendar integration. Direct users to the documentation below for how to schedule meetings.

1	Sign in to https://calendar.google.com with one of the test Google user accounts enabled for Hybrid Calendar.
2	Click Create to start an event, and then add a space scheduling keyword (such as @webex:space or @meet) to the Where field. Fill out other meeting information, as needed, and then click Save.
3	Open https://teams.webex.com, and sign in with the test user account.
4	Verify whether a new Webex space was created and contains the calendar invite card.
5	To test out-of-office status, in https://calendar.google.com, navigate to Settings and turn on Vacation responder. Within 20 minutes, you should see the test account's profile picture display an out-of-office overlay in Webex Teams, like this: The display picture update is triggered when others see your presence in a space. If the test user does not interact with other active users, you may need to use another account to verify the update.
6	To test the join button with a Webex room or desk device or Webex Board: In https://calendar.google.com, click Create to start an event, and then add a scheduling keyword (such as @webex) to the Location field. Click Rooms, and choose the device you want to add. Fill out other meeting information, as needed, and then click Save. When the meeting is scheduled to begin, verify that the Join button appears on the device.

Related Information

Schedule a Cisco Webex Meeting from Your Calendar

Show When You're Out of Office

Architecture: Expressway calendar connector

Expressway-based Calendar Connector for Microsoft Exchange and Office 365: Architecture

For a detailed overview of Hybrid Services, including architectural and design information for the Expressway-based Calendar Connector, we recommend that you read the Preferred Architecture for Cisco Webex Hybrid Services, Design Overview.

For more information on how the Calendar Connector integrates with Microsoft Exchange and Office 365, see the Cisco Webex Hybrid Calendar Service with Microsoft Exchange Integration Reference.

***Exchange (on-premises and cloud), Connector, and Webex Cloud Components for Hybrid Calendar Service***

***The Calendar Connector (installed on your Expressway server) is the on-premises component of the Hybrid Calendar for Microsoft Exchange.***

***One Button to Push (OBTP) topology: Cloud-registered Webex Room and desk devices and Webex boards***

***One Button to Push topology: Unified Communications Manager and TMS***

One Button to Push Topologies with the Calendar Connector

***Premises-Registered Endpoint OBTP with Cisco TMS and Cisco TMSXE***

An Exchange user schedules a meeting using a keyword or video address, and invites an on-prem video endpoint by its room mailbox address.
If the endpoint is available at that time, Microsoft Exchange automatically accepts the invitation on its behalf.
EWS notifications from Exchange alert the Calendar Connector and Cisco TMSXE that the meeting has been scheduled.
For Cisco Webex meetings, the Calendar Connector coordinates with the Cisco Webex cloud to schedule the meeting.
The Calendar Connector populates the user attribute "TMS:ExternalConferenceData" with the SIP URI for Cisco TMS to set the OBTP dial string.
Cisco TMSXE coordinates with Cisco TMS to book the meeting, if applicable. Cisco TMS sends OBTP information to the endpoints.

Office 365 and hybrid Exchange environments

Previously, to serve Office 365 users, you had to install the Calendar Connector on an on-premises Expressway. This on-premises deployment was required even if you didn't have a hybrid Exchange environment (on-premises Microsoft Exchange and an Office 365 tenant organization).

You can now choose to enable the cloud-based Hybrid Calendar for Office 365. With this service, hybrid Exchange environments have extra considerations:

You can run the Expressway-based Calendar Connector and the cloud-based Office 365 service at the same time.
Once you enable the cloud-based service, all Office 365 users who are not in any resource group automatically migrate to it.
To test the migration on a subset of users, make sure that the rest of the Office 365 users are in a resource group. Then enable the cloud-based Office 365 service.

***Hybrid Exchange environment with Hybrid Calendar***

The Calendar Connector on the Expressway-C serves both Exchange users and Office 365 users, in Resource Group A and Resource Group B. The cloud-based service serves any Office 365 users who are not in a resource group.

Prepare your environment

Management connector

The management connector is included in the Expressway-C base. You use it to register an Expressway to the cloud and link the Expressway interface with Control Hub. The management connector plays an important role as the coordinator of all connectors running on the Expressway server or cluster: It provides you with a single point of control for connector activities. The management connector enables cloud-based management of the on-premises connectors, handles initial registration with the cloud, manages the connector software lifecycle, and provides status and alarms.

For an HTTPS connection to be established between the management connector and the cloud, you must update the trust list on the Expressway-C connector host with certificates that were signed by certificate authorities in use by the Webex cloud. You can allow the Webex cloud to upload CA certificates to the Expressway-C trust store. Or, in the case where security policies prevent the Webex cloud from uploading trusted certificate authority certificates on Expressway-C, you may upload them manually.

Calendar connector

The calendar connectoris the on-premises component of the Hybrid Calendar. The connector runs on an Expressway-C host that you register to the Webex cloud.

The calendar connector acts like a broker between the cloud and your Microsoft Exchange (on-premises), Office 365 (cloud), or both (Hybrid Exchange deployment). The connector acts on behalf of users, similar to the way a client application would access a user's calendar information. The connector uses the impersonation role (which you can restrict to a subset of users) and uses Exchange Web Services to:

Autodiscover where users are homed
Listen for notifications on a user's calendar
Retrieve information on a user's calendar items and Out-of-Office status
Populate meeting invitations with details of Webex App spaces and Webex personal rooms.

The Hybrid Calendar is designed to minimize security concerns in a hybrid environment:

The cloud cannot retrieve or access the Exchange credentials from the connector
The cloud has no direct access to Exchange through the connector
The connector does not access any user email or contacts
The connector does not create search folders or other extra folders for the user
The connector is not an Exchange Foreign connector
The connector does not interact with the Exchange Hub transport server
No AD schema extensions are required

In production Exchange, the calendar connector increases the CPU usage and load on the CAS and MBX servers. The impact on your Exchange environment depends on:

Your Exchange deployment
The number of configured users
The number of meetings that the Hybrid Calendar updates per user per hour
The size of calendars

We document a throttling policy designed to help manage the increased traffic.

Calendar connector or cloud-based for Office 365 Users

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, a combination of the calendar connector and the cloud-based service, or, if you have no Microsoft Exchange users, deploy only 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).

The cloud-based service supports the TelePresence Management Suite (TMS) scheduling option. This integration allows the service to leverage your on-premises resource management and conference hosting environment for simplified meeting scheduling. The integration also extends the meeting join experience to a wide range of video devices. The cloud-based service links to the on-premises TMS by using the calendar connector. For this reason, you cannot deploy the TMS integration in the same organization with a calendar connector that is configured for Microsoft Exchange or Office 365.

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 part of this guide, to understand the requirements for that option.

Requirements for Hybrid Calendar

Product	Release
Webex App	Hybrid Calendar is available with the offers documented in License Requirements for Webex Hybrid Services.
Expressway—download from software.cisco.com at no charge	We recommend the latest release of Expressway for connector host purposes. See Expressway Connector Host Support for Cisco Webex Hybrid Services for information about Expressway version support.
Microsoft Exchange	2013, 2016, 2019 Microsoft 365
Webex Meetings—Use for @webex scheduling only; not required for scheduling meetings in Webex team spaces.	Any supported Webex Meetings release You must enable the Personal Room feature for the Webex site and for the individual users.

Each user's email address in the calendar system (Microsoft Exchange or Microsoft 365) must match their Webex App login address. To use @webex, the address should also match the user's Webex account address. If it does not, users must associate their Webex Personal Room with Cisco Webex Teams in the app in order to use @webex.

Each Webex App user can only have one email address associated with only one Hybrid Calendar integration. In other words, the Hybrid Calendar will only process meetings from a single address for creating spaces, decorating meetings, showing the meetings list and join button, and sending the Join button to video devices.

Set Up an impersonation account for on-premises Microsoft Exchange

The Microsoft Exchange impersonation account ( https://msdn.microsoft.com/en-us/library/office/dn722377(v=exchg.150).aspx) is a key integration point for the Hybrid Calendar. The service uses the impersonation account for continuous authentication with Microsoft Active Directory domain controllers and Microsoft Exchange Client Access Servers.

To ensure that impersonation remains secure and continuously connected, we recommend an account maintenance strategy such as using two impersonation accounts. This can prevent exposure to password expiry, which could take the service offline. To periodically rotate between the accounts, you change the account in the Calendar Connector configuration. The example in the following table shows one possible account rotation scheme, though you may choose a different strategy to ensure security and connectivity based on your organization's requirements:

Date	Account A hybridcalendarA@example.com	Account B hybridcalendarB@example.com
January 1	Set password	Set password
January 8	Configure Calendar Connector with account A	—
March 1	—	Change password
March 8	—	Update Calendar Connector with account B
May 1	Change password	—
May 8	Update Calendar Connector with account A	—
July 1	—	Change password
July 8	—	Update Calendar Connector with account B
Repeat the password rotation and Calendar Connector update process with both accounts.

Before you begin

You must choose a mail-enabled account to use as the service account. (The account doesn't have to be an administrator, but it must have a mailbox.)
Do not use an impersonation account that is used by other services such as Unity Connection, TMSXE, and so on.
If you limited the set of users that are synchronized with Active Directory using LDAP filters, you may want to limit the impersonation by using a new or existing management scope in Exchange.
For instructions and more detailed information from Microsoft on management scopes and impersonation, see the Microsoft Docs ApplicationImpersonation role article.

An account that is a member of the Enterprise Admins group.
An account that can grant permissions on Exchange objects in the configuration container.

Run the following command in Exchange Management Shell:

new-ManagementRoleAssignment -Name: RoleName -Role:ApplicationImpersonation -User 'ServiceUserName'

where:

RoleName is the name that you want to give the assignment, for example, CalendarConnectorAcct. The name that you enter for RoleName appears when you run get-ManagementRoleAssignment.
ServiceUserName is the name of the account you selected, in domain\alias format.

Set up an impersonation account for Office 365

Give impersonation permissions to the service account that the Calendar Connector will use with Office 365.

Before you begin

For a hybrid Exchange on-premises and Office 365 integration, you can use a simplified configuration with a single impersonation account if your deployment meets all of the following criteria:
- You synchronize your on-premises Exchange accounts to the Office 365 cloud.
  
  The impersonation account that you use must also be synchronized the Office 365 cloud, and the account's userPrincipalName must match one of its SMTP addresses.
- You administer all users in the on-premises Active Directory, including users whose mailboxes have been migrated to the Office 365 cloud.
- You synchronize passwords, or have a configured a federation so that users have a single password both on-premises and in the cloud.
- Your Exchange is configured such that all autodiscovery requests reach the on-premises environment. (If a mailbox has been migrated, the response indicates the relocation and provides the cloud email address.)
In the simplified configuration, you use a single impersonation account to service all users. Because ApplicationImpersonation privileges that you assign on-premises do not automatically apply to mailboxes homed in the Office 365 cloud, you must still explicitly assign these privileges. To do so, follow this procedure and use the same service account that you used in Set Up an impersonation account for on-premises Microsoft Exchange . Later, you'll set up only one Microsoft Exchange configuration on the Expressway-C.

For a hybrid integration that does not meet these criteria, follow this procedure and use a different service account for impersonation than you used in Set Up an impersonation account for on-premises Microsoft Exchange. Later, you'll set up two Exchange configuration records on the Expressway-C: one for the Exchange on-premises integration, and one for the Office 365 integration.
You must choose a mail-enabled account for this task. (The account doesn't have to be an administrator, but it must have a mailbox.)
Do not use an impersonation account that is used by other services such as Unity Connection, TMSXE and so on.
Ensure that the service account can authenticate with the authentication service or directory that is used in your deployment.

1	Log in to the Office 365 Admin Center using the administrator account.
2	Under Admin, select Exchange.
3	Select Permissions.
4	Under Admin Roles, create a new role group and enter a descriptive name, such as `ImpersonationGroup`.
5	Under Roles, add a new role. Select ApplicationImpersonation role.
6	Add the role to the group, and then select OK.
7	Add the service account to be used for impersonation to the group.

Complete the prerequisites for Hybrid Calendar

1	Allow time to configure the impersonation account. See Exchange Impersonation Account to understand the role of the account and for answers to common questions that are related to security.
2	Install or make sure you're running a supported calendar environment, as described in Requirements for Hybrid Calendar.
3	Ensure that users are listed in Active Directory and have a discoverable mailbox in the organization's Exchange server.
4	(Optional) Download the latest Directory Connector software from Control Hub ( https://admin.webex.com) and use it to import user attributes from your Active Directory. For more information about how to use Directory Connector, see the Deployment Guide for Cisco Directory Connector.
5	Provide the following port access: Port access for HTTPS or secure web sockets outbound from Expressway to .ciscospark.com, . rackcdn.com, .wbx2.com, .webex.com, and *.webexcontent.com: TCP port 443 (secure) Port access for EWS outbound from Expressway to Exchange: TCP port 443 (secure) or TCP port 80 (nonsecure) Port access for LDAP outbound from Expressway to Active Directory: TCP port 636 (secure) or TCP port 389 (nonsecure) Port access for Microsoft Global Catalog search: TCP port 3269 (for Global Catalog search secured by SSL) or TCP port 3268 (for unsecured Global Catalog search).
6	For @webex functionality, configure or use a Webex Meetings site. You must enable the Personal Room feature for the site and for the individual users.
7	To make One Button to Push (OBTP) available for Unified CM-registered endpoints managed by TMS: Set up TMS 15.0 and TMSXE 5.0 or higher with Microsoft Exchange integration. See the Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide (TMS 15.0 - WebEx Meeting Center WBS30). TMS and XE require no additional configuration to support Hybrid Calendar. To make conference rooms schedulable in Microsoft Outlook/Exchange, configure them in XE as if you were using on-premises conferencing. To configure rooms in Exchange, use the Cisco TelePresence Management Suite Extension for Microsoft Exchange Administration Guide. Understand the licensing requirements: TMS and XE Licensing is the same as if using on-premises resources. You require enough licenses to cover the number of endpoints that will use OBTP. A TMS license is needed to manage the endpoint and to push the speed dial button on the touchpad at the time of the scheduled conference. A TMS-XE license is needed for the endpoint to be scheduled in Exchange. For Unified CM-registered endpoints, OBTP works with Hybrid Calendar and Productivity Tools plugin for meeting invitations: Hybrid Calendar (scheduling keywords or supported video address) populates the user attribute "TMS:ExternalConferenceData" with the SIP URI for TMS to set the OBTP dial string. Productivity Tools plugin populates the attribute "UCCapabilities" attribute with the SIP URI for TMS to set the OBTP dial string. If you plan to deploy a hybrid Exchange environment with Office 365, you must enable TNEF for remote domains in Exchange Online. Having TNEF disabled causes Exchange Online to strip the TMS:ExternalConferenceData and UCCapabilities attributes, breaking OBTP for Unified CM-registered endpoints. For more information on TNEF, see https://docs.microsoft.com/en-us/exchange/mail-flow/content-conversion/tnef-conversion. If you have on-premises conferencing, you can add OBTP with Webex Meetings and run both at same time. We support OBTP functionality only; auto connect is not available.

Complete the Expressway-C connector host prerequisites for Hybrid Services

Use this checklist to prepare an Expressway-C for Hybrid Services, before you register it to the Webex cloud to host hybrid services connector software.

Before you begin

We recommend that the Expressway-C be dedicated to hosting connectors for Hybrid Services. You can use the Expressway-C connector host for other purposes, but that can change the supported number of users.

See User Capacity Limits for Expressway-based Hybrid Services so that you can plan your deployment accordingly.

As an administrator of hybrid services, you retain control over the software running on your on-premises equipment. You are responsible for all necessary security measures to protect your servers from physical and electronic attacks.

1	Obtain full organization administrator rights before you register any Expressways, and use these credentials when you access the customer view in Control Hub ( https://admin.webex.com).
2	Plan your connector capacity by referring to User Capacity Limits for Expressway-based Hybrid Services.
3	Deploy the Expressway-C connector host in a cluster to account for redundancy. Follow the supported Expressway scalability recommendations: For Hybrid Calendar (Exchange or Office 365) on a dedicated Expressway-C: calendar connector can be hosted on multiple Expressway-C clusters of up to 6 nodes each. calendar connector can under-provision users. If a single node fails, the system has extra capacity for all users to fail over to the working node. If one of the nodes fails in the cluster, the discovery and assignment services move users to the working node in approximately 30 seconds. The service catches up on any missed notifications if there is an outage. For hybrid call on a dedicated Expressway-C: call connector supports multiple Expressway-C clusters with no specific upper limit. Each cluster supports up to 6 Expressway-C nodes for active/active redundancy. For Hybrid Message on a dedicated Expressway-C: message connector can be hosted on multiple Expressway-C clusters of up to 6 nodes each. message connector can be used with multiple Unified Communications Manager IM and Presence Service clusters. Hybrid Calling is highly available if Unified CM and Expressways are deployed in a cluster. The same guidelines apply for the Expressway-C connector host clustering. For more information, see User Capacity Limits for Expressway-Based Hybrid Services. Hybrid Calendar is highly available if Exchange and Expressways are deployed in a cluster. The same guidelines apply for the Expressway-C connector host clustering. For more information, see User Capacity Limits for Expressway-Based Hybrid Services.
4	Follow these requirements for the Expressway-C connector host. Install the minimum supported Expressway software version. See the version support statement for more information. Install the virtual Expressway OVA file according to the Cisco Expressway Virtual Machine Installation Guide, after which you can access the user interface by browsing to its IP address. You can find the document in the list of Cisco Expressway Install and Upgrade Guides on cisco.com. The serial number of a virtual Expressway is based on the virtual machine's MAC address. The serial number is used to validate Expressway licenses and to identify Expressways that are registered to the Webex cloud. Do not change the MAC address of the Expressway virtual machine when using VMware tools, or you risk losing service. You do not require a release key, or an Expressway series key, to use the virtual Expressway-C for Hybrid Services. You may see an alarm about the release key. You can acknowledge it to remove it from the interface. Use the Expressway web interface in a supported browser. (See the Cisco Expressway Administrator Guide.) The interface may or may not work in unsupported browsers. You must enable JavaScript and cookies to use the Expressway web interface.
5	If this is your first time running Expressway, you get a first-time setup wizard to help you configure it for Hybrid Services. Select Webex Hybrid Services. This ensures that you will not require a release key.
6	Check that the following requirements are met for the Expressway-C connector host. You would normally do this during installation. See the Cisco Expressway Basic Configuration Deployment Guide, in the list of Cisco Expressway Configuration Guides on cisco.com, for details. Basic IP configuration (System > Network interfaces > IP) System name (System > Administration settings) DNS settings (System > DNS) NTP settings (System > Time) New password for admin account (Users > Administrator accounts, click Admin user then Change password link) New password for root account (Log on to CLI as root and run the passwd command) Expressway-C connector hosts do not support dual NIC deployments.
7	Configure the Expressway-C as a "cluster of one": We recommend that you configure the Expressway as a primary peer before you register it, even if you do not currently intend to install an extra peer. When you change clustering settings on X8.11 and later, be aware that removing all peer addresses from the System > Clustering page signals to the Expressway that you want to remove it from the cluster. This causes the Expressway to factory reset itself on its next restart. If you want to remove all peers but keep configuration on the remaining Expressway, leave its address on the clustering page and make it the primary in a "cluster of one". Here are the minimum clustering settings required, but the Cisco Expressway Cluster Creation and Maintenance Deployment Guide has more detail: Enable H.323 protocol. On Configuration > Protocols > H.323 page, set H.323 Mode to On. H.323 mode is required for clustering, even if the Expressway does not process H.323 calls. You may not see the H.323 menu item if you used the Service Select wizard to configure the Expressway for Hybrid Services. You can work around this problem by signing in to the Expressway console and issuing the command `xconfig H323 Mode: "On"`. System > Clustering > Cluster name should be an FQDN. Typically this FQDN is mapped by an SRV record in DNS that resolves to A/AAAA records for the cluster peers. System > Clustering > Configuration primary should be 1. System > Clustering > TLS verification mode should be Permissive, at least until you add a second peer. Select Enforce if you want cluster peers to validate each others' certificates before allowing intercluster communications. System > Clustering > Cluster IP version should match the type of IP address of this Expressway-C. System > Clustering > Peer 1 address should be the IP address or FQDN of this Expressway Each peer FQDN must match that Expressway's certificate if you are enforcing TLS verification. To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Expressway-C. Capitalization is not supported at this time.
8	If you have not already done so, open required ports on your firewall. All traffic between Expressway-C and the Webex cloud is HTTPS or secure web sockets. TCP port 443 must be open outbound from the Expressway-C. See https://collaborationhelp.cisco.com/article/WBX000028782 for details of the cloud domains that are requested by the Expressway-C.
9	Get the details of your HTTP proxy (address, port) if your organization uses one to access the internet. You'll also need a username and password for the proxy if it requires basic authentication. The Expressway cannot use other methods to authenticate with the proxy. We tested and verified Squid 3.1.19 on Ubuntu 12.04.5. We have not tested auth-based proxies. If your organization uses a TLS proxy, the Expressway-C must trust the TLS proxy. The proxy's CA root certificate must be in the trust store of the Expressway. You can check if you need to add it at Maintenance > Security > Trusted CA certificate . The details of the proxy, as configured on the primary Expressway in the connector host cluster, are shared throughout the Expressway cluster. You cannot configure different proxies for different nodes in the cluster.
10	Review these points about certificate trust. You can choose the type of secure connection when you begin the main setup steps. Hybrid Services requires a secure connection between Expressway-C and Webex. You can let Webex manage the root CA certificates for you. However, if you choose to manage them yourself, be aware of certificate authorities and trust chains; you must also be authorized to make changes to the Expressway-C trust list. Access to the Expressway CA trust list may also be required if you want to secure the connections between Expressway-C and Microsoft Exchange, or between Expressway-C and Microsoft® Active Directory®, when configuring the calendar connector.

Configure Hybrid Calendar book version

Hybrid Calendar with Exchange deployment task flow

To deploy Hybrid Calendar with your Microsoft Exchange environment, perform the following tasks.

Before you begin

Prepare your environment

1	Configure a throttling policy for impersonation account A custom throttling policy helps the calendar connector work smoothly.
2	Register Expressway-C connector hosts to Cloud Add the Hybrid Calendar to your organization and connect your Expressway to the Webex cloud. This creates a resource in https://admin.webex.com and downloads connector software on to the Expressway.
3	(Optional) Append the Exchange CA certificate to the Expressway trusted CA list If you want Microsoft Exchange Web Services (EWS) traffic to be encrypted, make sure the Expressway trust list contains the certificate of the CA that signed the Exchange Server certificate.
4	Link the calendar connector to Microsoft Exchange Configure Exchange Servers for the calendar connector.
5	(Optional) Configure the Calendar Connector's Webex site settings If you have a Webex Meetings site, configure the @Webex functionality.
6	(Optional) Choose how Hybrid Calendar localizes meeting join details To override how the calendar connector localizes meeting join details for your entire organization, set the Default Language setting in https://admin.webex.com.
7	(Optional) Configure @webex and @meet keywords To change the action that the calendar connector takes when users enter @webex or @meet, set the Keywords settings in https://admin.webex.com.
8	(Optional) Customize Email Templates Choose what the Hybrid Calendar adds to meeting invitations, including audio or video join details and a localized header and footer in any language that the service supports.
9	Start the calendar connector
10	Enable Hybrid Calendar for users
11	(Optional) Add Hybrid Calendar to workspaces with Board, Desk, and Room Series If you want One Button to Push (OBTP) functionality to be provided to room and desk devices and Webex Boards that are registered to the Webex cloud, toggle on the calendar service for the device, and configure the room mailbox email address.
12	(Optional) Associate user's Personal Rooms with Webex For OBTP on Webex room and desk devices and Webex Boards, make sure that meeting schedulers have their Webex Personal Rooms associated with their Webex App accounts.
13	Test join button with room devices If you configured OBTP in the previous steps, test it with a device.

Configure a throttling policy for impersonation account

A custom throttling policy helps the calendar connector work smoothly:

The custom policy removes EWS limits from the impersonation account, to avoid issues such as maxconcurrency.
The custom policy is tailored for an enterprise application. (The default policy is tailored for user load.)

Before you begin

Set Up an impersonation account for on-premises Microsoft Exchange

This procedure is not required for Office 365.

1	In Exchange Management Shell, create the policy. `New-ThrottlingPolicy -Name` `"CalendarConnectorPolicy"` `-EWSMaxConcurrency unlimited -EWSMaxBurst unlimited -EWSRechargeRate unlimited -EWSCutOffBalance unlimited -EWSMaxSubscriptions 5000`
2	If the impersonation account does not have a mailbox, run the following command: `Enable-Mailbox` `"impersonation account"` `-Database` `"database name"`
3	Apply the new policy to the impersonation account: `Set-ThrottlingPolicyAssociation -Identity` `"impersonation account"` `-ThrottlingPolicy` `"CalendarConnectorPolicy"` where `"impersonation account"` is the name of the impersonation account you're using as the service account for the calendar connector. `CalendarConnectorPolicy` is the name of the policy that you created in Step 2.
4	Confirm that the mailbox is using the new policy: `Get-ThrottlingPolicyAssociation -Identity` `"impersonation account"` `\| findstr "ThrottlingPolicy"`

What to do next

Register Expressway-C connector hosts to Cloud

Hybrid Services use software connectors hosted on Expressway-C to securely connect Webex to your organization's environment. Use this procedure to register Expressway-C resources to the cloud.

After you complete the registration steps, the connector software is automatically deployed on your on-premises Expressway-C.

Before you begin

Make sure your Expressway-C is running on a version that's supported for hybrid services. See the Supported Versions of Expressway for Cisco Webex Hybrid Services Connectors documentation ( https://help.webex.com/article/ruyceab) for more information about which versions are supported for new and existing registrations to the cloud.
Sign out of any open connections to the Expressway-C interface that are open in other browser tabs.
If your on-premises environment proxies the outbound traffic, you must first enter the details of the proxy server on Applications > Hybrid Services > Connector Proxy before you complete this procedure. Doing so is necessary for successful registration.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid and then choose one: If this is the first connector host you're registering, click Set up on the card for the hybrid service you're deploying, and then click Next. If you've already registered one or more connector hosts, click View all on the card for the hybrid service you're deploying, and then click Add Resource. The Webex cloud rejects any attempt at registration from the Expressway web interface. You must first register your Expressway through Control Hub, because the Control Hub needs to hand out a token to the Expressway to establish trust between premises and cloud, and complete the secure registration.
3	Choose a method to register the Expressway-C: New Expressways—choose Register a new Expressway with its Fully Qualified Domain Name (FQDN), enter your Expressway-C IP address or fully qualified domain name (FQDN) so that Webex creates a record of that Expressway-C and establishes trust, and then click Next. You can also enter a display name to identify the resource in Control Hub. To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Expressway-C. Capitalization is not supported at this time. Existing Expressways—choose Select an existing Expressway cluster to add resources to this service, and then choose the node or cluster from the drop-down that you previously registered. You can use it to run more than one hybrid service. If you're registering a cluster, register the primary peer. You don't need to register any other peers, because they register automatically when the primary registers. If you start with one node set up as a primary, subsequent additions do not require a system reboot.
4	Click Next, and for new registrations, click the link to open your Expressway-C. You can then sign in to load the Connector Management window.
5	Decide how you want to update the Expressway-C trust list: A check box on the welcome page determines whether you will manually append the required CA certificates to the Expressway-C trust list, or whether you allow Webex to add those certificates for you. Choose one of the following options: Check the box if you want Webex to add the required CA certificates to the Expressway-C trust list. When you register, the root certificates for the authorities that signed the Webex cloud certificates are installed automatically on the Expressway-C. This means that the Expressway-C should automatically trust the certificates and be able to set up the secure connection. If you change your mind, you can use the Connector Management window to remove the Webex cloud CA root certificates and manually install root certificates. Uncheck the box if you want to manually update the Expressway-C trust list. See the Expressway-C online help for the procedure. When you register, you will get certificate trust errors if the trust list does not currently have the correct CA certificates. See Certificate Authorities for Hybrid Services.
6	Click Register. After you're redirected to Control Hub, read the on-screen text to confirm that Webex identified the correct Expressway-C.
7	After you verify the information, click Allow to register the Expressway-C for Hybrid Services. Registration can take up to 5 minutes depending on the configuration of the Expressway and whether it's a first-time registration. After the Expressway-C registers successfully, the Hybrid Services window on the Expressway-C shows the connectors downloading and installing. The management connector automatically upgrades itself if there is a newer version available, and then installs any other connectors that you selected for the Expressway-C connector host. Each connector installs the interface pages that you need to configure and activate that connector. This process can take a few minutes. When the connectors are installed, you can see new menu items on the Applications > Hybrid Services menu on your Expressway-C connector host. If registration fails and your on-premises environment proxies the outbound traffic, review the Before You Begin section of this procedure. If the registration process times out or fails (for example, you must fix certificate errors or enter proxy details), you can restart registration in Control Hub.

Append the Exchange CA certificate to the Expressway trusted CA list

If you want to verify the certificates presented by the Exchange Server, then the Expressway trust list must contain the certificate of the CA that signed the Exchange Server certificate. The CA certificate may already be in the trust list; use this procedure on each Expressway cluster to check the list and append the certificate if necessary.

If you're using a custom domain, make sure that you add the CA certificate for the domain certificate issuer to the Expressways.

Before you begin

You must import certificates to each Expressway-C.

1	On the Expressway-C connector host, go to Maintenance > Security certificates > Trusted CA certificate.
2	Review the CA certificates in the trust list to check if the correct CA certificate is already trusted.
3	To append any new CA certificates: Click Browse (or the equivalent in your browser) to locate and select the PEM file. Click Append CA certificate. The newly appended CA certificate appears in the list of CA certificates.
4	To replace an existing CA certificate with an updated one, for a particular issuer and subject: Check the check box next to the Issuer details. Click Delete. Append the replacement certificate as described above.

Certificate Authorities for Hybrid Services

The table lists the Certificate Authorities that your on-premises or existing environment must trust when using Hybrid Services.

If you opted to have Webex manage the required certificates, then you do not need to manually append CA certificates to the Expressway-C trust list.

The issuers used to sign the Webex host certificates may change in future, and the table below may then be inaccurate. If you are manually managing the CA certificates, you must append the CA certificates of the issuing authorities that signed the currently valid certificates for the hosts listed below (and remove expired/revoked CA certificates).

Cloud hosts signed by this CA

Issuing CA

Must be trusted by

For this purpose

CDN

O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root

Expressway-C

To ensure Expressway downloads connectors from a trusted host

Common identity service

O=VeriSign, Inc., OU=Class 3 Public Primary Certification Authority

Windows Server 2003 or Windows Server 2008 hosting the Cisco directory connector

Expressway-C

To synchronize users from your Active Directory with Webex and to authenticate Hybrid Services users

Webex App

O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority

Expressway-C

Related Information

Supported Certificate Authorities for Cisco Webex

Link the calendar connector to Microsoft Exchange

The calendar connector installs automatically after you register your Expressway connector host for Hybrid Services. The connector does not start automatically, and requires some configuration to link to your calendar environment.

1	From the Expressway connector host, go to Applications > Hybrid Services > Calendar Service > Microsoft Exchange Configuration, and then click New. Make sure you choose Microsoft Exchange Configuration, not Cisco Conferencing Services Configuration. You cannot configure the Calendar Connector for Microsoft Exchange or Office 365 in the same organization with the conferencing services (integration with Cisco TelePresence Management Suite).
2	Enter the credentials of the service account that you want the calendar connector to use to connect to Exchange. The service account queries calendars on behalf of your users, using the impersonation role. You can use these formats: `username@domain.com`—The userPrincipalName. Typically, this value matches the user's primary email address, but the properties are separate. userPrincipalName consists of the User Logon Name (not always the same as sAMAccountName) and the UPN suffix, which is based on the Active Directory domain (not always the same as the NetBIOS domain). Use this format whenever possible. If you used the simplified configuration with a single impersonation account to prepare a hybrid Exchange on-premises and Office 365 integration, you must use this format. Also, make sure that the impersonation account that you use is synchronized to the Office 365 cloud, and that its userPrincipalName matches one of the account's SMTP addresses. `DOMAIN\username`—DOMAIN is the NetBIOS domain (the pre-Windows 2000 domain); "username" is the sAMAccountName (the legacy username or pre-Windows 2000 username). If you're unsure about what to use for these formats, use Active Directory Users and Computers on a Windows machine to view the Account tab of the Properties pane for the user in question. The correct values to use are displayed as: User logon name for the first format. User logon name (pre-Windows 2000) for the second format.
3	Enter a unique Display Name for this Exchange Server.
4	For the Type, select Exchange On-Premises for Exchange 2013, 2016, or 2019. (Select this type even if you are preparing a hybrid Exchange on-premises and Office 365 integration.)
5	For Need Proxy for Connection?, select Yes if https access goes through a web proxy to your Exchange environment.
6	For Enable this Exchange server?, select Yes. You can select No for debugging purposes, but users will not be subscribed to this Exchange.
7	Check a value for the Authentication Type: For added security, we recommend NTLM for on-premises Exchange servers. For Hybrid Exchange (on-premises and Office 365) deployments, check both NTLM and Basic authentication types. If one method fails, then the other method is used.
8	Leave TLS Verify Mode as the default value (On) so that this Expressway-C verifies the certificate that the Exchange Server presents. You may need to update the trust stores on both servers to ensure that each one trusts the CA that signed the other's certificate.
9	Under Discovery, select Use Autodiscover to enable autodiscovery. The calendar connector queries to find one or more Exchange servers. You must use autodiscovery for deployments of Microsoft Exchange 2013 and later. Use Provide Exchange Address directly only for troubleshooting or testing purposes. This option does not use autodiscovery. If you select it, enter the IPv4 address, IPv6, or FQDN of the Exchange server.
10	Configure the extra fields that are related to autodiscovery. Choose whether to Enable SCP record lookup. If you set this field to Yes, the first autodiscover step that the calendar connector takes is an Active Directory Service Connection Point (SCP) record lookup to get a list of autodiscover URLs. The calendar connector uses the Active Directory domain, Active Directory site, Query mode, and LDAP TLS Verify Mode and fields only if you enable this step. These fields provide the information necessary to find and query an LDAP server in Active Directory. Even if this step fails, autodiscovery may succeed at a later step. Enter the Active Directory domain to query for the SCP record. Enter the Active Directory site that is geographically closest to the calendar connector, to optimize the query response time. Select a Query mode to control which directory access protocol that calendar connector uses to query Active Directory. If you select ldaps (secure LDAP), the Domain Controller must authenticate itself by presenting a server certificate to this Expressway-C. Enable LDAP TLS Verify Mode if you want the Expressway-C to validate the certificate that the Domain Controller presents. This option checks the server name against the CN or SANs in the received certificate, and also checks that the issuing authority is in the local trusted CA list. Enter an Email Address so that calendar connector can test the autodiscover process (other than SCP record lookup, which uses the Active Directory domain instead). Use the email address of a user that you will enable for the Hybrid Calendar Service, as it appears in Control Hub. If the test fails, then your settings are not saved. If you omit the email address, then your settings are saved without verifying the autodiscover process (other than SCP record lookup, if enabled). To manually configure any Autodiscover redirect URLs that the Calendar Connector should trust, click Configure Trust List. Once you click Add, the Calendar Connector automatically populates any missing Autodiscover redirect URLs that it finds while contacting the Autodiscover service. URLs from unauthenticated sources are placed in pending state, and blocked unless you choose to allow them. If you skip this step now, you can still manually add URLs later, or explicitly accept or deny the pending URLs.
11	Click Add to store the Exchange Server configuration on the Expressway connector host. The calendar connector tests the connection to the Exchange environment, and notifies you if there are pending Autodiscover redirect URLs to review.
12	(Optional) If your organization has multiple user email domains, we recommend that you test the autodiscover configuration with a user address from each email domain to ensure that the process works for all of them. To test another address, change the value of the Email Address field to a different address, and then click Save..

What to do next

Configure the Calendar Connector's Webex site settings

After you configure the Exchange settings, configure the details for your Webex Meetings sites. If you have more than one Webex site, do these steps for each site, and set the default to the site with the most users. Users who are not on the default site, or who want to use a different site, must set up their Personal Room in the Webex app.

Before you begin

For the @webex functionality to work for users, verify the following:
- You have at least one Webex Meetings site, with the Personal Room feature enabled for the site and for the individual users.
- The email address in each user's Webex account matches the user's Exchange email address and Webex App login address. If it does not, users must set up their Personal Room in the Webex app.
Gather the Webex user account email address of a valid user on your site. The calendar connector uses this account to access the Webex Personal Room details for users who schedule meetings with @webex.

1	From the Expressway-C connector host, go to Applications > Hybrid Services > Calendar Service > Cisco Conferencing Services Configuration, and then click New.
2	Select Type as Webex under Conferencing Services Type.
3	Enter the Fully Qualified Site Name for this Webex Meetings site. If your site is accessed as example-co.webex.com, you'd enter example-co.webex.com.
4	Enter a valid Webex user account email address, leave the password field blank, and then click Test Connection to validate the site information that you entered. If testing the connection fails, you can save the configuration with both the user name and password fields blank.
5	Indicate whether or not this site is the default. The default site is used for @webex unless the user has a different site configured in their My Personal Room setting in the Webex App app (either because the user's Webex site has been linked to Control Hub by an administrator, or because the user configured the setting with a different site).
6	Click Save to save the configuration.

Choose how Hybrid Calendar localizes meeting join details

In Control Hub, the Default Language setting controls the language of the join details that the Hybrid Calendar adds to invitations. If you leave the setting at its default, the service uses the language from the item.Culture property of each meeting invitation. (Typically, the scheduler's operating system controls the value of item.Culture.)

To override choosing languages on a meeting-by-meeting basis from item.Culture, choose a specific language to use for join details for all meetings across your organization.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for Exchange, click Edit settings.
4	In the Meeting Invitations section, choose a language from the Default Language drop-down list, and click Save. After you save the change, the Hybrid Calendar uses the language you choose each time it adds join to details a meeting. It doesn’t change the language for existing join details.

Configure @webex and @meet keywords

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for your calendar environment, click Edit settings. If you have the Hybrid Calendar set up for multiple calendar environments, you can access the keywords settings from multiple pages in Control Hub, but the values that you set apply to all environments. The Hybrid Calendar (Microsoft 365) displays a list of tenants included in this organization.
4	Select the tenant to configure.
5	Click the Settings tab.
6	In the Keywords section, select the default action that you want for each keyword.
7	Click Save.

Customize Email Templates

Choose which meeting join details the calendar service includes in meeting invitations.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Meeting > Settings.
3	Locate the Meeting Join Customization section.
4	Choose whether to show Join by Phone details. When you include the dial-in details, you can also choose to add a link to global call-in numbers, a link to toll-free calling restrictions, or both.
5	Show or hide details on joining from an application or video conferencing device. When you include the video dialing details, you can also choose to include an IVR IP address, a Skype for Business join link, or both.
6	Click Add a Language and then select the language from the drop-down menu to create a custom header and footer for any of the languages that the Hybrid Calendar Service supports. When you've got the header and footer text that you want, click Save. The header and footer values have a maximum of 1024 characters each (including spaces).
7	Once you've added a custom header and footer for a language, you can choose that language as a default for any other language that doesn't have a custom header and footer defined. Your default language choice saves automatically.

Start the calendar connector

You can do this task before you configure the calendar connector links to your Exchange environment and Webex environment, but all tests will fail until the calendar connector is Running and you may need to restart the connector after configuration.

1	From Expressway, go to Applications > Hybrid Services > Connector Management. The Connector management section of the page has a list of connectors and the status of each. The Management Connector is Running and the Calendar Connector is Not enabled.
2	Click Calendar Connector.
3	Select Enabled from the Active drop-down list.
4	Click Save. The calendar connector starts and the status changes to Running.

What to do next

Enable Hybrid Calendar for users

Use this procedure to enable a small number of Webex users for Hybrid Calendar with Microsoft Exchange or Office 365.

See Ways to add and manage users in Control Hub for other methods, such as using a bulk CSV template or Active Directory synchronization through Cisco directory connector.

Before you begin

By default, users receive email notifications regarding the Hybrid Calendar, including a welcome email after you enable them. For steps to toggle off these User Email Notifications, see the Configure notifications for Hybrid Services help article.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Users.
3	Choose a specific user from the list, or use the search to narrow the list, and then click the row to open an overview of the user.
4	Click Edit, and then ensure that the user is assigned at least one paid service under Licensed Collaboration Services. Make necessary changes, and then click Save.
5	Click Calendar Service, toggle on Calendar, choose Microsoft Exchange, and then save your changes. After you activate the service, the user status changes from Pending Activation to Activated. The length of time for this change depends on the number of users that you're enabling for the service. If email notifications are enabled, users receive a message indicating that the feature is enabled.

Add Hybrid Calendar to workspaces with Board, Desk, and Room Series

Before you begin

This task assumes that you've already created places for the Board, Desk, and Room devices. If you need to create the workspace, see Add shared devices and services to a workspace.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Workspaces and select the workspace to modify.
3	Go to Scheduling and select Calendar so that users can use One Button to Push (OBTP) on their devices.
4	Select the calendar provider.
5	Enter the email address of the room mailbox. (For help locating this email address, see " Create and manage room mailboxes" on the Microsoft Docs website.) This is the email address that will be used to schedule meetings.
6	Click Save.

Associate user's Personal Rooms with Webex

The users on your Webex site have been Webex App linked. (For site linking steps, see Link Webex sites to Control Hub.)
Users change their own preferred Webex site from the Webex App settings or preferences, see Change your default meeting site
For a comprehensive approach, use the bulk CSV import process from Control Hub to set users’ preferredWebExSite in the steps that follow.

1	Sign in to the customer view in https://admin.webex.com.
2	In the left-hand navigation pane, under Management click Users.
3	Click Manage Users.
4	See this article for the detailed CSV import/export procedure.
5	Use a CSV editor to change the `preferredWebExSite` attribute for all or some users.
6	Import the CSV file.

Test join button with room devices

Use these steps to set up a test meeting and verify OBTP on a registered device.

To test a Webex team meeting in Exchange or Office 365:

In Outlook, Outlook Web Access, or https://mail.office365.com, create a new meeting, and then add a keyword such as @webex:space or @meet to the Location field.
Go to the Scheduling Assistant and click Add room, and choose the device you want to add.
Fill out other meeting information as needed, and send the invitation.
When the meeting is scheduled to begin, verify that the Join button appears on the device.

To test a Personal Room meeting in Exchange or Office 365:

In Outlook, Outlook Web Access, or https://mail.office365.com, create a new meeting, and then add @webex (or the scheduler's Personal Room URL) to the Location field.
Go to the Scheduling Assistant and click Add room, and choose the device you want to add.
Fill out other meeting information as needed, and send the invitation.
When the meeting is scheduled to begin, verify that the Join button appears on the device.

What to do next

Introduce the calendar features to your users

Follow these articles to help users learn about the Hybrid Calendar scheduling and out of office features:

Deploy Hybrid Calendar with Office 365

Hybrid Calendar with Office 365 deployment task flow

To deploy Hybrid Calendar with your Office 365 environment, perform the following tasks.

Before you begin

Prepare your environment

1	Register Expressway-C connector hosts to Cloud Add the Hybrid Calendar to your organization and connect your Expressway to the Webex cloud. This creates a resource in https://admin.webex.com and downloads connector software on to the Expressway.
2	(Optional) Append the Exchange CA certificate to the Expressway trusted CA list If you want Microsoft Exchange Web Services (EWS) traffic to be encrypted, make sure the Expressway trust list contains the certificate of the CA that signed the Exchange Server certificate.
3	Link Calendar Connector to Office 365 Configure Exchange Servers for the calendar connector.
4	(Optional) Configure the Calendar Connector's Webex site settings If you have a Webex Meetings site, configure the @Webex functionality.
5	(Optional) Choose How the Hybrid Calendar Service Localizes Meeting Join Details To override how the calendar connector localizes meeting join details for your entire organization, set the Default Language setting in https://admin.webex.com.
6	(Optional) Configure @webex and @meet Keywords To change the action that the calendar connector takes when users enter @webex or @meet, set the Keywords settings in https://admin.webex.com.
7	(Optional) Customize Email Templates Choose what the Hybrid Calendar adds to meeting invitations, including audio or video join details and a localized header and footer in any language that the service supports.
8	Start the calendar connector
9	Enable Hybrid Calendar for users
10	(Optional) Add the Hybrid Calendar Service to Workspaces with Webex Room, Desk, and Board Devices If you want One Button to Push (OBTP) functionality to be provided to Webex room and desk devices and Webex Boards that are registered to the Webex cloud, configure places for the devices.
11	(Optional) Associate user's Personal Rooms with Webex For OBTP on Webex room and desk devices and Webex Boards, make sure that meeting schedulers have their Personal Rooms associated with their Webex App accounts.
12	Test join button with room devices If you configured OBTP in the previous step, test it with a device.

Register Expressway-C connector hosts to Cloud

Hybrid Services use software connectors hosted on Expressway-C to securely connect Webex to your organization's environment. Use this procedure to register Expressway-C resources to the cloud.

After you complete the registration steps, the connector software is automatically deployed on your on-premises Expressway-C.

Before you begin

Make sure your Expressway-C is running on a version that's supported for hybrid services. See the Supported Versions of Expressway for Cisco Webex Hybrid Services Connectors documentation ( https://help.webex.com/article/ruyceab) for more information about which versions are supported for new and existing registrations to the cloud.
Sign out of any open connections to the Expressway-C interface that are open in other browser tabs.
If your on-premises environment proxies the outbound traffic, you must first enter the details of the proxy server on Applications > Hybrid Services > Connector Proxy before you complete this procedure. Doing so is necessary for successful registration.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid and then choose one: If this is the first connector host you're registering, click Set up on the card for the hybrid service you're deploying, and then click Next. If you've already registered one or more connector hosts, click View all on the card for the hybrid service you're deploying, and then click Add Resource. The Webex cloud rejects any attempt at registration from the Expressway web interface. You must first register your Expressway through Control Hub, because the Control Hub needs to hand out a token to the Expressway to establish trust between premises and cloud, and complete the secure registration.
3	Choose a method to register the Expressway-C: New Expressways—choose Register a new Expressway with its Fully Qualified Domain Name (FQDN), enter your Expressway-C IP address or fully qualified domain name (FQDN) so that Webex creates a record of that Expressway-C and establishes trust, and then click Next. You can also enter a display name to identify the resource in Control Hub. To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Expressway-C. Capitalization is not supported at this time. Existing Expressways—choose Select an existing Expressway cluster to add resources to this service, and then choose the node or cluster from the drop-down that you previously registered. You can use it to run more than one hybrid service. If you're registering a cluster, register the primary peer. You don't need to register any other peers, because they register automatically when the primary registers. If you start with one node set up as a primary, subsequent additions do not require a system reboot.
4	Click Next, and for new registrations, click the link to open your Expressway-C. You can then sign in to load the Connector Management window.
5	Decide how you want to update the Expressway-C trust list: A check box on the welcome page determines whether you will manually append the required CA certificates to the Expressway-C trust list, or whether you allow Webex to add those certificates for you. Choose one of the following options: Check the box if you want Webex to add the required CA certificates to the Expressway-C trust list. When you register, the root certificates for the authorities that signed the Webex cloud certificates are installed automatically on the Expressway-C. This means that the Expressway-C should automatically trust the certificates and be able to set up the secure connection. If you change your mind, you can use the Connector Management window to remove the Webex cloud CA root certificates and manually install root certificates. Uncheck the box if you want to manually update the Expressway-C trust list. See the Expressway-C online help for the procedure. When you register, you will get certificate trust errors if the trust list does not currently have the correct CA certificates. See Certificate Authorities for Hybrid Services.
6	Click Register. After you're redirected to Control Hub, read the on-screen text to confirm that Webex identified the correct Expressway-C.
7	After you verify the information, click Allow to register the Expressway-C for Hybrid Services. Registration can take up to 5 minutes depending on the configuration of the Expressway and whether it's a first-time registration. After the Expressway-C registers successfully, the Hybrid Services window on the Expressway-C shows the connectors downloading and installing. The management connector automatically upgrades itself if there is a newer version available, and then installs any other connectors that you selected for the Expressway-C connector host. Each connector installs the interface pages that you need to configure and activate that connector. This process can take a few minutes. When the connectors are installed, you can see new menu items on the Applications > Hybrid Services menu on your Expressway-C connector host. If registration fails and your on-premises environment proxies the outbound traffic, review the Before You Begin section of this procedure. If the registration process times out or fails (for example, you must fix certificate errors or enter proxy details), you can restart registration in Control Hub.

Append the Exchange CA certificate to the Expressway trusted CA list

If you're using a custom domain, make sure that you add the CA certificate for the domain certificate issuer to the Expressways.

Before you begin

You must import certificates to each Expressway-C.

1	On the Expressway-C connector host, go to Maintenance > Security certificates > Trusted CA certificate.
2	Review the CA certificates in the trust list to check if the correct CA certificate is already trusted.
3	To append any new CA certificates: Click Browse (or the equivalent in your browser) to locate and select the PEM file. Click Append CA certificate. The newly appended CA certificate appears in the list of CA certificates.
4	To replace an existing CA certificate with an updated one, for a particular issuer and subject: Check the check box next to the Issuer details. Click Delete. Append the replacement certificate as described above.

Certificate Authorities for Hybrid Services in an Office 365 Environment

The table lists the Certificate Authorities that your existing environment must trust when using Hybrid Services.

If you opted to have Webex manage the required certificates, then you do not need to manually append CA certificates to the Expressway-C trust list.

Cloud hosts signed by this CA	Issuing CA	Must be trusted by	For this purpose
CDN	`O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root`	Expressway-C	To ensure Expressway downloads connectors from a trusted host
Common Identity (CI) service	`O=VeriSign, Inc., OU=Class 3 Public Primary Certification Authority`	Windows Server 2003 or Windows Server 2008 hosting the Cisco directory connector Expressway-C	To synchronize users from your Active Directory with Webex and to authenticate Hybrid Services users
Webex App	`O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority`	Expressway-C
Office 365 cloud	`O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root`	Expressway-C	Office 365 support
Office 365 cloud	`O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root CA, C=US`	Expressway-C	Office 365 support

Related Information

Supported Certificate Authorities for Cisco Spark

Link Calendar Connector to Office 365

The calendar connector installs automatically after you register your Expressway for Hybrid Services. The connector does not start automatically, and requires some configuration to link to your calendar environment.

1	From the Expressway-C connector host, go to Applications > Hybrid Services > Calendar Service > Microsoft Exchange Configuration, and then click New. Make sure you choose Microsoft Exchange Configuration, not Cisco Conferencing Services Configuration. You cannot configure the Calendar Connector for Microsoft Exchange or Office 365 in the same organization with the conferencing services (integration with Cisco TelePresence Management Suite).
2	Enter the credentials of the service account that you want the calendar connector to use to connect to Exchange. The service account queries calendars on behalf of your users, using the impersonation role. You can use these formats: `username@domain.com`—The userPrincipalName. Typically, this value matches the user's primary email address, but the properties are separate. userPrincipalName consists of the User Logon Name (not always the same as sAMAccountName) and the UPN suffix, which is based on the Active Directory domain (not always the same as the NetBIOS domain). `DOMAIN\username`—DOMAIN is the NetBIOS domain (the pre-Windows 2000 domain); "username" is the sAMAccountName (the legacy username or pre-Windows 2000 username). If you're unsure about what to use for these formats, use Active Directory Users and Computers on a Windows machine to view the Account tab of the Properties pane for the user in question. The correct values to use are displayed as: User logon name for the first format. User logon name (pre-Windows 2000) for the second format.
3	Enter a unique Display Name for this Exchange Server.
4	For the Type, select Office365.
5	For Need Proxy for Connection?, select Yes if https access goes through a web proxy to your Exchange environment.
6	For Enable this Exchange server?, select Yes. You can select No for debugging purposes, but users will not be subscribed to this Exchange.
7	Check Basic for the Authentication Type. For Hybrid Exchange (on-premises and Office 365) deployments, you can check both NTLM and Basic authentication types. If one method fails, then the other method is used.
8	Leave TLS Verify Mode as the default value On so that this Expressway-C verifies the certificate presented by the Exchange Server. You may need to update the trust stores on both servers to ensure that each one trusts the CA that signed the other's certificate.
9	Enter an Email Address so that calendar connector can test the connection and check that the directory query worked. Use the email address of a user that you will enable for the Hybrid Calendar Service, as it appears in Control Hub. If the test fails, then your settings are not saved. If you omit the mailbox name, then your settings are saved without verifying connectivity.
10	To manually configure any Autodiscover redirect URLs that the Calendar Connector should trust, click Configure Trust List. Once you click Add, the Calendar Connector automatically populates any missing Autodiscover redirect URLs that it finds while contacting the Autodiscover service. URLs from unauthenticated sources are placed in pending state, and blocked unless you choose to allow them. If you skip this step now, you can still manually add URLs later, or explicitly accept or deny the pending URLs.
11	Click Add to store the Exchange Server configuration on the Expressway-C. The calendar connector tests the connection to the Exchange environment.

Configure the Calendar Connector's Webex site settings

Before you begin

For the @webex functionality to work for users, verify the following:
- You have at least one Webex Meetings site, with the Personal Room feature enabled for the site and for the individual users.
- The email address in each user's Webex account matches the user's Exchange email address and Webex App login address. If it does not, users must set up their Personal Room in the Webex app.
Gather the Webex user account email address of a valid user on your site. The calendar connector uses this account to access the Webex Personal Room details for users who schedule meetings with @webex.

1	From the Expressway-C connector host, go to Applications > Hybrid Services > Calendar Service > Cisco Conferencing Services Configuration, and then click New.
2	Select Type as Webex under Conferencing Services Type.
3	Enter the Fully Qualified Site Name for this Webex Meetings site. If your site is accessed as example-co.webex.com, you'd enter example-co.webex.com.
4	Enter a valid Webex user account email address, leave the password field blank, and then click Test Connection to validate the site information that you entered. If testing the connection fails, you can save the configuration with both the user name and password fields blank.
5	Indicate whether or not this site is the default. The default site is used for @webex unless the user has a different site configured in their My Personal Room setting in the Webex App app (either because the user's Webex site has been linked to Control Hub by an administrator, or because the user configured the setting with a different site).
6	Click Save to save the configuration.

Choose How the Hybrid Calendar Service Localizes Meeting Join Details

In Control Hub, the Default Language setting controls the language of the join details that the Hybrid Calendar adds to invitations. If you leave the setting at its default, the service uses the language from the item.Culture property of each meeting invitation. (Typically, the scheduler's operating system controls the value of item.Culture.)

To override choosing languages on a meeting-by-meeting basis from item.Culture, choose a specific language to use for join details for all meetings across your organization.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for Exchange, click Edit settings.
4	In the Meeting Invitations section, choose a language from the Default Language drop-down list, and click Save. After you save the change, the Hybrid Calendar uses the language you choose each time it adds join to details a meeting. It doesn’t change the language for existing join details.

Configure @webex and @meet Keywords

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Hybrid.
3	From the Hybrid Calendar card for your calendar environment, click Edit settings. If you have the Hybrid Calendar set up for multiple calendar environments, you can access the keywords settings from multiple pages in Control Hub, but the values that you set apply to all environments. The Hybrid Calendar (Microsoft 365) displays a list of tenants included in this organization.
4	Select the tenant to configure.
5	Click the Settings tab.
6	In the Keywords section, select the default action that you want for each keyword.
7	Click Save.

Customize Email Templates

Choose which meeting join details the calendar service includes in meeting invitations.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Services click Meeting > Settings.
3	Locate the Meeting Join Customization section.
4	Choose whether to show Join by Phone details. When you include the dial-in details, you can also choose to add a link to global call-in numbers, a link to toll-free calling restrictions, or both.
5	Show or hide details on joining from an application or video conferencing device. When you include the video dialing details, you can also choose to include an IVR IP address, a Skype for Business join link, or both.
6	Click Add a Language and then select the language from the drop-down menu to create a custom header and footer for any of the languages that the Hybrid Calendar Service supports. When you've got the header and footer text that you want, click Save. The header and footer values have a maximum of 1024 characters each (including spaces).
7	Once you've added a custom header and footer for a language, you can choose that language as a default for any other language that doesn't have a custom header and footer defined. Your default language choice saves automatically.

Start the calendar connector

1	From Expressway, go to Applications > Hybrid Services > Connector Management. The Connector management section of the page has a list of connectors and the status of each. The Management Connector is Running and the Calendar Connector is Not enabled.
2	Click Calendar Connector.
3	Select Enabled from the Active drop-down list.
4	Click Save. The calendar connector starts and the status changes to Running.

What to do next

Enable Hybrid Calendar for users

Use this procedure to enable a small number of Webex users for Hybrid Calendar with Microsoft Exchange or Office 365.

See Ways to add and manage users in Control Hub for other methods, such as using a bulk CSV template or Active Directory synchronization through Cisco directory connector.

Before you begin

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Users.
3	Choose a specific user from the list, or use the search to narrow the list, and then click the row to open an overview of the user.
4	Click Edit, and then ensure that the user is assigned at least one paid service under Licensed Collaboration Services. Make necessary changes, and then click Save.
5	Click Calendar Service, toggle on Calendar, choose Microsoft Exchange, and then save your changes. After you activate the service, the user status changes from Pending Activation to Activated. The length of time for this change depends on the number of users that you're enabling for the service. If email notifications are enabled, users receive a message indicating that the feature is enabled.

Add the Hybrid Calendar Service to Workspaces with Webex Room, Desk, and Board Devices

Before you begin

This task assumes that you've already created places for the Board, Desk, and Room devices. If you need to create the workspace, see Add shared devices and services to a workspace.

1	Sign in to the customer view of https://admin.webex.com/login.
2	In the left-hand navigation pane, under Management click Workspaces and select the workspace to modify.
3	Go to Scheduling and select Calendar so that users can use One Button to Push (OBTP) on their devices.
4	Select the calendar provider.
5	Enter the email address of the room mailbox. (For help locating this email address, see " Create and manage room mailboxes" on the Microsoft Docs website.) This is the email address that will be used to schedule meetings.
6	Click Save.

Deploy the Expressway calendar connector for a Hybrid Exchange environment

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.

Before you begin

Prepare your environment.
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.

1	Deploy Expressway Calendar Connector for Microsoft Exchange by adding an Exchange configuration to Expressway. You must enable and configure auto discovery when you add the configuration—Select Use Active Directory to enable auto discovery. We do not support manually entered Exchange addresses in Exchange hybrid environments. For the authentication type, you should check both NTLM and Basic authentication types. If one method fails, then the other method is used.
2	Enable Hybrid Calendar for users who have mailboxes in on-premises Exchange.
3	Start calendar connector and ensure that the activated users are subscribed.
4	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 Webex App space for an activated user.
5	Stop the calendar connector. Do not proceed until you see that it fully stopped.
6	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.
7	Enable Hybrid Calendar for users who have mailboxes in Office 365.
8	Start calendar connector and ensure that activated users in both on-premises and Office 365 are subscribed.
9	As a test, in an Outlook invitation, add a space scheduling keyword to the Location field; verify that this step creates a Webex App 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.

Related Information

Schedule a Webex meeting from your calendar

Thanks for your feedback.

Deployment guide for Hybrid Calendar

Architecture: Office 365 with cloud-based Hybrid Calendar

Cloud-based Hybrid Calendar with Office 365: Scheduling flow

Prepare your environment

How the Hybrid Calendar accesses user calendars

Deploying alongside an existing Expressway-based Calendar Connector

Change processing timeframes

Requirements for Hybrid Calendar with Microsoft Office 365

Deploy cloud-based Hybrid Calendar with Office 365

Hybrid Calendar with Office 365 deployment task flow

Prepare your Webex Meetings site

Enable and configure Hybrid Calendar with Microsoft 365

Add an additional tenant to Hybrid Calendar with Office 365

Modify a tenant of Hybrid Calendar with Office 365

Choose how Hybrid Calendar localizes meeting join details

Configure @webex and @meet keywords

Customize email templates

Enable Hybrid Calendar with Office 365 for users

Add Hybrid Calendar to workspaces with Board, Desk, and Room series

Associate Webex personal rooms with Webex App

Test the Office 365 and Hybrid Calendar integration

Move a user from an Expressway-based connector

Architecture: Google Calendar with cloud-based Hybrid Calendar

Hybrid Calendar with Google Calendar: Scheduling flow

Prepare your environment

Requirements for Hybrid Calendar Service With Google Calendar

Remove Google Hangouts information in meeting events

Deploy Hybrid Calendar with Google Calendar

Hybrid Calendar with Google Calendar deployment task flow

Enable and configure Hybrid Calendar with Google Calendar

Localize meeting join details

Configure @webex and @meet keywords

Customize email templates

Enable the Hybrid Calendar with Google for users

Add Hybrid Calendar to workspaces with Board, Desk, and Room series

Associate personal rooms with Webex App

Test the Google Calendar and Hybrid Calendar integration

Architecture: Expressway calendar connector

Expressway-based Calendar Connector for Microsoft Exchange and Office 365: Architecture

One Button to Push Topologies with the Calendar Connector

Office 365 and hybrid Exchange environments

Prepare your environment

Management connector

Calendar connector

Calendar connector or cloud-based for Office 365 Users

Requirements for Hybrid Calendar

Set Up an impersonation account for on-premises Microsoft Exchange

Set up an impersonation account for Office 365

Complete the prerequisites for Hybrid Calendar

Complete the Expressway-C connector host prerequisites for Hybrid Services

Configure Hybrid Calendar book version

Hybrid Calendar with Exchange deployment task flow

Configure a throttling policy for impersonation account

Register Expressway-C connector hosts to Cloud

Append the Exchange CA certificate to the Expressway trusted CA list

Certificate Authorities for Hybrid Services

Link the calendar connector to Microsoft Exchange

Configure the Calendar Connector's Webex site settings

Choose how Hybrid Calendar localizes meeting join details

Configure @webex and @meet keywords

Customize Email Templates

Start the calendar connector

Enable Hybrid Calendar for users

Add Hybrid Calendar to workspaces with Board, Desk, and Room Series

Associate user's Personal Rooms with Webex

Test join button with room devices

Deploy Hybrid Calendar with Office 365

Hybrid Calendar with Office 365 deployment task flow

Register Expressway-C connector hosts to Cloud

Append the Exchange CA certificate to the Expressway trusted CA list

Certificate Authorities for Hybrid Services in an Office 365 Environment

Link Calendar Connector to Office 365

Configure the Calendar Connector's Webex site settings

Choose How the Hybrid Calendar Service Localizes Meeting Join Details

Configure @webex and @meet Keywords

Customize Email Templates

Start the calendar connector

Enable Hybrid Calendar for users

Add the Hybrid Calendar Service to Workspaces with Webex Room, Desk, and Board Devices