The sync was not executed because the perform_sync parameter was not set or email report says that Cloud Sync ran in Preview Mode

Cause:

This means that Cloud Sync is still in Preview Mode, meaning that no accounts will get synchronized to Zivver. If the proposed changes look good, you can set Cloud Sync to make the changes.

Steps to resolve automated synchronizations:

1. Login to portal.azure.com
2. Type ZivverCloudSync in the top search bar and click the Automation Account
3. Type Runbooks in the left search bar and click this menu item
4. Open the runbook ZivverCloudSyncLoader
5. Search Schedules and open the ZivverCloudSyncSchedule
6. Verify that the schedule has parameter perform_sync
7. If this parameter is not present, click Unlink
8. Click Link a schedule
9. Select the schedule and add the parameter perform_sync

An error occurred while attempting to fetch SCIM Groups [401 Unauthorized]

Cause:

This means that Cloud Sync cannot connect to Zivver with the provided API key.

Steps to resolve:

1. Login to portal.azure.com
2. Type ZivverCloudSync in the top search bar and click the Automation Account
3. Type Variables in the left search bar and click this menu item
4. Open the variable CLOUD_SYNC__API_KEY and paste a correct API key
5. Click Save

Skipping account example@domain.nl because it is a group in one system and a user mailbox in the other

Cause:

Cloud Sync skips this account from synchronisation because there is a mismatch between the account type in Exchange Online and the account type in Zivver. An Exchange Online UserMailbox should correspond with a Zivver User account. An Exchange Online SharedMailbox should correspond with a Functional account in Zivver. You do not have to resolve this warning if there is a good reason for the mismatch (e.g. legacy configuration).

Steps to resolve:

1. Go to the Zivver accounts page as an administrator
   
2. Find the account mentioned in the warning log and click Manage
   
3. Change the account type

Failed to get EXO Mailboxes: The V1AppOnly token doesn’t contain the permissions required by the target API

Cause:

This means that the Managed Identity corresponding to the Automation Account does not have the required permissions

Steps to resolve:

1. Refer to 04. Frequently asked questions for instructions on how to check the permissions in the Azure portal
2. Refer to 02. Prerequisites and setup for instructions on how to assign the correct permissions

Failed to create user: Account is outside the organization

Cause:

This means this email address already exists outside of your Zivver organization.

Steps to resolve:

1. Go to the Domains page
2. Adopt free accounts

Failed to update user. Error creating alias: Alias is a guest

Refer to this documentation.

Account not found in SCIM IDs. Cannot update it.

Cause:

This means that Cloud Sync cannot perform an action on this account because it could not create this account earlier in the flow.

Steps to resolve:

1. Search for other warnings or errors in the log file related to this account
2. Resolve the corresponding errors

Failed to send email. Blocked by tenant configured AppOnly AccessPolicy Setting

Cause:

This means that the sender mailbox of the email report is not allowed to send email because of the permission policy.

Steps to resolve:

1. Refer to 02. Prerequisites and setup for instructions on how to set up a policy for the email report. Ensure that the sender mail address is equal to the mail address in the CLOUD_SYNC__EMAIL_REPORT_SENDER variable.

Failed to send email. Blocked by tenant configured AppOnly AccessPolicy Setting

Cause:

This means that the Mail.Send Graph API permissions are not properly set up for the Managed Identity.

Steps to resolve:

1. Refer to 02. Prerequisites and setup for instructions on how to set up Mail.Send Graph API permissions.
2. View the currently assigned API permissions by navigating in the Azure Portal to Enterprise Applications. Here you can filter on Managed Identities, select ZivverCloudSync and check if you see the Mail.Send permission under Permissions.

No email report will be sent out. CLOUD_SYNCEMAIL_REPORT_SENDER or CLOUD_SYNCEMAIL_REPORT_RECIPIENTS variables were not set

Cause:

This means that the email report was not sent because the sender and/or recipients were not properly specified.

Steps to resolve:

1. In the Azure Portal, navigate to the ZivverCloudSync Automation Account
2. Navigate to Variables
3. Check that the CLOUD_SYNC__EMAIL_REPORT_SENDER and CLOUD_SYNC__EMAIL_REPORT_RECIPIENTS exist and each contain at least one email address

Cloud Sync was halted due to large amount of changes threshold exceeded

Cause:

This means that the sync was not executed because more than 10 % of accounts were to be created, updated or suspended. This is a failsafe mechanism, to avoid making unintended large changes.

Steps to resolve:

1. In the Azure Portal, navigate to the ZivverCloudSync Automation Account
2. Navigate to Runbooks
3. Open the ZivverCloudSyncLoader runbook
4. Click Start
5. At parameters, submit the parameter allow_large_sync
6. Click OK