Advance notice of end of support for Microsoft Exchange Web Services + Application Impersonation

Zoom strives to provide frictionless and secure video communications empowering people to accomplish more. In response to Microsoft’s announcement of the Retirement of RBAC Application Impersonation in Exchange Online planned for February, 2025, Zoom customers must plan to migrate any existing calendar integrations with O365 (Exchange Online) using Microsoft Exchange Web Services (EWS) + Application Impersonation to use Microsoft Graph API + Application Permissions instead.

This may affect a calendar integration for:

Calendar integrations with Exchange 2010 or greater on-premises are not affected by Microsoft’s announcement.  Calendar integrations with O365 that do not use Exchange Web Services + Application Impersonation are also not affected by Microsoft’s announcement.  However, if your calendar integration with O365 is configured to use Exchange Web Services + Full Delegate Access, Zoom still recommends you consider migration ahead of Microsoft’s eventual full retirement of Exchange Web Services planned for October, 2026.

This article covers:

Background

Zoom offers calendar integration for Zoom Rooms, Workspace Reservation and Cisco/Polycom Rooms managed by Zoom Enhanced API Connector.

Many Zoom customers elect to configure calendar integration for one or more of these services to make it easy for end users to schedule meetings and/or workspace reservations with conference rooms, workspace desks, etc.

In particular, many customers elected to configure their Zoom calendar integration(s) with Microsoft Office 365 (aka “Exchange Online”) to use Exchange Web Services (EWS) with Application Impersonation (aka “App-level Impersonation”) due to the ease of initial configuration and the potential reduced additional configuration for new calendar resources.

In February, 2024, Microsoft announced the Retirement of RBAC Application Impersonation in Exchange Online.  This Microsoft retirement affects any Zoom calendar integration with O365 (Exchange Online) that uses Exchange Web Services + Application Impersonation.  Currently configured integrations will stop functioning when Microsoft completes their retirement planned for February, 2025.

Starting from March, 2024 Zoom offered an alternative style of integration using Microsoft Graph API + Application Permissions that provides equivalent features and functionality.  Zoom recommends migrating your calendar integrations to use Microsoft Graph API + Application Permissions.  For many customers, migration is simple and straightforward.  Like EWS + Application Impersonation, calendar integration with Microsoft Graph API + Application Permissions is easy to initially configure and requires little additional configuration for new calendar resources added in the future in most cases.

How can I check if my calendar integration is affected?

Customers may verify whether a calendar integration with O365 uses Microsoft Exchange Web Services + Application Impersonation by following the steps in the relevant section(s) below.

For Zoom Rooms and/or Workspace Reservation

Zoom Rooms and Workspace Reservation share calendar integrations.  It is not necessary to check both Zoom Rooms and Workspace Reservation separately.

  1. Sign in to the Zoom web portal.
  2. Click Room Management then Calendar Integration.
    1. If you only have Workspace Reservation services Room Management will not be an available menu.  Instead, click Workspaces Management then Calendar Integration.
  3. In the table in the section External Calendar Service note each calendar service row of any of the following types:
    1. Office 365
    2. Office 365 global services
    3. Office 365 operated by 21Vianet
    4. Office 365 Government Community Cloud (GCC) High
  4. For the first calendar service with one of the above types, note the data in the Calendar Resources column for this row, specifically the number of assigned resources.
    1. The Calendar Resources data is formatted as X total, Y assigned - for example, 33 total, 30 assigned.  The value to note is the Y assigned quantity - in the example that is 30 assigned.
  5. At the end of this row, click the Reauthorize button.  NOTE: do not complete the Authorize action at this time.
  6. In the Edit the calendar service page that appears, first confirm that Exchange Web Services (EWS) is selected.  If yes, proceed.  If no, this calendar service is unaffected and you may proceed to step 8.
  7. Next, in the section Account Permission Type note whether App-level Impersonation or Full Delegate Access is selected.  If App-level Impersonation is selected, the calendar service is affected and must be migrated.  If Full Delegate Access is selected, no change is required at this time.
  8. Click Cancel to return to the list of calendar integrations.
  9. Repeat steps 4-8 for each calendar service.
  10. If you reviewed the calendar services found in Room Management then Calendar Integration, it is not necessary to review calendar services in Workspaces Management then Calendar Integration.  Zoom Rooms and Workspace Reservation share calendar integrations.

Proceed on to check calendar services for Cisco/Polycom Rooms managed by Enhanced API Connector, which are configured separately.  If you have no Cisco/Polycom Rooms managed by Enhanced API Connector, or do not use calendar integration for Cisco/Polycom Rooms managed by Enhanced API Connector, proceed on to How to migrate to Microsoft Graph API + Application Permissions.

For Cisco/Polycom Rooms managed by Enhanced API Connector

  1. Sign in to the Zoom web portal.
  2. Click Room Management then Cisco/Polycom Rooms.
    1. If this menu is not available, you have no Cisco/Polycom Rooms and may skip the remaining steps.
  3. At the top, click Calendar Integration.
  4. In the table note each calendar service row of any of the following types:
    1. Office 365
    2. Office 365 global services
    3. Office 365 operated by 21Vianet
    4. Office 365 Government Community Cloud (GCC) High
  5. For the first calendar service with one of the above types, note the data in the Calendar Resources column for this row, specifically the number of assigned resources.
    1. The Calendar Resources data is formatted as X total, Y assigned - for example, 33 total, 30 assigned.  The value to note is the Y assigned quantity - in the example that is 30 assigned.
  6. At the end of this row, click the ... (ellipsis) button, then click the Reauthorize button.  NOTE: do not complete the Authorize action at this time.
  7. In the Edit the calendar service page that appears, first confirm that Exchange Web Services (EWS) is selected.  If yes, proceed.  If no, this calendar service is unaffected and you may proceed to step 9.
  8. Next, in the section Account Permission Type note whether App-level Impersonation or Full Delegate Access is selected.  If App-level Impersonation is selected, the calendar service is affected and must be migrated.  If Full Delegate Access is selected, no change is required at this time.
  9. Click Cancel to return to the list of calendar integrations.
  10. Repeat steps 5-9 for each calendar service.

Proceed on to How to migrate to Microsoft Graph API + Application Permissions.

How to migrate to Microsoft Graph API + Application Permissions

Prerequisites for migration to Microsoft Graph API + Application Permissions

Associated and verified domain preparation

As noted above, to set up a calendar integration with O365 using MS Graph API Application Permissions integration your Zoom account must have at least one associated domain that matches a custom domain you have verified in your O365 account.

Begin by discovering the custom domains you have verified in your O365 account.

  1. An O365 administrator must have at least the Domain Name Administrator privileged role in order to view the domains in an O365 account.  Several other O365 built-in roles, e.g. Global Administrator, also include the necessary permissions.  Involve your O365 administrator to complete these steps.
  2. Visit Microsoft Entra admin center.
  3. Login as an O365 administrator with the ability to view domains.
  4. Browse to Identity > Settings > Domain names.
    1. The Settings menu may be hidden by default - click Show more to expose it
  5. Note the listed domains that have the status Verified.

At least one (1) of these domains must match a Zoom account associated domain.

Next, discover the Zoom account associated domains, if any:

  1. Sign in to the Zoom web portal.
  2. Click Account Management then Account Profile.
  3. Scroll to the section Associated Domains.
  4. Note the domains, if any, that are listed with (Verified) status.
    1. If no domains are listed, you have no verified domains.

Then consider your next steps:

Determining the migration steps

Migration steps depend on the complexity and number of your current calendar integrations.

It’s important to remember that Zoom Rooms & Workspace Reservation share calendar integrations, but Cisco/Polycom Rooms managed by Enhanced API Connector are configured separately.  Both Zoom Rooms & Workspace Reservation and Cisco/Polycom Rooms managed by Enhanced API Connector can set up calendar integration with O365 using Microsoft Graph API + Application Permissions simultaneously.  However, both Zoom Rooms & Workspace Reservation and Cisco/Polycom Rooms managed by Enhanced API Connector may only have one (1) calendar integration using MS Graph API + Application Permissions to a particular O365 tenant.

If you determine your account has just one (1) affected calendar integration for Zoom Rooms and/or Workspace Reservation and/or just one (1) affected calendar integration for Cisco/Polycom Rooms managed by Enhanced API Connector, you may migrate directly to Microsoft Graph API + Application Permissions.  Consult these sections:

If you have multiple calendar integrations of either type, you will need to perform some consolidation after migration.  Depending on which kind of calendar integration has multiple affected instances, consult these sections:

Direct migration to Microsoft Graph API + Application Permissions for Zoom Rooms and/or Workspace Reservation

In most cases direct migration for Zoom Rooms & Workspace Reservation is very straightforward.  Zoom recommends performing the migration during a maintenance window, but there is no expected downtime when completing the migration.

If using Workspace Reservation, please ensure you follow these following steps to reauthorize the existing calendar service, as creating a may have impact on reservations.  

Preparation

As noted in the Prerequisites for migration to Microsoft Graph API + Application Permissions section, to set up a calendar integration with O365 using MS Graph API Application Permissions integration your Zoom account must have at least one (1) associated domain that matches a custom domain you have verified in your O365 account.

You cannot proceed until you have completed the steps in the Associated and verified domain preparation section and confirmed there is at least one (1) matching domain between your O365 account verified domains and your Zoom account associated domains.

You may also optionally apply Role Based Access Control for Applications in Exchange Online if you wish to restrict the calendar integration’s access to specific calendar resources (e.g. the calendar resources of your Zoom Rooms and/or Workspaces).  Take this action after you have completed the integration.

Performing the Migration

Note: Zoom recommends performing the migration during a pre scheduled maintenance window, but there is no expected downtime when completing the migration.

Follow these steps to perform the migration for Zoom Rooms & Workspace Reservation:

  1. Sign in to the Zoom web portal.
  2. Click Room Management then Calendar Integration.
    1. If you only have Workspace Reservation services Room Management will not be an available menu.  Instead, click Workspaces Management then Calendar Integration.
  3. In the table in the section External Calendar Service find the one (1) calendar service row with any of the following types:
    1. Office 365
    2. Office 365 global services
    3. Office 365 operated by 21Vianet
    4. Office 365 Government Community Cloud (GCC) High
  4. Click the Reauthorize button.
  5. In the Edit the calendar service page that appears, change the selector from Exchange Web Services (EWS) to Graph API.
  6. Next, in the section Account Permission Type confirm the selector is set to Application Permissions (it may already be selected).
  7. Click Authorize - you will be redirected to login to your Microsoft O365 account.  As noted in Prerequisites for migration to Microsoft Graph API + Application Permissions, you must login as a Microsoft O365 administrator with the Global Administrator or Cloud Application Administrator built-in role.
    1. As noted, Zoom does not recommend using a dedicated service account to login to your Microsoft O365 account to perform the Authorize step.
  8. After logging in, you will be presented with the permissions requested by the Zoom calendar integration using MS Graph API app permissions app. Click Accept to proceed.
    1. If you observe a page stating Need admin approval, consult the Troubleshooting section.
  9. You will be returned to the Zoom admin portal, and your calendar integration will begin using Microsoft Graph API + Application Permissions.
    1. If you observe an error message, consult the Troubleshooting section.

Your Zoom Rooms & Workspaces with calendar resources under this calendar service will now use Microsoft Graph API + Application Permissions.

You may also safely delete the O365 dedicated service account used by the affected calendar service you migrated to MS Graph API + Application Permissions at step 3, as this dedicated service account is no longer used after migrating to MS Graph API + Application Permissions.  Consult your O365 administrator to first confirm this dedicated service account is not used for any other purpose, and then to safely remove it.

Direct migration to Microsoft Graph API + Application Permissions for Cisco/Polycom Rooms managed by Enhanced API Connector

In most cases direct migration for Cisco/Polycom Rooms managed by Enhanced API Connector is very straightforward.  Zoom recommends performing the migration during a maintenance window, but there is no expected downtime when completing the migration.

Preparation

As noted in the Prerequisites for migration to Microsoft Graph API + Application Permissions section, to set up a calendar integration with O365 using MS Graph API Application Permissions integration your Zoom account must have at least one (1) associated domain that matches a custom domain you have verified in your O365 account.

You cannot proceed until you have completed the steps in the Associated and verified domain preparation section and confirmed there is at least one (1) matching domain between your O365 account verified domains and your Zoom account associated domains.

You may also optionally apply Role Based Access Control for Applications in Exchange Online if you wish to restrict the calendar integration’s access to specific calendar resources (e.g. the calendar resources of your Cisco Polycom Rooms managed by Enhanced API Connector).  Take this action after you have completed the integration.

Performing the Migration

Note: Zoom recommends performing the migration during a pre scheduled maintenance window, but there is no expected downtime when completing the migration.

Follow these steps to perform the migration for Zoom Rooms & Workspace Reservation:

  1. Sign in to the Zoom web portal.
  2. Click Room Management then Cisco/Polycom Rooms.
    1. If this menu is not available, you have no Cisco/Polycom Rooms and may skip the remaining steps.
  3. At the top, click Calendar Integration.
  4. In the table in the section External Calendar Service find the one (1) calendar service row with any of the following types:
    1. Office 365
    2. Office 365 global services
    3. Office 365 operated by 21Vianet
    4. Office 365 Government Community Cloud (GCC) High
  5. On the row of that calendar service, click the ... (ellipsis) button, then click the Reauthorize button. NOTE: do not complete the Authorize action at this time.
  6. In the Edit the calendar service page that appears, change the selector from Exchange Web Services (EWS) to Graph Api.
  7. Next, in the section Account Permission Type confirm the selector is set to Application Permissions (it may already be selected).
  8. Click Authorize - you will be redirected to login to your Microsoft O365 account.  As noted in Prerequisites for migration to Microsoft Graph API + Application Permissions, you must login as a Microsoft O365 administrator with the Global Administrator or Cloud Application Administrator built-in role.
    1. As noted, Zoom does not recommend using a dedicated service account to login to your Microsoft O365 account to perform the Authorize step.
  9. After logging in, you will be presented with the permissions requested by the Zoom calendar integration using MS Graph API app permissions app. Click Accept to proceed.
    1. If you observe a page stating Need admin approval, consult the Troubleshooting section.
  10. You will be returned to the Zoom admin portal, and your calendar integration will begin using Microsoft Graph API + Application Permissions.
    1. If you observe an error message, consult the Troubleshooting section.

Your Cisco/Polycom Rooms managed by Enhanced API Connector associated with calendar resources under this calendar service will now use Microsoft Graph API + Application Permissions.

You may also safely delete the O365 dedicated service account used by the affected calendar service you migrated to MS Graph API + Application Permissions at step 4, as this dedicated service account is no longer used after migrating to MS Graph API + Application Permissions.  Consult your O365 administrator to first confirm this dedicated service account is not used for any other purpose, and then to safely remove it.

Migrating when you have multiple affected Zoom Rooms and/or Workspace Reservation calendar integrations

Calendar integration for Zoom Rooms & Workspace Reservation supports multiple independent/separate calendar services with O365 using Exchange Web Services + Application Impersonation, so long as each integration uses a different dedicated service account.

Calendar integration with O365 using Microsoft Graph API + Application Permissions only supports a single unified integration.

Therefore, full migration to calendar integration with O365 using Microsoft Graph API + Application Permissions will require some consolidation.

Note: The steps below describe a method of manually performing consolidation by discovering calendar resources in affected calendar services and re-assigning them manually.  It is possible for an administrator with knowledge of how to export & import Zoom Rooms and Workspaces using CSV, or with knowledge of the Zoom Rooms and Workspaces REST API, to achieve the same objective by following steps 1-4, then using Zoom Rooms and Workspaces export/import via CSV or REST API capabilities to perform calendar resource reassignment.  These advanced methods are only recommended for administrators proficient in Zoom Rooms and Workspaces export/import with CSV or REST API capabilities.

To manually perform the consolidation, follow the steps below:

  1. Sign in to the Zoom web portal.
  2. Click Room Management then Calendar Integration.
    1. If you only have Workspace Reservation services Room Management will not be an available menu.  Instead, click Workspaces Management then Calendar Integration.
  3. In the table in the section External Calendar Service, observe all of your affected calendar services that you’ve already determined uses EWS + Application Impersonation and plan to migrate to Microsoft Graph API + Application Permissions.
    1. In the Calendar Resources column with the text X total, Y assigned, note the number of Y assigned resources for each affected calendar service.
    2. Calculate the sum of all Y assigned values for all the affected calendar services so you may validate your consolidation at step 10.
    3. Pick one (1) of your affected calendar services to migrate to Microsoft Graph API + Application Permissions first.  In order to reduce the effort required, Zoom recommends picking the affected calendar service that has the most Calendar Resources assigned.
  4. Follow the steps described in the Direct migration to Microsoft Graph API + Application Permissions for Zoom Rooms and/or Workspace Reservation section for the one (1) affected calendar service you will migrate first, as selected in step 3(c).
  5. For the first other affected calendar service listed in the section Existing Calendar Services (excluding the one just migrated), follow these steps:
    1. In the Calendar Resources column with the text X total, Y assigned, note the number of assigned resources.
    2. In the Calendar Resources column with the text X total, Y assigned, click the link to view the calendar resource assignments.
    3. For each listed calendar resource:
      1. Note the value of Calendar Resource, which is in the form of an email address.
      2. Note the value of Assigned To. If the Assigned To value for the calendar resource is Unassigned, no action is necessary.  If the Assigned To value for the calendar resource is Assigned to X the calendar resource is assigned to a particular Zoom Room or Workspace.  Note the Assigned To value, which is the name of a Zoom Room or Workspace.  You will modify the calendar service and calendar resource assignment later in the Zoom Rooms or Workspaces section of the web portal.
      3. If there are multiple pages of calendar resources, visit each page, repeating steps 5(c)(i) and 5(c)(ii).  You can adjust the page size to speed up the process, if desired.
  6. Repeat step 5 for each other affected calendar service listed in the section Existing Calendar Services (excluding the one just migrated).
  7. In the left-side navigation menu, under the Room Management section, click Zoom Rooms.
    1. If you only have Workspace Reservation services Room Management will not be an available menu.  Proceed to the next step to modify Workspaces.
    2. Starting with the first Zoom Room or Workspace name you collected in steps 5-6, perform the following steps:
      1. Using the search box under the list of Zoom Rooms (not the search box below the Location Directory), search for the name of the Zoom Room or Workspace.
      2. If that value is not found, it’s a Workspace.  Note it and proceed to step 7(c).
      3. If that value is found, click the Edit button for this Zoom Room.
      4. Scroll to the Calendar configuration setting
      5. Change the calendar service (first drop-down box) to the calendar service you migrated to MS Graph API + Application Permissions at step 4.
      6. Change the calendar resource (second drop-down box) to match the calendar resource (which is in the form of an email) you noted for this Zoom Room’s name at step 5(c)(i).
    3. Repeat step 7(b) for each Zoom Room or Workspace name you collected in steps 5-6.
  8. If you have Workspace services, in the left-side navigation menu, under the Workspaces Management section, click Workspaces.
    1. If you do not have Workspace Reservation services, Workspaces Management will not be an available menu.  You can skip step 8 entirely.
    2. In the Workspaces section on the right-side portion of the page, click the Workspaces sub-tab to view the list of all Workspaces.
    3. Starting with the first Workspace name you collected in steps 5-6 (which may be an item you skipped in step 7), perform the following steps:
      1. Using the search box under the list of Workspaces (not the search box below the Location Directory), search for the name of the Workspace.
      2. If that value is not found, you may have missed a Zoom Room in step 7.
      3. If that value is found, click the Edit button for this Workspace.
      4. Scroll to the Calendar configuration setting
      5. Change the calendar service (first drop-down box) to the calendar service you migrated to MS Graph API + Application Permissions at step 4.
      6. Change the calendar resource (second drop-down box) to match the calendar resource (which is in the form of an email) you noted for this Workspace’s name at step 5(c)(i).
    4. Repeat step 8(c) for each Workspace name you collected in steps 5-6, and skipped in step 7.
  9. Click Room Management then Calendar Integration.
    1. If you only have Workspace Reservation services Room Management will not be an available menu.  Instead, click Workspaces Management then Calendar Integration.
  10. In the table in the section External Calendar Service observe your affected calendar services and validate your work.
    1. Assuming you did not skip the migration of any Zoom Room step 7 and/or Workspace in step 8, the other affected calendar services you recorded at steps 5 and 6 should all show a value of X total, 0 assigned in the calendar resources column.
      1. If any affected calendar service still has a non-zero number of assigned calendar resources, review and migrate them as described in steps 5, 7 and 8.
    2. Assuming you did not skip the migration of any Zoom Room step 7 and/or Workspace in step 8, the affected calendar service you migrated to MS Graph API + Application Permissions at step 4 should now have a value of assigned calendar resources equal to the sum you calculated in step 3(a).
  11. You may now delete the other affected calendar services you recorded at steps 5 and 6, that now report 0 assigned calendar resources.  DO NOT delete the affected calendar service you migrated at step 4.
    1. You may safely delete the O365 dedicated service accounts used by the affected calendar services you recorded at steps 5 and 6, as these calendar services are no longer used.  Consult your O365 administrator to first confirm these dedicated service accounts are not used for any other purpose, and to safely remove them.
    2. You may also safely delete the O365 dedicated service account used by the affected calendar service you migrated to MS Graph API + Application Permissions at step 4, as this dedicated service account is no longer used after migrating to MS Graph API + Application Permissions.  Consult your O365 administrator to first confirm this dedicated service account is not used for any other purpose, and to safely remove it.

Your consolidation of Zoom Rooms & Workspaces is now complete.

Migrating when you have multiple affected Cisco/Polycom Rooms managed by Enhanced API Connector calendar integrations

Calendar integration for Cisco/Polycom Rooms managed by Enhanced API Connector supports multiple independent/separate calendar services with O365 using Exchange Web Services + Application Impersonation, so long as each integration uses a different dedicated service account.

Calendar integration with O365 using Microsoft Graph API + Application Permissions only supports a single unified integration.

Therefore, full migration to calendar integration with O365 using Microsoft Graph API + Application Permissions will require some consolidation.

Note: The steps below describe a method of manually performing consolidation by discovering calendar resources in affected calendar services and re-assigning them manually.  It is possible for an administrator with knowledge of how to export & import Cisco/Polycom Rooms managed by Enhanced API Connector using CSV to achieve the same objective by following steps 1-4, then using Cisco/Polycom Rooms managed by Enhanced API Connector export/import via CSV to perform calendar resource reassignment.  This advanced method is only recommended for administrators proficient in Cisco/Polycom Rooms managed by Enhanced API Connector export/import with CSV.

To manually perform the consolidation, follow the steps below:

  1. Sign in to the Zoom web portal.
  2. Click Room Management then Cisco/Polycom Rooms.
    1. If this menu is not available, you have no Cisco/Polycom Rooms and may skip the remaining steps.
  3. At the top, click Calendar Integration.
  4. In the table, observe all of your affected calendar services that you’ve already determined uses EWS + Application Impersonation and plan to migrate to Microsoft Graph API + Application Permissions.
    1. In the Calendar Resources column with the text X total, Y assigned, note the number of Y assigned resources for each affected calendar service.
    2. Calculate the sum of all Y assigned values for all the affected calendar services so you may validate your consolidation at step 11.
    3. Pick one (1) of your affected calendar services to migrate to Microsoft Graph API + Application Permissions first.  In order to reduce the effort required, Zoom recommends picking the affected calendar service that has the most Calendar Resources assigned.
  5. Follow the steps described in the Direct migration to Microsoft Graph API + Application Permissions for Cisco/Polycom Rooms managed by Enhanced API Connector section for the one (1) affected calendar service you will migrate first, as selected in step 4(c).
  6. For the first other affected calendar service listed in the section Existing Calendar Services (excluding the one just migrated), follow these steps:
    1. In the Calendar Resources column with the text X total, Y assigned, note the number of assigned resources.
    2. In the Calendar Resources column with the text X total, Y assigned, click the link to view the calendar resource assignments.
    3. For each listed calendar resource:
      1. Note the value of Calendar Resource, which is in the form of an email address
      2. Note the value of Assigned Room. If the Assigned Room value for the calendar resource is Unassigned, no action is necessary.  If the Assigned Room value for the calendar resource is Assigned to X rooms the calendar resource is assigned to one or more Cisco/Polycom Rooms.  You will modify the calendar service and calendar resource assignment later in the Cisco/Polycom Rooms section of the web portal.
      3. If there are multiple pages of calendar resources, visit each page, repeating steps 5(c)(i) and 5(c)(ii).  You can adjust the page size to speed up the process, if desired.
  7. Repeat step 6 for each other affected calendar service listed in the section Existing Calendar Services (excluding the one just migrated).
  8. In the left-side navigation menu, under the Room Management section, click Cisco/Polycom Rooms again.
    1. Starting with the first calendar resource email address you collected in steps 6-7, perform the following steps:
      1. View the list of Cisco/Polycom Rooms and find the Calendar Resource email address under the Calendars column.  If there are multiple pages of Cisco/Polycom Rooms, visit each page, looking for the Calendar Resource email address.  You can adjust the page size to speed up the process, if desired.
      2. When that value is found, click the Edit button for the associated Cisco/Polycom Room.
      3. Choose the Meeting tab
      4. Under the Calendar Resources setting click the X next to the calendar resource.
      5. In the modal that appears, click Remove to confirm.
      6. Under the Calendar Resources setting click the + to associate a new calendar resource.
      7. In the modal that appears, select the calendar service you migrated to MS Graph API + Application Permissions at step 5.
      8. From the list of available resources, select the calendar resource email address.  You may use the search function to help find the resource.
      9. Click Save.
    2. Repeat step 8(a) for each calendar resource email you collected in steps 6-7.
  9. In the left-side navigation menu, under the Room Management section, click Cisco/Polycom Rooms again.
  10. At the top, click Calendar Integration.
  11. In the table observe your affected calendar services and validate your work.
    1. Assuming you did not skip the migration of any calendar resource email in step 8, the other affected calendar services you recorded at steps 6 and 7 should all show a value of X total, 0 assigned in the calendar resources column.
      1. If any affected calendar service still has a non-zero number of assigned calendar resources, review and migrate them as described in steps 6 and 8.
    2. Assuming you did not skip the migration of any Cisco/Polycom Room at step 8, the affected calendar service you migrated to MS Graph API + Application Permissions at step 4 should now have a value of assigned calendar resources equal to the sum you calculated in step 4(a).

Your consolidation of Cisco/Polycom Rooms managed by Enhanced API Connector is now complete.

Troubleshooting

You clicked Authorize and logged into Microsoft O365, but observed a page stating Need admin approval.

This error indicates you logged into Microsoft O365 services as an administrator or user that does not have the Microsoft O365 Global Administrator or Cloud Application Administrator built-in role.  As noted in the Prerequisites for migration to Microsoft Graph API + Application Permissions, you must complete the Authorize step by logging into Microsoft O365 services as an administrator with the Microsoft O365 Global Administrator or Cloud Application Administrator built-in role in order to Accept the permissions requested by the Zoom calendar integration using MS Graph API app permissions app.

Please click the Have an admin account? Sign in with that account link in the page, then login as an O365 administrator account with the required built-in role.

Note: You may not even have been challenged to login to Microsoft O365, due to already being logged into O365, or having cached credentials.  To ensure you are challenged to login, you may use a browser in private or guest browsing mode to login to Zoom admin portal, then attempt to Authorize the calendar service again.

You clicked Accept when presented with the permissions requested by the Zoom calendar integration using MS Graph API app permissions app but observed the error message "The O365 account verified domains do not match any Zoom account associated domain" or "Zoom Associated domains do not match O365 verified domains when you return to the Zoom admin portal."

This error indicates that there is not at least one (1) matching domain between the set of O365 verified domains and the set of Zoom account associated domains. Review the instructions in the section Associated and verified domain preparation and attempt the migration again.