Skip to content

Authentication Strengths - What They Really Allow

The question it answers: Which authentication strengths used by Conditional Access allow weaker methods than their name suggests?

Conditional Access policies that require an authentication strength are only as strong as the combinations the strength allows. A custom strength called “Phishing-resistant MFA” that also accepts SMS, push or OATH codes quietly downgrades every policy that uses it. The Policy Analyser shows the strength’s name only.

Where in the appEntra ID › Identity Configuration › Authentication Strengths
WorkloadEntra ID
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceMicrosoft Entra ID P1.
Report id (API and MCP)entra.configuration.authentication-strengths
ColumnKeyType
SeveritySeverityStatus
TypeCategoryText
StrengthSubjectLink
CheckSettingText
Allowed combinationsValueText
FindingFindingText
Used byDetailText
DateWhenDate
CA policiesNumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

Licence: Microsoft Entra ID P1.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
Policy.Read.AllMicrosoft GraphRead your organization’s policies
Data sources it reads
  • GET /v1.0/policies/authenticationStrengthPolicies
  • GET /v1.0/identity/conditionalAccess/policies (cached)
GET /ir-api/v1/reports/entra.configuration.authentication-strengths?size=100

An AI assistant reads it with the MCP tool get_report and the id entra.configuration.authentication-strengths. The client needs the Read grant for Entra ID. See Using the API.