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 and Privileged Role Administrator roles. You can limit the scopes with Role Based Access Control (RBAC).
- For background, see the Migration FAQ.
Migrate to Graph API
Start the migration in Robin, then accept the permissions in Microsoft.
- In the Robin web dashboard, go to Manage > Integrations.
- In the Installed list, select Manage next to Microsoft 365. The Microsoft 365 page opens.
- In the Migrate M365 Integration card at the top of the page, select Start Migration.
- Select Migrate via App. 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.
- In the Microsoft Permissions requested window, review the permissions and select Accept. The migration starts.
- When the migration is complete, check for errors. See Common errors when migrating to Graph.
- 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.
The migration can take a few minutes, based on how many calendars you have. You can leave this page and come back later. The migration continues while you are away. To view the status at any time, select View migration status on the Microsoft 365 page.
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.
To roll back:
- Open the migration status and select Rollback Migration.
- Select Roll back to confirm.
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.
The migration status lists each calendar with its Calendar Address, Space Name and Status. A calendar that failed shows Error, and a skipped calendar shows Skipped.
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.
Skipped calendars
A calendar shows Skipped when it fails to migrate and was already out of sync before the migration. For example, it had not synced with Robin for more than 2 days. A skipped calendar is not on Graph API. To fix it:
- Check that the calendar exists in Outlook.
- Reconnect the calendar to its space in Robin. See Add a calendar to your space.
Need admin approval message
If people see a “Need admin approval” message after they sign in, consent on behalf of the organization:
- Sign in with a Microsoft global admin account.
- In the Microsoft permissions window, select Consent on behalf of your organization, then select Accept.