From 5c805deafa9ae6dcab1dccaf5e2f74b8f0336767 Mon Sep 17 00:00:00 2001 From: Michael Mardahl Date: Tue, 24 Sep 2019 07:36:20 +0200 Subject: [PATCH] Update windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- ...roll-a-windows-10-device-automatically-using-group-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md b/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md index 027941f4b4..ae4db48664 100644 --- a/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md +++ b/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md @@ -124,7 +124,7 @@ If two-factor authentication is required, you will be prompted to complete the p ![Two-factor authentication notification](images/autoenrollment-2-factor-auth.png) ->[!Tip] +> [!Tip] > You can avoid this behavior by using Conditional Access Policies in Azure AD. Learn more by reading [What is Conditional Access?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview).