This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have a requirement where the application I'm working on needs an integer-based user ID associated with each user. I know that B2C generates a hexadecimal UUID, but that would be a very large number if converted to an integer.
Before my client switched to B2C, they used an auto incrementing column for each user in the database. But I don't know of an easy way to implement this in B2C. I know how to create custom attributes, which we already use. But I don't know how to create a custom attribute that would auto increment like this.
It doesn't even have to be an auto incremented value, but just an integer value that isn't enormous. One thought was to use the array index of the user, but then anytime a user is deleted, the other IDs would have to be updated in the database, so that's not really feasible.
Any suggestions would be greatly appreciated.
Managing external identities to enable secure access for partners, customers, and other non-employees
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 32%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJR%3C/text%3E%3C/svg%3E)
Thanks @Anonymous and Please use rest api integration with Azure B2C custom application to implement auto incrementing integer concepts with custom policy. Please refer this document- https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-rest-api-intro/
Thank you. I was hoping to avoid a custom policy, as it seems pretty complex for a relatively simple use case. But it looks like it might be unavoidable. For now, I am using a function app that periodically checks for new users and uses the Graph API to update the extension attribute. But I will look more into the custom policy option.