Skip to content

Commit e2c22fb

Browse files
Update device-enrollment-program-enroll-ios.md
adding more clarity/resources to the limitation note based on customer confusion
1 parent ab9be47 commit e2c22fb

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

memdocs/intune/enrollment/device-enrollment-program-enroll-ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ Now that you've installed your token, you can create an enrollment profile for A
207207
- **Setup Assistant with modern authentication**: Devices running iOS/iPadOS 13.0 and later can use this method. Older iOS/iPadOS devices in this profile will fall back to using the **Setup Assistant (legacy)** process.
208208

209209
> [!NOTE]
210-
> MFA won't work for Setup Assistant with modern authentication if you're using a 3rd party MFA provider to present the MFA screen during enrollment. Only the Azure AD MFA screen works during enrollment.
210+
> MFA won't work for Setup Assistant with modern authentication if you're using a 3rd party MFA provider to present the MFA screen during enrollment. Only the Azure AD MFA screen works during enrollment. This AAD documentation would have the latest updates on support for custom controls for MFA - https://techcommunity.microsoft.com/t5/azure-active-directory-identity/upcoming-changes-to-custom-controls/ba-p/1144696
211211
212212
This method provides the same security as Company Portal authentication but avoids the issue of leaving end users with a device they can't use until the Company Portal installs.
213213

0 commit comments

Comments
 (0)