5.2.1. App Protection Policies for Managed and BYOD Devices
💡 First Principle: An app protection policy follows the work account, not the device. When a user signs in to Outlook with a work account, the Intune App SDK inside Outlook downloads that account's policy and enforces it on that account's data. Anything that isn't corporate stays outside the rules. Ask "which account owns this data?" and you can predict what a policy will and won't touch.
What's managed. Only apps that integrate the Intune App SDK or are wrapped with the Intune App Wrapping Tool can receive app protection. Policies apply only in the work context: for Microsoft 365 apps, corporate locations are Exchange email and OneDrive work or school, and a new file counts as personal until it's saved to a corporate location. Apps can also support multiple managed accounts, with policy enforced per account.
Platform prerequisites. On Android, the Intune Company Portal must be installed to receive app protection even without enrollment, and Intune MAM requires Entra device registration for Microsoft 365 apps. App protection on Android requires Android 10.0 or later.
Creating a policy. Go to Apps > Protection > Create policy, choose iOS/iPadOS or Android, and work through Basics, Apps, Data protection, Access requirements, Conditional launch and Assignments. On the Apps page, Target policy to offers All Apps, Microsoft Apps, Core Microsoft Apps (Edge, Excel, Office, OneDrive, OneNote, Outlook, PowerPoint, SharePoint, Teams, To Do, Word) or Selected apps. Policies are assigned to user groups, and Microsoft advises applying app protection before you turn on the Conditional Access rule that requires it.
The three settings pages map to three questions:
- Data protection — where can org data go? Backup, sending and receiving data, cut/copy/paste, saving copies, printing, encryption.
- Access requirements — who may open it? App PIN, biometrics, work account credentials, how often to recheck.
- Conditional launch — under what conditions? Maximum PIN attempts, offline grace period, jailbroken or rooted devices, minimum OS and app versions, threat level. Each condition triggers an action; when conditions conflict, wipe beats block, and block beats a dismissible warning.
Managed vs unmanaged devices. A common design is two policies: a strict one for unmanaged personal devices and a more relaxed one for MDM-managed devices. You separate them with assignment filters for managed apps on the Assignments page. On iOS, "unmanaged" means no MDM passes the IntuneMAMUPN key to the app; on Android, it means Intune MDM wasn't detected.
The data protection framework gives you a tested starting point in three levels, each building on the one before:
| Setting | Level 1 Enterprise basic | Level 2 Enterprise enhanced | Level 3 Enterprise high |
|---|---|---|---|
| Purpose | Minimum for enterprise devices | Adds data-leakage controls and minimum OS | Adds advanced data protection, stronger PIN, Mobile Threat Defense |
| Encrypt org data | Require | Same as Level 1 | Same as Level 1 |
| Send org data to other apps | All apps | Policy managed apps | Same as Level 2 |
| Cut, copy and paste | Any app | Policy managed apps with paste in | Same as Level 2 |
| Backup | Allow | Block | Same as Level 2 |
| Print org data | Allow | Same as Level 1 | Block |
| App PIN | Required, simple PIN allowed, minimum 4 | Same as Level 1 | Simple PIN blocked, minimum 6 |
| Jailbroken or rooted device | Block access | Same as Level 1 | Wipe data |
| Offline grace period before wipe | 90 days | 30 days | Same as Level 2 |
| Device threat level (Mobile Threat Defense) | Not part of this level | Not part of this level | Max allowed Secured, otherwise block access |
Microsoft recommends rolling the levels out in rings: quality assurance, then preview, then production.
Selective wipe. Go to Apps > App selective wipe > Create wipe request and pick the user and device; Intune tracks a separate request for each protected app. On iOS and Android it requires deployed app protection. The wipe happens only when the user opens the app, and can take up to 30 minutes. You can also automate it as the Wipe data action of a conditional launch setting.
Windows. App protection also exists for Windows, aimed at personal, unmanaged Windows devices using Microsoft Edge. It's strict about that: the device must not be Entra joined or MDM enrolled to any tenant, and if it becomes MDM-managed later, app protection stops applying. Windows policies have two categories, Data protection and Health Checks (the Windows name for conditional launch).
⚠️ Exam Trap: Don't eliminate an app protection answer because the device "isn't enrolled in Intune". App protection policies work on unenrolled devices — that's their purpose. What they do need is an Intune license for the user, the user in a targeted group, an SDK-enabled app signed in with the work account and, on Android, Company Portal installed.
Reflection Question: An employee leaves the company, and their personal Android phone was never enrolled. What can you remove from it, what stays, and why must the employee open Outlook before the wipe actually happens?