Error saving SCIM provisioning attribute list in Entra

Question

Error saving SCIM provisioning attribute list in Entra

Shree Varshan G 40

Screenshot 2025-12-27 205911

I am trying to edit the SCIM attribute list for my enterprise application in Entra. I have added custom attributes like:

urn:ietf:params:scim:schemas:extension:CustomFields:2.0:User:cf_time

urn:ietf:params:scim:schemas:extension:CustomFields:2.0:User:cf_droppy

urn:ietf:params:scim:schemas:extension:CustomFields:2.0:User:cf_checky

.......

Even after normalizing all field names to lowercase and underscores, and signing out/in, I keep encountering this error when clicking Save:

“We encountered an error while updating provisioning configuration for Saving attribute list”

I verified that all fields are unique and there are no duplicates.
The portal allows me to type the attributes, but does not save.
This happens consistently across browsers.

Can you help me understand why this error occurs and how to successfully save a custom SCIM attribute list? and how to solve this any thing i'm missing

Данило Кошнарьов 90 Reputation points

2025-12-27T21:13:55.5466667+00:00
The error occurs because Entra ID’s SCIM provisioning configuration does not accept arbitrary custom attribute URNs typed directly into the portal. The provisioning UI only supports attributes that are defined in the SCIM schema exposed by your target application’s /Schemas endpoint. If you manually add attributes that aren’t recognized by the app’s SCIM service, the portal will let you type them but will fail to save. You can’t just type custom SCIM attributes into Entra — they must exist in the target app’s SCIM schema. To fix this, extend your app’s SCIM schema or use supported extension attributes in Entra.

Check your app’s SCIM schema:

Query the app’s SCIM /Schemas endpoint.

Verify that your custom attributes (cftime, cfdroppy, etc.) are defined there.

Update the target app’s SCIM implementation:

If the attributes aren’t defined, extend the app’s SCIM schema to include them.

Ensure the app’s SCIM service can accept and return values for those attributes.

Reconfigure in Entra:

Once the schema is updated, go back to Entra provisioning → Mappings.

Add the custom attributes again. This time they should save successfully.

Alternative approach:

If schema extension isn’t possible, map your custom fields to existing supported attributes (like extensionAttribute1–15 in Azure AD).

These can then be synchronized to your app without breaking schema validation.

Your answer

Данило Кошнарьов 90 Reputation points

2025-12-27T21:13:55.5466667+00:00

The error occurs because Entra ID’s SCIM provisioning configuration does not accept arbitrary custom attribute URNs typed directly into the portal. The provisioning UI only supports attributes that are defined in the SCIM schema exposed by your target application’s /Schemas endpoint. If you manually add attributes that aren’t recognized by the app’s SCIM service, the portal will let you type them but will fail to save. You can’t just type custom SCIM attributes into Entra — they must exist in the target app’s SCIM schema. To fix this, extend your app’s SCIM schema or use supported extension attributes in Entra.

Check your app’s SCIM schema:

Query the app’s SCIM /Schemas endpoint.

Verify that your custom attributes (cftime, cfdroppy, etc.) are defined there.

Update the target app’s SCIM implementation:

If the attributes aren’t defined, extend the app’s SCIM schema to include them.

Ensure the app’s SCIM service can accept and return values for those attributes.

Reconfigure in Entra:

Once the schema is updated, go back to Entra provisioning → Mappings.

Add the custom attributes again. This time they should save successfully.

Alternative approach:

If schema extension isn’t possible, map your custom fields to existing supported attributes (like extensionAttribute1–15 in Azure AD).

These can then be synchronized to your app without breaking schema validation.