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(243.2, 16%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENH%3C/text%3E%3C/svg%3E)
According to your documentation: https://learn.microsoft.com/en-gb/azure/active-directory-b2c/add-api-connector?pivots=b2c-user-flow#before-creating-the-user the objectId of the user being created should be returned in the api request, however this is not the case.
I have checked the Application Claims > Users Object Id and this does not make a difference.
It is necessary to have the objectId in order to relate the newly created user to data in the application.
Hello, apologies for the confusing sample requests. Azure AD B2C sign up user flows will only include the objectId claim in the API request during the PreTokenIssuance/Before sending the token (preview) step. We will proceed to correct our documentation.
Let us know if you need additional assistance. If the answer was helpful, please accept it so that others can find a solution.
![](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(35.2, 23%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
Documentation is STILL NOT FIXED! I was developing an application based on the oid being provided and it isn't. PLEASE UPDATE THE DOCUMENTATION!
Apologies for that, I'm reaching within the documentation team to fix it and will come back to you ASAP.
![](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(236.8, 91%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
In the exact same situation, it's extremely frustrating how poorly documented (and seemingly supported) Azure B2B is compared with B2C. The documentation is merged together and it's a painful struggle of trial and error to figure out what is possible and what isn't
![](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(54.400000000000006, 81%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Everything is just so hard to use - poor documentation, just half baked stuff and they want us to pay through our nose for such a service. This post has been 2 years back and I still don't see the documentation updated. The current documentation still doesn not reflect how the object id can be sent to the API connector. Regretting choosing Azure!!!