If you have enabled Single Sign-on (SSO) with Devolutions Hub Business prior to January 9, 2023, it is not configured for Provisioning with Azure AD. To benefit from this feature, you must create a new configuration with Azure AD that will synchronize your desired User groups with Devolutions Hub Business.
Create an Enterprise Application in Azure AD and Change the OpenID Configuration
- Since you have already configured the Single Sign-on authentication, you will need to create a new enterprise application in Azure AD following the steps in Configure SSO Authentication with Microsoft Azure and edit the current OpenID configuration in Devolutions Hub Business.
- The provisioning feature with Azure AD has to be done within this new enterprise application.
- After the synchronization is done, verify that all your existing users are flagged as synced and that they are in their respective Azure User Groups. If some users are not flagged as synced, it means that they are not members of any Azure group that is part of the enterprise application in Azure.
To avoid any downtime during this new setup, you need to complete the configuration in Devolutions Hub Business. Once the new values are saved, the Microsoft authentication will change the enterprise application and should be seamless.
Replace Devolutions Hub Custom User Groups with Azure User Groups
Note that this task can be done whenever you have the opportunity, a group at a time.
If you have Devolutions Hub Custom User Groups, ensure that you have an Azure User Group that contains the same users.
Once the Azure groups correspond to the custom groups, you can start to replace those custom groups with the Azure groups wherever you assign them in System Permissions, Vault Permissions, and Folder/Entry Permissions.
Contact our support team at email@example.com if you need help.