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...

Provisioning

marhav

Copper Contributor

Oct 04, 2023

owinoakelo

Hello.
These days, I'm working on implementing support for the SCIM protocol into a client application and using the SCIM Validator to check its functionality. A few days ago, the SCIM Validator sent me a multi-value PATCH operation for nested parameters in this format:

 "Operations": [
        {
            "op":"replace",
            "value":
            {
                "name.givenName":"Aron",
                "name.familyName":"Raul",
            }
        }
    ]

Today, I noticed that instead of the original nine tests, a tenth one, "PATCH User- Disable User," has appeared, and the format of the patch replace operation has changed. Now, the multi-value operation for nested parameters looks like this:

"Operations": [
    {
      "op": "replace",
      "value": {
        "name": {
          "givenName": "Trevion",
          "familyName": "Larissa"
        },
      }
    }
  ]

Does an SCIM client that wants to collaborate with AAD need to support both the above-mentioned variations, or will the one from today be sufficient?

owinoakelo
Brass Contributor
Oct 04, 2023
marhav This is an issue on our end and an appropriate fix has been deployed and is rolling out now. Please support the one you received previously.

Forum Discussion

Azure AD SCIM Validator is in General Availability (GA) Status

Resources