EIDAUTH-018: Microsoft Authenticator Login Context (Application Name and Location)
- Platform
- Entra ID / M365
- Category
- Entra ID Authentication Methods & MFA
- Severity
- Medium
- Zero Trust pillar
- Identity (weight 3)
- Golden fixtures
- 3
- Branch coverage
- Observed: fixtures prove the verdicts they exercise
- Provenance
- baseline
What it checks
When the Microsoft Authenticator authentication method is enabled, displaying login context information (application name and geographic location) in push and passwordless notifications gives the user the situational awareness needed to recognize and reject MFA prompts they did not initiate. Without this context, users are far more likely to approve adversary-initiated push requests during MFA fatigue or real-time phishing attacks. This setting is controlled by the displayAppInformationRequiredState and displayLocationInformationRequiredState feature settings on the MicrosoftAuthenticator method configuration.
Recommended value
If Microsoft Authenticator is enabled, displayAppInformationRequiredState is enabled (application name shown); displayLocationInformationRequiredState is also recommended
Remediation
Navigate to Entra ID > Protection > Authentication methods > Policies > Microsoft Authenticator. Under the Configure tab, set 'Show application name in push and passwordless notifications' to Enabled for all users, and enable 'Show geographic location in push and passwordless notifications'. This satisfies SCuBA MS.AAD.3.3, which requires Microsoft Authenticator to be configured to show login context when it is enabled.
Fixture-proven verdicts
Every verdict below is proven by a golden fixture in the module's gating test suite. This table derives from the last green run; it cannot be edited by hand.
| Scenario | Expected verdict |
|---|---|
| clean | PASS |
| known-bad | FAIL |
| no-data | Not Assessed |
Framework mappings
- CISA SCuBA
- MS.AAD.3.3v2
- NIST SP 800-53
- IA-2(1), IA-2(2)
- CIS M365 Benchmark
- 5.2.3.2
- EIDSCA
- AM06, AM09
- MITRE ATT&CK
- T1621