Microsoft Graph migration tool

Use the Microsoft Graph migration tool in the Robin web dashboard to migrate your Microsoft connection to Graph API.

Things to know before you start

  • Robin recommends that you migrate at an off-peak time to limit disruption. If you see errors, you can roll back the migration to your previous setup.
  • To migrate through the Enterprise app, you need a Microsoft Global admin, or a user with the Application Administrator & Privilege Role Administrator roles. You can limit the scopes with Role Based Access Control (RBAC).
  • For background, see the Migration FAQ.

Migration steps

  1. In the Robin web dashboard, go to the Manage > Integrations tab.
  2. Scroll down to workplace integrations and select Start Migration.

    Screenshot 2024-05-28 at 11.37.26 AM.png

  3. Select Migrate via App.

  4. The OAuth flow starts to connect to your account. If the migration does not start right away, you may need to do this step again. Review the permissions and select Accept.

    Screenshot 2025-01-16 at 1.47.29 PM.png

  5. The migration starts. It can take a few minutes, based on how many calendars you have. You can leave this page and come back later.

    Screenshot 2024-05-29 at 12.32.58 PM.png

  6. When the migration is complete, check for errors. See the common errors below.
  7. You can close this page and view the status at any time.

    Screenshot 2024-05-28 at 11.42.37 AM.png

  8. If the migration is successful, Robin recommends that you sign in as a different user to check that SSO and room booking work as expected.

Roll back the migration

If most or all of your calendars fail to migrate, Robin recommends that you roll back to your previous setup while you fix the errors. Roll back as soon as possible to keep your calendars in sync. A rollback loses any calendar changes made after the migration.

Screenshot 2024-05-29 at 12.30.34 PM.png

Common errors when migrating to Graph

If all calendars fail after you migrate, roll back and migrate again. In most cases, this fixes the problem. If most calendars migrate successfully, Robin recommends that you fix the individual errors and do not roll back.

Screenshot 2024-05-28 at 11.54.02 AM.png

Common reasons a calendar fails to migrate:

  • The calendar does not exist in Outlook.
  • If an application access policy limits the app's scope, the app might not have the scope it needs to access the calendars.

Screenshot 2024-05-28 at 11.53.11 AM.png

Skipped calendars

The migration skips room calendars that were in a bad state before the migration and have not synced successfully in the last 48 hours. Check that each calendar exists in Outlook.

Need admin approval message

If people see a “Need admin approval” message after they sign in, sign in with a Microsoft global admin account and consent on behalf of the organization.

Articles in this section

Was this article helpful?
1 out of 1 found this helpful
Share