Support FAQs | Cloud Synchronisation

This section covers how, during ‘rollover’, our processes could affect your Cloud Synchronisation with Google Workspace and Microsoft 365. Any processes which rely on the users being in the Cloud will fail to find the user until a successful sync with the respective Cloud Sync Tool (Azure AD Connect or Google Cloud Directory Sync). This may include licensing, calendars, Google Classroom, or Teams for Education.

General Advice

I use Azure AD Connect / Google Cloud Directory Sync (GCDS) – is there anything I need to do?

As part of the rollover process, we may be making a large number of changes to AD objects (e.g. creating new class/tutor/teacherOfStudent groups), and by default, your cloud synchronisation tool may have a limit on the number of changes it can make.  If so, you may receive synchronisation errors - you may find the links to documentation below helpful:

GCDS - https://support.google.com/a/topic/2679497?hl=en&ref_topic=4511280

Azure AD Connect - https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnectsync-feature-prevent-accidental-deletes

Any processes which rely on the users being in the Cloud may be affected by this until a successful sync with the respective Cloud[SW2] Sync Tool (Azure AD Connect or Google Cloud Directory Sync). This may include licensing, calendars, Google Classroom or Teams for Education.

 

New Users Processing

Read more about New Users here

 

My new users were created in Active Directory, when will they be licensed in Microsoft 365?

When we create the users in Active Directory, we need them to have been synchronised to Microsoft 365 before we can set the licenses for them. This is usually done by Azure AD Connect. In some cases, you may have an additional scheduled task which runs a couple of hours later, which will attempt to license the users. You can also re-run the scheduled task at any time.

If you use OU filtering, you may need to check that any new OUs for users are inside the scope.

Any processes which rely on the users being in Microsoft 365 will fail to find the user until a successful Azure AD Connect synchronisation.

 

My new users were created in Active Directory, when will they be shown in Google Workspace?

After the users are created in Active Directory, you will need to run a full synchronisation using Google Cloud Directory Sync (GCDS). Only after this full synchronisation will the users then be created in Google Workspace.

If you use OU filtering, you may need to check that any new OUs for users are inside the scope.

Any processes which rely on the users being in Google Workspace will fail to find the user until after a successful GCDS synchronisation.

 

Leavers Processing

Read more about Leavers here

 

Leavers are being processed, but what about the licenses they were using in Microsoft 365?

Depending on your Azure AD Connect configuration, and also whether we are moving your leavers to another OU in Active Directory, licenses may be stripped automatically. If you need licensing to be handled separately for leavers, please contact our support team.

Leavers are being processed, but what happens to their Google Workspace account?

Depending on your Google Cloud Directory Sync (GCDS) configuration, and whether we are moving your leavers to another OU in Active Directory, users may be suspended automatically. If a user is disabled in Active Directory, GCDS will usually suspend the account. If you do not want to automatically suspend Google Workspace accounts, there may be options we can suggest – for example, not moving the users. You can also change the GCDS settings for account suspension.

 

Copyright © 2021 SalamanderSoft Limited