You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Preview | Production tenant | Mobile capability owners, UX | Enduser scenario validation, user facing documentation | 7-14 days, post Quality Assurance |
55
+
| Preview | Production tenant | Mobile capability owners, UX | End-user scenario validation, user facing documentation | 7-14 days, post Quality Assurance |
56
56
| Production | Production tenant | Mobile capability owners, IT help desk | N/A | 7 days to several weeks, post Preview |
57
57
58
58
As the above table indicates, all changes to the App Protection Policies should be first performed in a pre-production environment to understand the policy setting implications. Once testing is complete, the changes can be moved into production and applied to a subset of production users, generally, the IT department and other applicable groups. And finally, the rollout can be completed to the rest of the mobile user community. Rollout to production may take a longer amount of time depending on the scale of impact regarding the change. If there is no user impact, the change should roll out quickly, whereas, if the change results in user impact, rollout may need to go slower due to the need to communicate changes to the user population.
@@ -106,7 +106,7 @@ The policies in level 1 enforce a reasonable data access level while minimizing
106
106
107
107
| Setting | Setting description | Value | Platform |
| Device conditions | SafetyNet device attestation | Basic integrity and certified devices / Block access | Android | <p>This setting configures Google's SafetyNet Attestation on enduser 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> |
153
-
| 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 enduser will be blocked from access until they turn on Google's app scanning on their Android device. |
152
+
| Device conditions | SafetyNet device attestation | Basic integrity and certified devices / Block access | Android | <p>This setting configures Google's SafetyNet Attestation 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> |
153
+
| 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. |
154
154
| Device conditions | Require device lock | N/A / Block access | Android | This setting ensures that Android devices have a device PIN, password, or pattern are set to enable a device lock. This condition does not distinguish between lock options or the complexity. |
155
155
156
156
#### Level 2 enterprise enhanced data protection
@@ -163,7 +163,7 @@ The policy settings enforced in level 2 include all the policy settings recommen
| Data Transfer |Backup org data to… | Block | iOS/iPadOS, Android ||
166
+
| Data Transfer |Back up org data to… | Block | iOS/iPadOS, Android ||
167
167
| Data Transfer | Send org data to other apps | Policy managed apps | iOS/iPadOS, Android | <p>With iOS/iPadOS, administrators can configure this value to be "Policy managed apps", "Policy managed apps with OS sharing", or "Policy managed apps with Open-In/Share filtering". </p><p>Policy managed apps with OS sharing is available when the device is also enrolled with Intune. This setting allows data transfer to other policy managed apps, as well as file transfers to other apps that have are managed by Intune. </p><p>Policy managed apps with Open-In/Share filtering filters the OS Open-in/Share dialogs to only display policy managed apps. </p><p> For more information, see [iOS app protection policy settings](app-protection-policy-settings-ios.md).</p> |
168
168
| Data Transfer | Select apps to exempt | Default / skype;app-settings;calshow;itms;itmss;itms-apps;itms-appss;itms-services; | iOS/iPadOS ||
169
169
| Data Transfer | Save copies of org data | Block | iOS/iPadOS, Android ||
Copy file name to clipboardExpand all lines: memdocs/intune/apps/app-protection-policy-settings-android.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,7 +120,7 @@ For more information, see [Data transfer policy exceptions for apps](app-protect
120
120
| <ol><br>**PIN type**| Set a requirement for either numeric or passcode type PINs before accessing an app that has app protection policies applied. Numeric requirements involve only numbers, while a passcode can be defined with at least 1 alphabetical letter **or** at least 1 special character. <br><br> Default value = **Numeric**<br><br> **Note:** Special characters allowed include the special characters and symbols on the Android English language keyboard. |
121
121
| <ul><b> **Simple PIN**| Select **Allow** to allow users to use simple PIN sequences like *1234*, *1111*, *abcd* or *aaaa*. Select **Blocks** to prevent them from using simple sequences. Simple sequences are checked in 3 character sliding windows. If **Block** is configured, 1235 or 1112 would not be accepted as PIN set by the end user, but 1122 would be allowed. <br><br>Default value = **Allow** <br><br>**Note:** If Passcode type PIN is configured, and Simple PIN is set to Allow, the user needs at least one letter **or** at least one special character in their PIN. If Passcode type PIN is configured, and Simple PIN is set to Block, the user needs at least one number **and** one letter **and** at least one special character in their PIN. </li> |
122
122
| <ul><b> **Select minimum PIN length**| Specify the minimum number of digits in a PIN sequence. <br><br>Default value = **4**|
123
-
| <ul><b> **Fingerprint instead of PIN for access (Android 6.0+)** | Select **Allow** to allow the user to use [fingerprint authentication](https://developer.android.com/about/versions/marshmallow/android-6.0.html#fingerprint-authentication) instead of a PIN for app access. <br><br>Default value = **Allow** <br><br>**Note:** This feature supports generic controls for biometric on Android devices. OEM-specific biometric settings, like Samsung Pass, *are not supported.* <br><br>On Android, you can let the user prove their identity by using [Android fingerprint authentication](https://developer.android.com/about/versions/marshmallow/android-6.0.html#fingerprint-authentication) instead of a PIN. When the user tries to use this app with their work or school account, they are prompted to provide their fingerprint identity instead of entering a PIN. <br><br> Android personally-owned work profile enrolled devices require registering a separate fingerprint for the **Fingerprint instead of PIN for access** policy to be enforced. This policy takes effect only for policy-managed apps installed in the Android personally-owned work profile. The separate fingerprint must be registered with the device after the Android personally-owned work profile is created by enrolling in the Company Portal. For more information about personally-owned work profile fingerprints using Android personally-owned work profiles, see [Lock your work profile](https://support.google.com/work/android/answer/7029958). |
123
+
| <ul><b> **Fingerprint instead of PIN for access (Android 9.0+)** | Select **Allow** to allow the user to use [fingerprint authentication](https://developer.android.com/about/versions/marshmallow/android-6.0.html#fingerprint-authentication) instead of a PIN for app access. <br><br>Default value = **Allow** <br><br>**Note:** This feature supports generic controls for biometric on Android devices. OEM-specific biometric settings, like Samsung Pass, *are not supported.* <br><br>On Android, you can let the user prove their identity by using [Android fingerprint authentication](https://developer.android.com/about/versions/marshmallow/android-6.0.html#fingerprint-authentication) instead of a PIN. When the user tries to use this app with their work or school account, they are prompted to provide their fingerprint identity instead of entering a PIN. <br><br> Android personally-owned work profile enrolled devices require registering a separate fingerprint for the **Fingerprint instead of PIN for access** policy to be enforced. This policy takes effect only for policy-managed apps installed in the Android personally-owned work profile. The separate fingerprint must be registered with the device after the Android personally-owned work profile is created by enrolling in the Company Portal. For more information about personally-owned work profile fingerprints using Android personally-owned work profiles, see [Lock your work profile](https://support.google.com/work/android/answer/7029958). |
124
124
| <ul><b>**Override fingerprint with PIN after timeout**| To use this setting, select **Require** and then configure an inactivity timeout. <br><br>Default value = **Require**|
125
125
| <ul><b><ul><b> **Timeout (minutes of inactivity)**| Specify a time in minutes after which either a passcode or numeric (as configured) PIN will override the use of a fingerprint. This timeout value should be greater than the value specified under 'Recheck the access requirements after (minutes of inactivity)'.<br><br>Default value = **30**|
126
126
| <ul><b>**Biometrics instead of PIN for access**| Select **Allow** to allow the user to use Face Unlock to authenticate users on Android devices. If allowed, Face Unlock is used to access the app on Android 10 or higher devices. |
0 commit comments