We are provisioning users from Azure AD to Genesys Cloud via SCIM, but our custom attributes like ‘Employee Region’ and ‘Cost Center Code’ are not mapping correctly.
In our APAC deployment, the Azure AD custom extension attribute extension_abc123_region needs to land in the GC user profile field customAttributes.region. But the SCIM connector keeps silently dropping the value.
This is a known gap in the SCIM implementation across multiple CCaaS vendors.
In our RFP evaluations, NICE CXone supports custom SCIM attribute mapping natively through their admin console. Genesys Cloud requires you to build a custom Azure AD provisioning app with a manual attribute mapping table. Five9 doesn’t support SCIM at all and relies on CSV imports.
Hello! This is a classic question and I’ve helped many community members with this exact issue.
The Genesys Cloud SCIM endpoint (/api/v2/scim/v2/users) supports the urn:ietf:params:scim:schemas:extension:enterprise:2.0:User schema, but custom attributes must be mapped explicitly in the Azure AD Enterprise Application’s ‘Provisioning > Attribute Mappings’ blade. You cannot use the generic extension_ attributes - you must map them to the specific GC SCIM extension URN.
Does this SCIM mapping affect which Management Unit the user lands in for WFM scheduling?
We assign agents to Management Units based on their ‘Cost Center Code’. If that custom attribute isn’t syncing correctly from Azure AD, the agents end up in the wrong MU and their published schedules are completely wrong.
Pro tip! 
Test your SCIM mapping with a single user first before enabling bulk provisioning!
Create one test user in Azure AD with all your custom attributes populated. Trigger a manual provisioning cycle and verify every field lands correctly in GC before you turn on automatic sync for 500 users. Trust me, you do NOT want to debug attribute mapping with 500 angry agents wondering why their profiles are wrong! 
From a change management perspective, communicate the SCIM sync schedule to your agents.
Azure AD provisioning runs on a fixed cycle (typically every 40 minutes). If an agent’s department changes in HR, they won’t see it reflected in Genesys Cloud for up to 40 minutes. Set clear expectations so they don’t flood the help desk with ‘My profile is wrong’ tickets.