In this step, we’ll configure the synctool so it can connect both to Microsoft Entra ID (previously called Azure AD) and the Workspace.

All the data you have collected in the first two steps can be filled in the configuration UI tool. You can find this tool in the downloaded Workspace 365 synctool folder. When you unzip the folder, the name of the file is: ​

To disable the welcome page, uncheck checkbox at the bottom of the page. You can change the default language to Nederlands or English. Click Next to continue.

To connect the Azure AD synctool to Microsoft Entra ID, fill in the fields below. Click Next when all information is entered. Here, the connection to the entered information/Microsoft Entra ID will be validated.

To add a new environment, fill in the following and click on 'Save' when you're done:

Your Workspace site URL: this is the workspace base URL where all the environments are hosted on, mostly 'https://{companyname}.workspace365.net'.

Environment name: this must match exactly with the environment name in Workspace 365 and can be retrieved from the Workspace 365 URL, e.g. 'https://portal.workspace365.net/john -> john'.

Sync API authentication token: this must match with the Workspace 365 environment 'Users & groups' > 'User provisioning' > API key (step 2). ​
​

Accidently included the wrong group and/or domain in filtering? No worries! You may follow these steps:

The corresponding users will then be automatically removed and won't be able to sign into Workspace. The removed users will be present under the "deleted users" list under 'User Management' and will be removed permanently after 30 days (of course these users will not be deleted from Microsoft 365!).

Changed your mind or want to add to a specific group and/or domain? Follow these steps:

The corresponding users will be now be added to the Workspace environment.

You can choose the desired filtering options. If you leave both unchecked, domain- and group filtering, it will sync all users and groups.

If you want to enable domain filtering, check the enable domain filtering checkbox. This will expand and show all domains and subdomains within the current domain.

You can make a selection of the desired domains you want to sync. All users with the domain prefix selected will be synced in this case:

Will not be synced:

If you want to enable group filtering, check the enable group filtering checkbox. This will expand and show all groups within this current domain.

We do not support nested groups.

Here you can make a selection of the desired groups you want to sync. All users within the selected group and the group itself will be synced in this case:

Will not be synced:

It is possible to combine both, domain- and group filtering, as shown below:
​

​

We have the following active directory structure:

If domain filtering is enabled and the following checked:

If group filtering is enabled and the following is checked:

The following users and groups will be synced:

Will not be synced:

Click on preferences to open the synchronization settings menu.

You can set the synchronization type to Periodical or Once a day. If you choose to set the synchronization type to 'Periodical' you need to define the interval in hours and/or minutes. If you choose to set the synchronization type to 'Once a day', you need to define at which time you want to run the sync.

Why do we have caching? Well, caching makes things much faster. Instead of syncing every user object from scratch, the Azure AD synctool will only check for changes, and only these changes will be handled by the synctool and written to the cache. The cache can be seen as the synctool's "memory". When you clear the synctool's cache, you basically clear the synctool's memory and thus the entire user history. Unfortunately you cannot look into the cache history.

When you make user changes like adding or removing users in Microsoft Entra ID, these changes are written to the synctool's cache. That is, when the sync from the User provisioning settings in Workspace is enabled.

But what happens when you disable the sync and make manual user changes in Workspace 365? For example, you removed a user in Workspace from a group that is being synchronized while the sync was disabled in Workspace. As a consequence, this user change will not be written to the cache. In other words, the cache still thinks the user exists in Workspace.

So, what happens when you made a mistake and want to re-add that same user? It doesn't matter if you also deleted the user from the deleted user list, the cache still thinks the user exists in Workspace and, as a consequence, the synctool will not sync the user.

Why do we want to avoid clearing the cache?

If users are not being updated or added to specific groups, clearing the cache may fix this issue. However, we have seen that clearing the cache may cause user discrepancies later on and it can take a long time to sync all user objects, especially in large environments, and is generally too resource-intensive.

So how can I fix user synchronization issues, without clearing the cache?

What do I need to take into account when I still want to clear the cache?

Do not clear the cache as first solution! If you clear the cache, please make sure you run the latest version of the Azure AD synctool. Please contact support when you're in doubt.

If groups are not being synced accordingly, try disabling filtering first and run a full sync before you clear the cache. When the sync is complete, you can enable filtering again and sync the selected groups.

How to clear the cache

Proceed to step 4.