Microsoft Entra External ID
Authentication

User Attributes

In brief

The documentation now directs Embedded native authentication and BYO UX users to follow the native authentication attribute contract, including exact returned `attributeId` values, current requirements, and validation metadata.

What Entra admins need to know

Administrators should consult the attribute contract when implementing these experiences.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Attribute collection in your interface

For Embedded native authentication and BYO UX, follow the native authentication attribute contract. Use exact returned attributeId values, current requirements, and validation metadata rather than copying the directory property table into a request. Submissions to the Native Authentication API submissions use string values even when the directory attribute has a Boolean or integer data type.

For an existing V1 SDK integration, use the MSAL Android library for library-specific attribute types. Those types aren't the response schema for the Native Authentication API.

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…