5.2. Plan and Implement App Protection and App Configuration Policies
💡 First Principle: You can protect data without owning the device by drawing the boundary around the work data inside the app, not around the hardware. An app built with the Intune App SDK knows which account and files are corporate, so it can encrypt them, stop them leaking into personal apps and erase them on command, leaving personal photos and email untouched. That's why app-level controls are the default answer for personal devices.
Why care? Many employees won't hand device control to their employer, and without app-level protection you'd face a bad choice: block personal phones (and watch users forward work email to personal accounts) or allow them unprotected.
Three policy types divide the work:
| Policy | Job | Needs enrollment? | Where it lives |
|---|---|---|---|
| App protection policy | Protects org data inside apps: encryption, copy and save limits, PIN, launch checks, selective wipe | No | Apps > Protection |
| Conditional Access (Require app protection policy) | Refuses access unless the app is under app protection | No | Microsoft Entra admin center |
| App configuration policy | Supplies settings, such as allowed accounts or server names | Managed devices channel: yes; managed apps channel: no | Apps > Configuration |
⚠️ Common Misconception: Because most Intune features — configuration profiles, compliance, Required app installs — need enrollment, it's natural to assume app protection policies do too. They don't: they work independently of MDM, whether the device is enrolled in Intune, in a non-Microsoft MDM, or not at all. The user needs only an Entra account, an Intune license, membership in a targeted group and a work-account sign-in to the app; when they leave, a selective wipe removes only the organization's data.