From 4dc960643e1a1ee752442c7be2528f974e1fc2a9 Mon Sep 17 00:00:00 2001 From: LuNeicia Williams Date: Mon, 11 Nov 2024 10:32:46 -0600 Subject: [PATCH 1/3] Add mobile threat defense service info - Update compliance-policy-create-ios.md The Microsoft Learn article on Android states that the device threat level is evaluated by a third party mobile threat defense service. https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-android-for-work#device-health The Microsoft Learn article on iOS does not state from where the mobile threat defense level is evaluated. If the mobile threat defense for iOS is also evaluated by a third party mobile threat defense service, it would be helpful to note that in the doc. --- memdocs/intune/protect/compliance-policy-create-ios.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/memdocs/intune/protect/compliance-policy-create-ios.md b/memdocs/intune/protect/compliance-policy-create-ios.md index 2ef3da3e5c0..b2cafd40f05 100644 --- a/memdocs/intune/protect/compliance-policy-create-ios.md +++ b/memdocs/intune/protect/compliance-policy-create-ios.md @@ -81,7 +81,7 @@ For details about email profiles, see [configure access to organization email us - **Require the device to be at or under the Device Threat Level** *Supported for iOS 8.0 and later* - +Select the maximum allowed device threat level evaluated by your mobile threat defense service. Use this setting to take the risk assessment as a condition for compliance. Choose the allowed threat level: - **Not configured** (*default*) - This setting isn't evaluated for compliance or noncompliance. - **Secured** - This option is the most secure, and means that the device can't have any threats. a device with any level of threats is evaluated as noncompliant. @@ -197,4 +197,4 @@ For details about email profiles, see [configure access to organization email us - [Add actions for noncompliant devices](actions-for-noncompliance.md).and [use scope tags to filter policies](../fundamentals/scope-tags.md). - [Monitor your compliance policies](compliance-policy-monitor.md). -- See the [compliance policy settings for macOS](compliance-policy-create-mac-os.md) devices. \ No newline at end of file +- See the [compliance policy settings for macOS](compliance-policy-create-mac-os.md) devices. From 4dcb1aac1bf536cd771c2ec15e6ef0f387b2643b Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Wed, 29 Jan 2025 12:47:20 -0500 Subject: [PATCH 2/3] Update compliance policy creation date and formatting --- memdocs/intune/protect/compliance-policy-create-ios.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/memdocs/intune/protect/compliance-policy-create-ios.md b/memdocs/intune/protect/compliance-policy-create-ios.md index b2cafd40f05..5e86f1fdf1f 100644 --- a/memdocs/intune/protect/compliance-policy-create-ios.md +++ b/memdocs/intune/protect/compliance-policy-create-ios.md @@ -7,7 +7,7 @@ keywords: author: lenewsad ms.author: lanewsad manager: dougeby -ms.date: 05/15/2024 +ms.date: 01/29/2025 ms.topic: reference ms.service: microsoft-intune ms.subservice: protect @@ -80,9 +80,10 @@ For details about email profiles, see [configure access to organization email us - **Block** - Mark rooted (jailbroken) devices as not compliant. - **Require the device to be at or under the Device Threat Level** - *Supported for iOS 8.0 and later* -Select the maximum allowed device threat level evaluated by your mobile threat defense service. - Use this setting to take the risk assessment as a condition for compliance. Choose the allowed threat level: + *Supported for iOS 8.0 and later* + + Select the maximum allowed device threat level evaluated by your mobile threat defense service. + Use this setting to take the risk assessment as a condition for compliance. Choose the allowed threat level: - **Not configured** (*default*) - This setting isn't evaluated for compliance or noncompliance. - **Secured** - This option is the most secure, and means that the device can't have any threats. a device with any level of threats is evaluated as noncompliant. - **Low** - The device is evaluated as compliant if only low-level threats are present. Anything higher puts the device in a noncompliant status. From d06b11a00bd0becec983eb9643617dc9e1e67963 Mon Sep 17 00:00:00 2001 From: Rebecca Agiewich <16087112+rjagiewich@users.noreply.github.com> Date: Wed, 29 Jan 2025 10:02:47 -0800 Subject: [PATCH 3/3] UI updates --- .acrolinx-config.edn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.acrolinx-config.edn b/.acrolinx-config.edn index be92383dddc..f6d32f5f132 100644 --- a/.acrolinx-config.edn +++ b/.acrolinx-config.edn @@ -38,7 +38,7 @@ For more information about the exception criteria and exception process, see [Mi Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. _You should fix all spelling errors regardless of your total score_. Fixing spelling errors helps maintain customer trust in overall content quality. -| Article | Total score
(Required: 80) | Words + phrases
(Brand, terms) | Correctness
(Spelling, grammar) | Clarity
(Readability) | +| Article | Total score
(Required: 80) |Terminology | Spelling and Grammar | Clarity
(Readability) | |---------|:--------------:|:--------------------:|:------:|:---------:| "