Rıza KorkusuzTechnical Support
Cloud identity

Microsoft Entra ID Explained

Identities, sign-in and MFA, Conditional Access, password reset and troubleshooting sign-in problems.

Study guideUpdated 2026-10-20Original notes and diagrams

Study guide, not an experience claim. I wrote these notes while studying this tool for IT support and service desk work. I have not administered it in production. Everything here is summarized in my own words from public documentation and lab-style thinking. Confirm details in the current official documentation, because these products change often.

What it is

Microsoft Entra ID (the new name for Azure Active Directory) is Microsoft's cloud identity service. It stores users, groups, devices and app registrations, and it is the place every Microsoft 365, Intune and many third-party (single sign-on) sign-ins go through. It is not simply "Active Directory in the cloud": it speaks web protocols (OAuth 2.0, OpenID Connect, SAML) instead of Kerberos and LDAP, and it has no OUs or Group Policy.

Why organizations use it

  • One identity for email, Teams, SharePoint, Intune and thousands of SaaS apps (single sign-on).
  • Multifactor authentication (MFA) and passwordless options to stop password-only attacks.
  • Conditional Access: decide access based on user, device, location and risk.
  • Self-service password reset so users don't wait on the service desk.
  • Sync with on-premises Active Directory for hybrid environments.

How it works

A typical sign-in to a Microsoft 365 app:

Entra ID sign-in flow1. Open appOutlook, Teams, portal2. Primary authPassword / passkey3. MFAAuthenticator, SMS, key4. Conditional AccessEvaluate signals5. Token issuedAccess granted6. LoggedSign-in logsEntra ID sign-in flow1. Open appOutlook, Teams, portal2. Primary authPassword / passkey3. MFAAuthenticator, SMS, key4. Conditional AccessEvaluate signals5. Token issuedAccess granted6. LoggedSign-in logs
Simplified sign-in sequence.
Conditional Access: signals in, decision out Signals User / group Device compliant? Location / IP App + sign-in risk ConditionalAccess policy Allow Allow + require MFA Block
The sign-in logs show which policy applied and why. That is the first stop for "I can't get in" tickets.

Common service desk tasks

  • Check if an account is enabled, licensed and in the right groups.
  • Help with MFA re-registration after a phone change, following identity verification policy.
  • Guide users to self-service password reset (SSPR).
  • Read the sign-in log for a failed sign-in and note the error code and failing policy.
  • Check a device's join state (Entra joined / hybrid joined / registered).

Troubleshooting steps

  1. Get the exact time, app and error message (screenshot helps).
  2. Verify the account: enabled, not locked, password not expired, license assigned.
  3. Open sign-in logs, filter by user and time, read the failure reason and which Conditional Access policy applied.
  4. MFA issue: confirm registered methods; re-registration only after verifying the user's identity.
  5. Device-based block: check the device compliance and join state (hand over to the Intune page steps).
  6. For hybrid users, check whether the problem is on-prem (AD account locked) or cloud; changes in AD may need a sync cycle.
  7. Escalate with user, UTC time, correlation ID / request ID from the error page.

Glossary

Tenant
An organization's dedicated instance of Entra ID.
UPN
User Principal Name, the sign-in name like user@contoso.com.
MFA
A second proof of identity beyond the password.
Conditional Access
If-then access rules based on signals.
SSPR
Self-service password reset.
Entra joined
Device joined directly to the cloud directory.
Hybrid joined
Device joined to on-prem AD and registered in Entra ID.
Entra Connect / Cloud Sync
Tools that sync on-prem AD objects to Entra ID.

Official documentation