Microsoft Entra IDTutorial Native Authentication Android Sign In Sign Out
In brief
To sign in a user using username (email) and password, collect the email and password from the user. If the username and password are valid, the app signs in the user.
What Entra admins need to know
Review the documentation change to determine whether it affects tenant configuration, security posture, or rollout plans.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
Open on Microsoft Learn ↗The comparison below is an extract of the Microsoft Learn article showing only the changed content. Open the full article for complete context.
To sign in a user using username (email) and password, collect the email and password from the user. If the username and password are valid, the app signs in the user.
If the Username built-in user attribute is enabled in your tenant's sign-up user flow, the username parameter in sign-in accepts either the user's email address or their username (alias). No separate sign-in logic is needed to support alias-based sign-in.
To sign in a user, you need to:
- Create a user interface (UI) to:
@@ -37,6 +37,8 @@ To sign in a user using the one-time passcode, collect the email and send an ema To sign in a user using username (email) and password, collect the email and password from the user. If the username and password are valid, the app signs in the user. +If the **Username** built-in user attribute is enabled in your tenant's sign-up user flow, the `username` parameter in sign-in accepts either the user's email address or their username (alias). No separate sign-in logic is needed to support alias-based sign-in.+ To sign in a user, you need to: 1. Create a user interface (UI) to: