The following steps are a partial fix to unblock the Cosmos DB migration of the local RBAC configuration (and other shared data) to version 2.1.7 using the published hotfix.
If you have updated to version 2.1.7 and you are connected to Cosmos DB, and you are stuck seeing the following message upon (a) launch, or (b) in the RBAC and sapio365 Access & Restrictions sections, the steps that follow will fix the situation. For security reasons, sapio365 RBAC roles are unavailable for EVERYONE until compatibility between Cosmos DB and sapio365 is achieved.
You must be a Microsoft 365 global admin to trigger a migration of Cosmos DB data.
Make sure you are using an Advanced session.
If you have ‘Load last session’ setting in Preferences enabled:
If you do NOT have ‘Load last session’ setting enabled (i.e. no session at startup):
Once the Cosmos DB migration has been triggered by an global admin, users with RBAC roles will be able to unblock their role sessions in sapio365 by following the same steps above.