01Description
Conditional Access did not restrict the OAuth 2.0 device code authentication flow. Any user could complete a device code sign-in, a flow intended for input-constrained devices such as conference room systems and command line tools.
02Impact
In device code phishing, an attacker generates a code and persuades the user to enter it at microsoft.com/devicelogin. The user completes their own MFA, and the attacker's session receives access and refresh tokens for the user's account. Because the user signs in on a genuine Microsoft page, the attack bypasses most phishing awareness cues and standard MFA.
03Severity
Typically
Medium
Typically Medium. Medium by default, given active device code phishing campaigns against Microsoft 365. Lower to Low where device compliance is required for all cloud apps. Report as an improvement where the tenant lacks Entra ID P1.
04How to verify
- 1Review Protection > Conditional Access > Policies for an enabled policy using Conditions > Authentication flows > Device code flow with a Block grant.
- 2Filter the Entra sign-in logs by authentication protocol (Device code) to see which users and applications use the flow today.
- 3Where authorized, initiate a device code sign-in with a test account and confirm it completes.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Create a Conditional Access policy that targets all users and all resources, sets Conditions > Authentication flows > Device code flow, and grants Block. This requires Entra ID P1.
- 2Exclude only the specific accounts or devices that need the flow, such as meeting room devices, and document each exclusion.
- 3Run the policy in Report-only mode first to identify legitimate use.
- 4Also block 'Authentication transfer' in the same condition unless there is a business need for it.
06References
Draft findings like this from your own evidence
Book a demo