Forum Discussion
Azure AD SCIM Validator is in General Availability (GA) Status
You can now validate the compatibility of your SCIM provisioning endpoint and Azure AD code base using our Azure AD SCIM Validator. This tool can be used by ISVs who want to build SCIM compatible ser...
Turns out the status code should be 201, but the validator doesn't indicate that's the problem
This feedback is noted Doogal Vincent_Drake_Cerberus and JameyAbdelnoorJameyAbdelnoor . We are working to address these, and I will share the individual updates.
owinoakelo , same issue as @Vincent_Drake_Cerberus with phone primary attribute being sent as random phone number string instead of boolean value.
I've run into the same issue with phonenumber[0].primary being sent as a string phone number, rather than a boolean.
Anyone found a workaround?- I think we put in a hardcoded True/False value as we have a built-in workaround for Microsoft sending text values for booleans. But that means we can't use schema discovery.
Alternatively, we removed that value from the schema; again, can't use discovery.
Hoping this gets fixed soon, it's a little frustrating.
