for #3, not at this time. We are working with Microsoft to have them implement the Client Credential Oauth flow within their user provisioning app, but they have indicated that will be at least a quarter out before they can support this.
#4, no, the user is only placed into an inactive state if it is specifically dictated by the mapping. The default mapping uses the MS "softDelete" attribute to determine if a user should be placed into an inactive state. If the user is soft deleted in Azure AD, then they will be set to "inactive" in Genesys Cloud on the next sync operation. If that user is then hard deleted in Azure AD, they will be deleted in Genesys Cloud.
#5, if a user is synced into a group that has a role assigned to it, then the user will inherit that role by way of their group membership. If there user is removed from the group, then the role will be removed from the user. Note that this is no different than the behavior you would find if you manually added/removed the user from the group.
------------------------------
Richard Schott
Genesys - Employees
------------------------------
Original Message:
Sent: 11-06-2020 01:59
From: Christoph Otto
Subject: Azure Active Directory Questions
Hi,
(1) we set up a OAuth Token with the maximum time of 38880000 seconds. (2) No new sync takes place after the token has expired, but the users remain in their current status.
(3) that interests me too
(4) Not sure, not tested
(5) Not sure, not tested
------------------------------
Christoph Otto
------------------------------