liveBook · Manning

Authentication factor

As explained in Microsoft Azure in Action

An authentication factor is an independent category of evidence used to verify an identity, such as knowledge, possession, or a biometric characteristic.

An authentication factor is a category of evidence used to verify identity. Multifactor authentication (MFA) strengthens access by requiring at least two different factor types instead of trusting a username and password alone. section 6.5

The three factor categories are:

  • Something you know, such as a username and password. section 6.5
  • Something you have, such as a phone with an authenticator app or a hardware security key. section 6.5
  • Something you are, such as a fingerprint or face scan. section 6.5

Requiring multiple factors limits the damage from reused, exposed, or weak passwords. In Azure, administrators configure the requirement through Entra ID Security and Conditional Access policies. section 6.5

How Microsoft Azure in Action covers it

How deep it goes
Defines three factor categories and sketches Conditional Access configuration, but stops short of detailed policy design.
Examples
Uses passwords, authenticator phones, hardware security keys, fingerprints, face scans, and an Azure portal MFA policy.
What it assumes
Assumes a service requiring authentication and introduces the factor categories from familiar username-and-password access.
What you can do after
Operate/configure MFA by creating an Entra ID Conditional Access policy requiring multifactor authentication.
How it connects
Connects authentication factors with multifactor authentication, Conditional Access, Entra ID, and username-and-password credentials.

Also explained in

Compare how 2 books explain authentication factor →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.