New developments in sapio365 sometimes require an update to the structure of Cosmos DB and a subsequent migration of your Cosmos DB data to the newer database version.

This warning may be a result of a corrupted local database or an absent one (new installation).

If you’re connected to Cosmos DB and you see 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 until compatibility between Cosmos DB and sapio365 is achieved.

You must be a global admin to trigger a migration of Cosmos DB data.

1 - Download the previous version of sapio365 to create a local database which can then be migrated upon updating sapio365. You can download it from one of the links below:

2 - Launch the downloaded sapio365 application. It may take a while to build the local database depending on the volume of RBAC data, shared Comments and User Activity Logs.

3 - Once it’s done, update the current instance of sapio365 or launch the updated sapio365 application (which originally resulted in the warning message). This will trigger the data migration.