Hello Vignesh,
Right now, Genesys Cloud doesn't support using OAuth 2.0 Client Credentials Grant directly for SCIM provisioning with Entra ID. Even though Azure gives you that option, the Genesys SCIM endpoint is expecting a static bearer token instead, which is why you're running into errors like CredentialValidationUnavailable when trying to use OAuth directly.
The supported approach is to create an OAuth client in Genesys Cloud with the SCIM Integration role, generate an access token (usually via Postman), and then drop that into Azure as the "Secret Token." The token expiration issue you're seeing is real, but there is a way to make it much more manageable-you can set the token duration up to 450 days (38,880,000 seconds) when creating the OAuth client, as long as it only has the SCIM Integration role and nothing else assigned. That way, instead of constantly rotating tokens, you're really only dealing with it about once every 15 months.
Hope this helps!
------------------------------
Cameron
Online Community Manager/Moderator
------------------------------
Original Message:
Sent: 04-16-2026 02:36
From: Vignesh Mohan
Subject: Genesys Azure SCIM Provisioning
We are currently configuring a SCIM provisioning integration between Microsoft Entra ID (Azure AD) and Genesys Cloud.
Azure provides two authentication methods for configuring SCIM provisioning with Genesys Cloud:
- Bearer Authentication
- OAuth 2.0 Client Credentials Grant
We were able to successfully configure SCIM provisioning using the Bearer Authentication method with the supported user attributes. In this approach, we configured the Tenant URL and Secret Token generated via Postman, in accordance with the Genesys documentation: Configure Microsoft Entra ID for Genesys Cloud SCIM (Identity Management) View summary - Genesys Cloud Resource Center
Although the SCIM integration and attribute mapping between Azure and Genesys Cloud are initially successful, we are encountering an issue when the bearer token expires. Once the token expires, user synchronization between Azure and Genesys Cloud stops, requiring manual regeneration and reconfiguration of the token.
To address this limitation, we attempted to implement the second authentication option available in Azure: OAuth 2.0 Client Credentials Grant. For this method, the following values were provided in Azure:
- Tenant URL:
https://api.usw2.pure.cloud/api/v2/scim/v2 - Token Endpoint:
https://login.usw2.pure.cloud/oauth/token - Client Identifier
- Client Secret
However, when testing the connection in Azure using this method, the configuration fails with the following error:
Error Code: CredentialValidationUnavailable
At this stage, we are seeking guidance on the correct configuration for OAuth 2.0–based SCIM provisioning with Genesys Cloud, or clarification on whether OAuth 2.0 client credentials are currently supported for SCIM provisioning from Microsoft Entra ID.
#System/PlatformAdministration
#Telephony
#Other
------------------------------
Vignesh Mohan
------------------------------