In addition to the schema attributes listed in Schema Attributes section, the connector supports managing the extended attributes that are registered on the client application on Azure. Creation of Local User (B2C) also supports custom attributes.
Could you add some additional details as to what clientID should be added here, and maybe how to get the correct one. Also a note as to when this would be needed over the standard ones below it?
Can a note be added here that the attributes are case sensitive? When a dev attempted to set this up, the powershell showed that the attribute name was ExtensionAttribute3: <data> so they created onPremisesExtensionAttribute_ExtensionAttribute3 which did not work until they changed it to onPremisesExtensionAttribute_extensionAttribute3 with the lowercase ‘e’.
When it wasn’t working they also tried the method above using the ClientId, which caused it to error out, so having the case sensitivity note might help there.
Hi @gmilunich! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-7278