Since Azure AD needs to be synced with your Visma Addo account, it may take some time from you made some changes in your Azure AD account before these changes take effect in your Visma Addo account. These can be changes in user rights or groups for a user. This article aims to explain about the different update intervals as well as rules in the interaction between Azure AD and Visma Addo.
To ensure that you get the best integration and the most smooth process with Azure AD, it is important that you who do the integration both have the role "administrator" in Visma Addo and that you have the role "Global Admin" in your company's Azure account , as otherwise an integration is not allowed.
The integration user that you are using to make the integration, should not be used for anything in Visma Addo and therefore we would strongly recommend that the integration user that you are using to make the integration is an admin user in Azure who is not associated with a person and who has been decided not to take it down.
The synchronization interval between Azure Ad and Visma Addo is set to occur every 1 hour after a user has logged in with Visma Addo. This means that if some changes are made to your Azure AD account, and a user logs in to Visma Addo with their Azure profile, this will start a synchronization between the platforms which can take up to an hour.
Once you have made some changes to Visma Addo in your Azure AD, it is therefore both important that an Azure user logs in, but that you wait one hour before the changes take effect.
These are all changes such as, change of rights, change of user group or deletion of users.
User and group synchronization
With the Sync interval in mind, you should also be aware that changes you make to your Visma Addo application in Azure Ad in connection with adding users and groups will only take effect according to the same sync rules as above.
Therefore, you may find that you create users and groups in Visma Addo, but that the people are not created in your Visma Addo account, nor are they associated with the right group.
In order for the people to join the group or have the right that you have selected in Azure AD, it therefore requires the user that you have made the change to, logs in.
the login will trigger the synchronization for the specific user and they will therefore be connected with the correct rights as well as in the correct group.