Getting the sign-up attributes via native authentication in Entra External ID (EEID)
The documentation is here.
With native auth, you do not use the normal EEID auth. screens.
You have to build your own and use native auth. to control the flow to EEID.
“If all the required attributes were submitted via the /signup/v1.0/start endpoint, the app receives a continuation token without submitting any attributes.
Otherwise, Microsoft Entra's response indicates that the app needs to submit the required attributes. These attributes, built in or custom, were configured in the Microsoft Entra admin centre by the tenant administrator.”
How then do you get the required sign-up attributes that the admin has configured for that user flow?
Get Rory Braybrook’s stories in your inbox
Join Medium for free to get updates from this writer.
The answer is that it is sent in the request, e.g.
{
"error": "attributes_required",
"error_description": "User attributes required",
"error_codes": [
55106
],
"timestamp": "yy-mm-dd 02:37:33Z",
"trace_id": "d6966055-...-80500",
"correlation_id": "3944-...-60d6",
"continuation_token": "AQABAAEAAAAtn...",
"required_attributes": [
{
"name": "displayName",
"type": "string",
"required": true,
"options": {
"regex": ".*@.**$"
}
},
{
"name": "extension_2588abcdwhtfeehjjeeqwertc_age",
"type": "string",
"required": true
},
{
"name": "postalCode",
"type": "string",
"required": true,
"options": {
"regex":"^[1-9][0-9]*$"
}
}
],
}The attributes were configured, e.g.
But when I run the code, no attributes are sent.
The reason is that only the required attributes are sent.
You configure this in the “User flows/page layouts” tab.
When this is configured, you will get the required sign-in attributes as shown above.
All good.









