Preventing Azure Active Directory terms of use from blocking Intune enrollment

Published 05-04-2021 08:00 AM 8,400 Views

By Wayne Bennett – Sr Program Manager | Microsoft Endpoint Manager – Intune

 

Using Microsoft Endpoint Manager – Microsoft Intune to set your company’s terms and conditions meets the requirements of many organizations. However, the Azure Active Directory (Azure AD) terms of use feature offers greater functionality— including terms of use in different languages and integration with Conditional Access in the form of grant controls. You can learn more about the differences between the two solutions in this blog post.

 

Potential to block access to Intune

If you’ve configured the Azure AD terms of use solution and set a grant control to require users to accept terms of use in your Conditional Access policy, you need to be aware of a configuration scenario that might unintentionally block access for your users when they try to enroll into Intune.

 

Typical configuration

When creating an Azure AD terms of use policy, you have the option to select Require users to consent on every device. If you choose this setting, you will see the Consent on every device will require users to register each device with Azure AD prior to getting access warning. Once saved, you are unable to change this setting.

 

Example screenshot to register each device with Azure AD prior to getting access in a Conditional Access policyExample screenshot to register each device with Azure AD prior to getting access in a Conditional Access policy

 

After you create the terms of use policy, the next step is to create a Conditional Access policy. As shown in the following example, many organizations will target All Cloud Apps without configuring any exclusions.

 

Example screenshot of targeting All cloud apps in a Conditional Access policyExample screenshot of targeting All cloud apps in a Conditional Access policy

 

Additionally, many organizations will select Require device to be marked as compliant grant controls and require users to accept the Azure AD terms of use policy.

 

Example screenshot of configuring both the "Require device to be marked as compliant" and "Terms of Use" policies under the Grant controlExample screenshot of configuring both the "Require device to be marked as compliant" and "Terms of Use" policies under the Grant control

 

Blocking enrollment issue

The combination of Azure AD terms of use requiring users to consent on every device, Conditional Access policy targeting All Cloud Apps, and the control requiring the user to accept the Azure AD terms of use results in the following unintended behaviour during the Intune enrollment process:

  • Once the user has authenticated in the Company Portal, prior to Azure AD terms of use appearing, the Help us keep your device secure message will appear. The user will be prompted to install the Microsoft Authenticator app, Conditional Access controls will begin a continuous registration cycle, and the user will be unable to complete enrollment.

 

The issue is caused by selecting Require users to consent on every device, requiring users to register each device with Azure AD prior to getting access, as per the warning, when creating the terms of use policy.

 

Example screenshot of the "Help us keep your device secure" messageExample screenshot of the "Help us keep your device secure" message

 

Prevent Intune enrollment from being blocked

There are two methods to keep the enrollment blocking scenario from occurring:

 

Method 1: The Terms of use dialog

The first method is to ensure that Require users to consent on every device in the Terms of use dialog remains at the default Off setting when creating the Azure AD terms of use policy.

 

Note

Once the Azure AD terms of use policy is created, it is not possible to edit the Require users to consent on every device setting. You must create and target a new terms of use policy in the Conditional Access policy.

 

Method 2: Exclude cloud apps

The second method is to exclude certain cloud apps from Conditional Access targeting. The Per-device terms of use section of the Azure Active Directory terms of use documentation states that “The Intune Enrollment app is not supported. Ensure that it is excluded from any Conditional Access policy requiring Terms of Use policy.” However, excluding the Microsoft Intune Enrollment cloud app is not sufficient— as the example below shows, you must also exclude the Microsoft Intune cloud app.

 

Example screenshot of excluding "Microsoft Intune" and "Microsoft Intune Enrollment" from the Cloud apps or actions listExample screenshot of excluding "Microsoft Intune" and "Microsoft Intune Enrollment" from the Cloud apps or actions list

 

Conclusion

Changing your configuration using either of the suggested methods will prevent the Intune enrollment blocking scenario. Before you make any change, be sure to evaluate the settings so you don’t impact any existing Conditional Access requirements.

 

More info and feedback

For further resources on this subject, please see the links below.

 

Plan an Azure Active Directory Conditional Access Deployment

Troubleshoot Conditional Access using the What If tool

What is Microsoft Intune

Conditional Access require terms of use

Cloud apps or actions in Conditional Access policy

Device compliance policies in Microsoft Intune

 

Let us know if you have any additional questions by replying to this post or reaching out to @IntuneSuppTeam  on Twitter.

%3CLINGO-SUB%20id%3D%22lingo-sub-2318525%22%20slang%3D%22en-US%22%3EPreventing%20Azure%20Active%20Directory%20terms%20of%20use%20from%20blocking%20Intune%20enrollment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2318525%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EBy%20Wayne%20Bennett%20%E2%80%93%20Sr%20Program%20Manager%20%7C%20Microsoft%20Endpoint%20Manager%20%E2%80%93%20Intune%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUsing%20Microsoft%20Endpoint%20Manager%20%E2%80%93%20Microsoft%20Intune%20to%20set%20your%20company%E2%80%99s%20terms%20and%20conditions%20meets%20the%20requirements%20of%20many%20organizations.%20However%2C%20the%20Azure%20Active%20Directory%20(Azure%20AD)%20terms%20of%20use%20feature%20offers%20greater%20functionality%E2%80%94%20including%20terms%20of%20use%20in%20different%20languages%20and%20integration%20with%20Conditional%20Access%20in%20the%20form%20of%20grant%20controls.%20You%20can%20learn%20more%20about%20the%20differences%20between%20the%20two%20solutions%20in%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fintune-customer-success%2Fchoosing-the-right-terms-solution-for-your-organization%2Fba-p%2F280180%22%20target%3D%22_blank%22%3Eblog%20post%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-2028220209%22%20id%3D%22toc-hId-2027478257%22%3E%3CSTRONG%3EPotential%20to%20block%20access%20to%20Intune%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EIf%20you%E2%80%99ve%20configured%20the%20Azure%20AD%20terms%20of%20use%20solution%20and%20set%20a%20grant%20control%20to%20require%20users%20to%20accept%20terms%20of%20use%20in%20your%20Conditional%20Access%20policy%2C%20you%20need%20to%20be%20aware%20of%20a%20configuration%20scenario%20that%20might%20unintentionally%20block%20access%20for%20your%20users%20when%20they%20try%20to%20enroll%20into%20Intune.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-220765746%22%20id%3D%22toc-hId-220023794%22%3E%3CSTRONG%3ETypical%20configuration%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EWhen%20creating%20an%20Azure%20AD%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fconditional-access%2Fterms-of-use%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eterms%20of%20use%20policy%3C%2FA%3E%2C%20you%20have%20the%20option%20to%20select%20%3CSTRONG%3ERequire%20users%20to%20consent%20on%20every%20device%3C%2FSTRONG%3E.%20If%20you%20choose%20this%20setting%2C%20you%20will%20see%20the%20%3CSTRONG%3EConsent%20on%20every%20device%20will%20require%20users%20to%20register%20each%20device%20with%20Azure%20AD%20prior%20to%20getting%20access%3C%2FSTRONG%3E%20warning.%20Once%20saved%2C%20you%20are%20unable%20to%20change%20this%20setting.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Azure%20AD%20Blog-1.png%22%20style%3D%22width%3A%20669px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F277835iF2F62250F1613FAA%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Azure%20AD%20Blog-1.png%22%20alt%3D%22Example%20screenshot%20to%20register%20each%20device%20with%20Azure%20AD%20prior%20to%20getting%20access%20in%20a%20Conditional%20Access%20policy%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EExample%20screenshot%20to%20register%20each%20device%20with%20Azure%20AD%20prior%20to%20getting%20access%20in%20a%20Conditional%20Access%20policy%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20you%20create%20the%20terms%20of%20use%20policy%2C%20the%20next%20step%20is%20to%20create%20a%20Conditional%20Access%20policy.%20As%20shown%20in%20the%20following%20example%2C%20many%20organizations%20will%20target%20%3CSTRONG%3EAll%20Cloud%20Apps%3C%2FSTRONG%3E%20without%20configuring%20any%20exclusions.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Azure%20AD%20Blog-2.png%22%20style%3D%22width%3A%20564px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F277836i2A2F2222CB2F5BA6%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Azure%20AD%20Blog-2.png%22%20alt%3D%22Example%20screenshot%20of%20targeting%20All%20cloud%20apps%20in%20a%20Conditional%20Access%20policy%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EExample%20screenshot%20of%20targeting%20All%20cloud%20apps%20in%20a%20Conditional%20Access%20policy%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAdditionally%2C%20many%20organizations%20will%20select%20%3CSTRONG%3ERequire%20device%20to%20be%20marked%20as%20compliant%3C%2FSTRONG%3E%20grant%20controls%20and%20require%20users%20to%20accept%20the%20Azure%20AD%20terms%20of%20use%20policy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Azure%20AD%20Blog-3.png%22%20style%3D%22width%3A%20358px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F277837i3156ED92E0186F6D%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Azure%20AD%20Blog-3.png%22%20alt%3D%22Example%20screenshot%20of%20configuring%20both%20the%20%26quot%3BRequire%20device%20to%20be%20marked%20as%20compliant%26quot%3B%20and%20%26quot%3BTerms%20of%20Use%26quot%3B%20policies%20under%20the%20Grant%20control%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EExample%20screenshot%20of%20configuring%20both%20the%20%22Require%20device%20to%20be%20marked%20as%20compliant%22%20and%20%22Terms%20of%20Use%22%20policies%20under%20the%20Grant%20control%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1586688717%22%20id%3D%22toc-hId--1587430669%22%3E%3CSTRONG%3EBlocking%20enrollment%20issue%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EThe%20combination%20of%20Azure%20AD%20terms%20of%20use%20requiring%20users%20to%20consent%20on%20every%20device%2C%20Conditional%20Access%20policy%20targeting%20All%20Cloud%20Apps%2C%20and%20the%20control%20requiring%20the%20user%20to%20accept%20the%20Azure%20AD%20terms%20of%20use%20results%20in%20the%20following%20unintended%20behaviour%20during%20the%20Intune%20enrollment%20process%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EOnce%20the%20user%20has%20authenticated%20in%20the%20Company%20Portal%2C%20prior%20to%20Azure%20AD%20terms%20of%20use%20appearing%2C%20the%20Help%20us%20keep%20your%20device%20secure%20message%20will%20appear.%20The%20user%20will%20be%20prompted%20to%20install%20the%20Microsoft%20Authenticator%20app%2C%20Conditional%20Access%20controls%20will%20begin%20a%20continuous%20registration%20cycle%2C%20and%20the%20user%20will%20be%20unable%20to%20complete%20enrollment.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20issue%20is%20caused%20by%20selecting%20%3CSTRONG%3ERequire%20users%20to%20consent%20on%20every%20device%3C%2FSTRONG%3E%2C%20requiring%20users%20to%20register%20each%20device%20with%20Azure%20AD%20prior%20to%20getting%20access%2C%20as%20per%20the%20warning%2C%20when%20creating%20the%20terms%20of%20use%20policy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Azure%20AD%20Blog-4.png%22%20style%3D%22width%3A%20333px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F277838iB27E7360CE76E35E%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Azure%20AD%20Blog-4.png%22%20alt%3D%22Example%20screenshot%20of%20the%20%26quot%3BHelp%20us%20keep%20your%20device%20secure%26quot%3B%20message%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EExample%20screenshot%20of%20the%20%22Help%20us%20keep%20your%20device%20secure%22%20message%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-900824116%22%20id%3D%22toc-hId-900082164%22%3E%3CSTRONG%3EPrevent%20Intune%20enrollment%20from%20being%20blocked%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EThere%20are%20two%20methods%20to%20keep%20the%20enrollment%20blocking%20scenario%20from%20occurring%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-1591385590%22%20id%3D%22toc-hId-1590643638%22%3E%3CSTRONG%3EMethod%201%3A%20The%20Terms%20of%20use%20dialog%3C%2FSTRONG%3E%3C%2FH4%3E%0A%3CP%3EThe%20first%20method%20is%20to%20ensure%20that%20%3CSTRONG%3ERequire%20users%20to%20consent%20on%20every%20device%3C%2FSTRONG%3E%20in%20the%20Terms%20of%20use%20dialog%20remains%20at%20the%20default%20%3CSTRONG%3EOff%3C%2FSTRONG%3E%20setting%20when%20creating%20the%20Azure%20AD%20terms%20of%20use%20policy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EOnce%20the%20Azure%20AD%20terms%20of%20use%20policy%20is%20created%2C%20it%20is%20not%20possible%20to%20edit%20the%20%3CSTRONG%3ERequire%20users%20to%20consent%20on%20every%20device%3C%2FSTRONG%3E%20setting.%20You%20must%20create%20and%20target%20a%20%3CEM%3Enew%3C%2FEM%3E%20terms%20of%20use%20policy%20in%20the%20Conditional%20Access%20policy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--216068873%22%20id%3D%22toc-hId--216810825%22%3E%3CSTRONG%3EMethod%202%3A%20Exclude%20cloud%20apps%3C%2FSTRONG%3E%3C%2FH4%3E%0A%3CP%3EThe%20second%20method%20is%20to%20exclude%20certain%20cloud%20apps%20from%20Conditional%20Access%20targeting.%20The%20Per-device%20terms%20of%20use%20section%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fconditional-access%2Fterms-of-use%23per-device-terms-of-use%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%20Active%20Directory%20terms%20of%20use%3C%2FA%3E%20documentation%20states%20that%20%E2%80%9CThe%20Intune%20Enrollment%20app%20is%20not%20supported.%20Ensure%20that%20it%20is%20excluded%20from%20any%20Conditional%20Access%20policy%20requiring%20Terms%20of%20Use%20policy.%E2%80%9D%20However%2C%20excluding%20the%20Microsoft%20Intune%20Enrollment%20cloud%20app%20is%20not%20sufficient%E2%80%94%20as%20the%20example%20below%20shows%2C%20you%20must%20also%20exclude%20the%20Microsoft%20Intune%20cloud%20app.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Azure%20AD%20Blog-5.png%22%20style%3D%22width%3A%20765px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F277839iB14FC3D72ADA1CCD%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Azure%20AD%20Blog-5.png%22%20alt%3D%22Example%20screenshot%20of%20excluding%20%26quot%3BMicrosoft%20Intune%26quot%3B%20and%20%26quot%3BMicrosoft%20Intune%20Enrollment%26quot%3B%20from%20the%20Cloud%20apps%20or%20actions%20list%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EExample%20screenshot%20of%20excluding%20%22Microsoft%20Intune%22%20and%20%22Microsoft%20Intune%20Enrollment%22%20from%20the%20Cloud%20apps%20or%20actions%20list%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--226571977%22%20id%3D%22toc-hId--227313929%22%3E%3CSTRONG%3EConclusion%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EChanging%20your%20configuration%20using%20either%20of%20the%20suggested%20methods%20will%20prevent%20the%20Intune%20enrollment%20blocking%20scenario.%20Before%20you%20make%20any%20change%2C%20be%20sure%20to%20evaluate%20the%20settings%20so%20you%20don%E2%80%99t%20impact%20any%20existing%20Conditional%20Access%20requirements.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--2034026440%22%20id%3D%22toc-hId--2034768392%22%3E%3CSTRONG%3EMore%20info%20and%20feedback%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EFor%20further%20resources%20on%20this%20subject%2C%20please%20see%20the%20links%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fconditional-access%2Fplan-conditional-access%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPlan%20an%20Azure%20Active%20Directory%20Conditional%20Access%20Deployment%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fconditional-access%2Ftroubleshoot-conditional-access-what-if%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETroubleshoot%20Conditional%20Access%20using%20the%20What%20If%20tool%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Ffundamentals%2Fwhat-is-intune%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWhat%20is%20Microsoft%20Intune%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fconditional-access%2Frequire-tou%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EConditional%20Access%20require%20terms%20of%20use%20%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fconditional-access%2Fconcept-conditional-access-cloud-apps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ECloud%20apps%20or%20actions%20in%20Conditional%20Access%20policy%20%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fprotect%2Fdevice-compliance-get-started%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDevice%20compliance%20policies%20in%20Microsoft%20Intune%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ELet%20us%20know%20if%20you%20have%20any%20additional%20questions%20by%20replying%20to%20this%20post%20or%20reaching%20out%20to%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FIntuneSuppTeam%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%3E%40IntuneSuppTeam%3C%2FSPAN%3E%3C%2FA%3E%3CSPAN%3E%E2%80%AF%20on%20Twitter.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2318525%22%20slang%3D%22en-US%22%3E%3CP%3ERead%20this%20post%20to%20learn%20more%20about%20preventing%20Azure%20Active%20Directory%20terms%20of%20use%20from%20blocking%20Intune%20enrollment.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2318525%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Active%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%20Customer%20Success%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMEM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎May 04 2021 05:40 AM
Updated by: