From b5d8ea410e16351d499030d714fae7679d0ff486 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B8rund=20Dahl?=
 <83746585+JrndD@users.noreply.github.com>
Date: Tue, 10 Sep 2024 11:39:51 +0300
Subject: [PATCH] Update multi-factor-authentication.md

Should mention in the article that Temporary Access Pass is a solution where a second device is not available.
---
 memdocs/intune/enrollment/multi-factor-authentication.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/memdocs/intune/enrollment/multi-factor-authentication.md b/memdocs/intune/enrollment/multi-factor-authentication.md
index 031502c3ec6..d0bb6ac163e 100644
--- a/memdocs/intune/enrollment/multi-factor-authentication.md
+++ b/memdocs/intune/enrollment/multi-factor-authentication.md
@@ -90,7 +90,7 @@ Complete these steps to enable multi-factor authentication during Microsoft Intu
 After you apply and deploy this policy, users will see a one-time MFA prompt when they enroll their device. 
 
 > [!NOTE]
-> A second device is required to complete the MFA challenge for these types of corporate-owned devices:  
+> A second device or a Temporary Access Pass is required to complete the MFA challenge for these types of corporate-owned devices:  
 >
 > - Android Enterprise fully managed devices  
 > - Android Enterprise corporate-owned devices with a work profile