Unable to bring the employee id in the user details while doing the provisioning through EntraIssue Problem Statement being faced by customers: Few customers who are using Microsoft Entra, and Entra ID being a key component of the platform, are facing issues while communication with SN SCIM. SCIM user endpoints follows RFCs and if any schema being used, need to be enlisted in schemas attribute request payload. At the same time, Microsoft Entra ID does not declare all schemas used in the request within the schemas array, causing the request to fail.ReleaseNACauseTechnical Explanation from SN side: SCIM user endpoints follows RFCs and if any schema being used, need to be enlisted in schemas attribute request payload. At the same time, Microsoft Entra ID is not following RFC and hence inclusion non-mandatory. Not following RFC(non-inclusion of used schemas) will fail with error: "Extended attributes namespace urn:ietf:params:scim:schemas:extension:servicenow:custom:2.0:User must be included in the schemas attribute”.ResolutionMany customers using Microsoft Entra ID are facing issues with the SCIM connector and requesting support for this. Conclusion: Previous conversation with Microsoft suggests that Automated tooling to migrate customers from SOAP to SCIM is planned but is at least 12-18 months away. Until then customers provisioning from Entra ID to ServiceNow should be using the SOAP API connector.