Skip to content

Commit d60d4a9

Browse files
Merge pull request #19244 from MandiOhlinger/PRs
Order
2 parents fea3fb0 + 99c690c commit d60d4a9

3 files changed

Lines changed: 15 additions & 16 deletions

File tree

intune/intune-service/includes/app-protection-framework-level1.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ The policies in level 1 enforce a reasonable data access level while minimizing
1212

1313
#### Data protection
1414

15-
| Setting | Setting description | Value | Platform |
16-
|-----------------|--------------------------------------------------------|-----------------------|----------------------------------------|
15+
| Setting | Setting description | Value | Platform |
16+
|---|---|---|---|
1717
| Data Transfer | Back up org data to… | Allow | iOS/iPadOS, Android |
1818
| Data Transfer | Send org data to other apps | All apps | iOS/iPadOS, Android |
1919
| Data Transfer | Send org data to | All destinations | Windows |
@@ -34,7 +34,7 @@ The policies in level 1 enforce a reasonable data access level while minimizing
3434
#### Access requirements
3535

3636
| Setting | Value | Platform | Notes |
37-
|----------------------------------------------------------------|---------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
37+
|---|---|---|---|
3838
| PIN for access | Require | iOS/iPadOS, Android | |
3939
| PIN type | Numeric | iOS/iPadOS, Android | |
4040
| Simple PIN | Allow | iOS/iPadOS, Android | |
@@ -52,13 +52,13 @@ The policies in level 1 enforce a reasonable data access level while minimizing
5252

5353
#### Conditional launch
5454

55-
| Setting | Setting description | Value / Action | Platform | Notes |
56-
|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
55+
| Setting | Setting description | Value / Action | Platform | Notes |
56+
|---|---|---|---|---|
5757
| App conditions | Max PIN attempts | 5 / Reset PIN | iOS/iPadOS, Android | |
5858
| App conditions | Offline grace period | 10080 / Block access (minutes) | iOS/iPadOS, Android, Windows | |
5959
| App conditions | Offline grace period | 90 / Wipe data (days) | iOS/iPadOS, Android, Windows | |
6060
| Device conditions | Jailbroken/rooted devices | N/A / Block access | iOS/iPadOS, Android | |
61-
| Device conditions | SafetyNet device attestation | Basic integrity and certified devices / Block access | Android | <p>This setting configures Google Plays device integrity check on end-user devices. Basic integrity validates the integrity of the device. Rooted devices, emulators, virtual devices, and devices with signs of tampering fail basic integrity. </p><p> Basic integrity and certified devices validates the compatibility of the device with Google's services. Only unmodified devices that have been certified by Google can pass this check.</p> |
61+
| Device conditions | SafetyNet device attestation | Basic integrity and certified devices / Block access | Android | <p>This setting configures Google Play's device integrity check on end-user devices. Basic integrity validates the integrity of the device. Rooted devices, emulators, virtual devices, and devices with signs of tampering fail basic integrity. </p><p> Basic integrity and certified devices validates the compatibility of the device with Google's services. Only unmodified devices that have been certified by Google can pass this check.</p> |
6262
| Device conditions | Require threat scan on apps | N/A / Block access | Android | This setting ensures that Google's Verify Apps scan is turned on for end user devices. If configured, the end-user will be blocked from access until they turn on Google's app scanning on their Android device. |
6363
| Device conditions | Max allowed device threat level | Low / Block access | Windows | |
6464
| Device conditions | Require device lock | Low/Warn | Android | This setting ensures that Android devices have a device password that meets the minimum password requirements. |

intune/intune-service/includes/app-protection-framework-level2.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,15 @@ Level 2 is the data protection configuration recommended as a standard for devic
3333

3434
| Setting | Setting description | Value / Action | Platform | Notes |
3535
|---|---|---|---|---|
36-
| App conditions | Disabled account | N/A / Block access | iOS/iPadOS, Android, Windows | |
36+
| App conditions | Disabled account | N/A / Block access | iOS/iPadOS, Android, Windows | |
37+
| App conditions | Offline grace period | 30 / Wipe data (days) | iOS/iPadOS, Android, Windows | |
3738
| Device conditions | Min OS version | *Format: Major.Minor.Build <br>Example: 14.8* / Block access | iOS/iPadOS | Microsoft recommends configuring the minimum iOS major version to match the supported iOS versions for Microsoft apps. Microsoft apps support an N-1 approach where N is the current iOS major release version. For minor and build version values, Microsoft recommends ensuring devices are up to date with the respective security updates. See [Apple security updates](https://support.apple.com/en-us/HT201222) for Apple's latest recommendations |
3839
| Device conditions | Min OS version | *Format: Major.Minor<br> Example: 9.0* / Block access | Android | Microsoft recommends configuring the minimum Android major version to match the supported Android versions for Microsoft apps. OEMs and devices adhering to Android Enterprise recommended requirements must support the current shipping release + one letter upgrade. Currently, Android recommends Android 9.0 and later for knowledge workers. See [Android Enterprise Recommended requirements](https://www.android.com/enterprise/recommended/requirements/) for Android's latest recommendations |
3940
| Device conditions | Min OS version | *Format: Build<br> Example: 10.0.26200.6899* / Block access | Windows | Microsoft recommends configuring the minimum Windows build to match the supported Windows versions for Microsoft apps. Currently, Microsoft recommends the following build:<ul><li>**Windows 11**: Build *10.0.26200.6899*. For more information, see [KB5066835 (25H2)](https://support.microsoft.com/help/5066835) and [Windows 11 release information](/windows/release-health/windows11-release-information).</li></ul> |
4041
| Device conditions | Min patch version | *Format: YYYY-MM-DD <br> Example: 2020-01-01* / Block access | Android | Android devices can receive monthly security patches, but the release is dependent on OEMs and/or carriers. Organizations should ensure that deployed Android devices do receive security updates before implementing this setting. See [Android Security Bulletins](https://source.android.com/security/bulletin/) for the latest patch releases. |
4142
| Device conditions | Required SafetyNet evaluation type | Hardware-backed key | Android | Hardware backed attestation enhances the existing Google's Play Integrity service check by applying a new [Hardware Backed](https://developer.android.com/training/safetynet/attestation#evaluation-types) evaluation type. It offers stronger root detection to address newer rooting tools and techniques that software-only solutions might not reliably identify.<p> As its name implies, hardware backed attestation uses a hardware-based component, which shipped with devices installed with Android 8.1 and later. Devices that were upgraded from an older version of Android to Android 8.1 are unlikely to have the hardware-based components necessary for hardware backed attestation. While this setting should be widely supported starting with devices that shipped with Android 8.1, Microsoft strongly recommends testing devices individually before enabling this policy setting broadly.</p> |
4243
| Device conditions | Require device lock | Medium/Block Access | Android | This setting ensures that Android devices have a device password that meets the minimum password requirements. |
4344
| Device conditions | Samsung Knox device attestation | Block Access | Android | Microsoft recommends configuring the **Samsung Knox device attestation** setting to **Block access** to ensure the user account is blocked from access if the device doesn't meet Samsung's Knox hardware-based verification of device health. This setting verifies all Intune MAM client responses to the Intune service were sent from a healthy device. <p> This setting applies to all devices targeted. To apply this setting only to Samsung devices, you can use "Managed apps" assignment filters. For more information on assignment filters, see [Use filters when assigning your apps, policies, and profiles in Microsoft Intune](/intune/intune-service/fundamentals/filters).|
44-
| App conditions | Offline grace period | 30 / Wipe data (days) | iOS/iPadOS, Android, Windows | |
4545

4646
> [!NOTE]
4747
> Windows conditional launch settings are labeled as **Health Checks**.

intune/intune-service/includes/app-protection-framework-level3.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,8 @@ Level 3 is the data protection configuration recommended as a standard for organ
1313
1414
#### Data protection
1515

16-
| Setting | Setting description | Value | Platform | Notes |
17-
|---------------|---------------------------------------|----------------------------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------|
16+
| Setting | Setting description | Value | Platform | Notes |
17+
|---|---|---|---|---|
1818
| Data Transfer | Transfer telecommunication data to | Any policy-managed dialer app | Android | Administrators can also configure this setting to use a dialer app that doesn't support App Protection Policies by selecting **A specific dialer app** and providing the **Dialer App Package ID** and **Dialer App Name** values. |
1919
| Data Transfer | Transfer telecommunication data to | A specific dialer app | iOS/iPadOS | |
2020
| Data Transfer | Dialer App URL Scheme | *replace_with_dialer_app_url_scheme* | iOS/iPadOS | On iOS/iPadOS, this value must be replaced with the URL scheme for the custom dialer app being used. If the URL scheme isn't known, contact the app developer for more information. For more information on URL schemes, see [Defining a Custom URL Scheme for Your App](https://developer.apple.com/documentation/uikit/inter-process_communication/allowing_apps_and_websites_to_link_to_your_content/defining_a_custom_url_scheme_for_your_app).|
@@ -28,8 +28,8 @@ Level 3 is the data protection configuration recommended as a standard for organ
2828

2929
#### Access requirements
3030

31-
| Setting | Value | Platform |
32-
|-----------------------------------------------------------|--------------------|---------------------------------|
31+
| Setting | Value | Platform |
32+
|---|---|---|
3333
| Simple PIN | Block | iOS/iPadOS, Android |
3434
| Select Minimum PIN length | 6 | iOS/iPadOS, Android |
3535
| PIN reset after number of days | Yes | iOS/iPadOS, Android |
@@ -39,8 +39,9 @@ Level 3 is the data protection configuration recommended as a standard for organ
3939

4040
#### Conditional launch
4141

42-
| Setting | Setting description | Value / Action | Platform | Notes |
43-
|----------------------------|--------------------------------------|-------------------|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
42+
| Setting | Setting description | Value / Action | Platform | Notes |
43+
|---|---|---|---|---|
44+
| App conditions | Offline grace period | 30 / Block access (days) | iOS/iPadOS, Android, Windows | |
4445
| Device conditions | Require device lock | High/Block Access | Android | This setting ensures that Android devices have a device password that meets the minimum password requirements. |
4546
| Device conditions | Max allowed device threat level | Secured / Block access | Windows |
4647
| Device conditions | Jailbroken/rooted devices | N/A / Wipe data | iOS/iPadOS, Android | |
@@ -49,5 +50,3 @@ Level 3 is the data protection configuration recommended as a standard for organ
4950
| Device conditions | Max OS version | *Format: Major.Minor.Build <br>Example: 15.0* / Block access | iOS/iPadOS | Microsoft recommends configuring the maximum iOS/iPadOS major version to ensure beta or unsupported versions of the operating system aren't used. See [Apple security updates](https://support.apple.com/en-us/HT201222) for Apple's latest recommendations |
5051
| Device conditions | Max OS version | *Format: Major.Minor<br> Example: 22631.* / Block access | Windows | Microsoft recommends configuring the maximum Windows major version to ensure beta or unsupported versions of the operating system aren't used. |
5152
| Device conditions | Samsung Knox device attestation | Wipe data | Android | Microsoft recommends configuring the **Samsung Knox device attestation** setting to **Wipe data** to ensure the org data is removed if the device doesn't meet Samsung's Knox hardware-based verification of device health. This setting verifies all Intune MAM client responses to the Intune service were sent from a healthy device. <p> This setting will apply to all devices targeted. To apply this setting only to Samsung devices, you can use "Managed apps" assignment filters. For more information on assignment filters, see [Use filters when assigning your apps, policies, and profiles in Microsoft Intune](/mem/intune-service/fundamentals/filters).|
52-
| App conditions | Offline grace period | 30 / Block access (days) | iOS/iPadOS, Android, Windows | |
53-

0 commit comments

Comments
 (0)