User Provisioning Schema changes not applying for older users

Question

Within User Provisioning, I have been using the Schema Editor within a self-made enterprise app to quickly define the attribute mappings for the app. This has been working for a while, however recently there seems to have been some UI changes around this, which subsequently has broken this feature for certain users.

After fiddling around, I think I've found that the issue appears to be related to when a user has been created in Entra. I've been doing this with Global Administrators, so the role does not seem to affect this at all.

When using an older account (the user I've been testing with was created in September 2021 for reference), I get the following popup when trying to save changes on the editor:

Note: the white boxes are just blanking any ids in the screenshot to make sure there isn't anything identifiable here, as they are not relevant.

When this popup appears, any changes I make to the schema json are reverted, so the user is never able to apply the changes like this.

However, when a newer user (the user I have tested this with was created in July 2024) attempts to perform this, they receive a different have a different popup:

When this popup appears, the changes are kept, and the save works as intended. You can see that my change has not reverted where I have put "editable": False to demonstrate this.

---

Could this be investigated and fixed please, as it renders the Schema Editor unusable for any user who has been using Entra for any significant length of time. I am more than happy to try anything else to fix this, but this is very easy to reproduce, and I'm happy to provide extra information around this if needed.

Answer 1

Hello @Steve Norwood ,

As we disscussed in offline on the issue you are facing, as we engaged with the internal engineering team to figure out the issue, now the schema changes are being saved and editable. I have tested in my tenant as well seems the issue has been fixed by the engineering team. As you confirmed in your email, the issue has been fixed, and you are now able to make changes in the schema editor, with those changes being saved successfully.

Please "Accept the answer" as the issue has been solved. This will help us and others in the community as well. Let us know if you have any additional queries happy to assist you further.

Answer 2

Hello @Steve Norwood ,

I understand you are using schema editor within yourself and made enterprise application. When you are trying make any changes with old user account the changes are not applying but when you are trying to make changes with new user account the changes are applying to the schema editor.

Could you please check the attribute limitations in this document and verify them within the schema editor you're using? Also, can you specify which attributes you've changed for both the old and new user accounts, where the schema is not saving? I notice that the pop-ups are the same for both the old and new users.

The following attributes and objects aren't supported:

• Multivalued attributes.
• Reference attributes (for example, manager).
• Groups.
• Complex anchors (for example, ObjectTypeName+UserName).
• Attributes that have characters such as "." or "["
• Binary attributes.

Please refer to the document in detail for the attributes and objects used in app provisioning: link.

I hope this helps. Let me know if you have any further questions. I'm happy to assist you further.