Intune app protection policies put guardrails around company data inside specific apps, such as Outlook, Teams and Edge, without requiring you to enroll or control the phone. Microsoft describes them as rules that keep an organization's data safe or contained in a managed app. For a small business where employees read email on personal phones, this is often the least invasive way to protect that data. This guide covers what the policies do, which controls matter, how to build and assign one, and how to pair it with Conditional Access so the policy is enforced rather than optional.
TL;DR
- App protection policies (also called MAM policies) protect data at the app level, so they work on personal phones and tablets that are not enrolled in device management.
- Core controls restrict copy and paste between apps, require an app PIN, encrypt work data and block saving corporate files to personal locations.
- A policy only protects users it is assigned to, in the apps it targets. Conditional Access with the "require app protection policy" grant is what stops unprotected apps from reaching Microsoft 365.
- Start with one of Microsoft's three data protection levels, pilot with a small group, and scope Conditional Access carefully to avoid lockouts.
- Keep different rules for personal (unenrolled) and company-managed devices rather than one policy for everyone.
Table of Contents
- What app protection policies actually do
- Do app protection policies work on unenrolled devices?
- Which apps and controls you can use
- Choosing a protection level
- Prerequisites before you build
- How to create and deploy a policy
- Making the policy enforceable with Conditional Access
- A rollout plan that respects your users
- Perspective
- Get a second pair of eyes on your setup
- FAQ
- Sources
What app protection policies actually do
An app protection policy (APP) is a set of rules that travels with the app rather than the device. When a user opens a protected app with their work account, Intune enforces the rules when they access or move corporate data. The user's personal photos, texts and other apps are not part of it.
That is the point of Mobile Application Management (MAM). With MAM, policies are defined on apps instead of devices, so administrators can protect organization data at the app level, especially in bring-your-own-device (BYOD) scenarios where device enrollment is not required.
If you have typed "Intune MAM policies" and "app protection policies" into search as if they were two things, they are the same capability. MAM is the approach, and app protection policies are the rule sets you create to carry it out.
Why this matters for a small business
Most SMBs do not issue every employee a company phone. People check email on whatever they own. Asking them to enroll a personal device in full management often meets resistance, because enrollment gives the company visibility and control over the whole device. App protection policies offer a narrower deal: the company protects its own data, and the employee keeps their device.

This also fits a Zero Trust approach. Microsoft's Zero Trust guidance notes that MAM supports least privilege: only approved apps can reach corporate data, and the data stays protected even when the device is unmanaged. If you are building that foundation more broadly, our 60-day Zero Trust plan for SMBs shows how this piece fits in.
Do app protection policies work on unenrolled devices?
Yes. Intune app protection policies are designed to protect corporate data on personal and unenrolled devices. They separate work data from personal data, so IT can secure corporate information without managing the device.
This is the question behind many forum threads, and the short answer is that the policy attaches to the user and the app, not the hardware. A person with a personal iPhone and a work account in Outlook can be covered, as long as the policy is assigned to them and the app is one that supports the policy.
There is a trade-off to plan for. Because you do not manage the device, you cannot see or control its wider state. That is why Microsoft's FAQ suggests that organizations allowing both managed and unmanaged devices apply stricter MAM policies to unenrolled devices and consider more relaxed or differentiated policies for devices managed through MDM.

Which apps and controls you can use
Supported apps
Supported apps include Microsoft 365 apps such as Outlook, Teams, Word, Excel and Microsoft Edge, plus partner apps. Check Microsoft's supported apps list before promising protection for a line-of-business or third-party app, because an app must support the policy to be covered. Microsoft also documents that app protection policies can set security requirements for Windows App on iOS and Android, and Microsoft Edge on Windows.
Data protection and access controls
Policies are organized into groups of settings. The ones most small businesses start with, per Microsoft's documentation of policy behavior:
- Restricting cut, copy and paste between apps, so a customer list copied out of Outlook cannot be pasted into a personal notes app.
- Requiring an app PIN to open protected apps.
- Encrypting work or school account data inside the app.
- Blocking "save as" for corporate files, so documents do not land in personal storage.
Conditional launch
Conditional launch settings decide whether an app opens at all. According to the same Microsoft page, administrators can:
- Reset the PIN after a maximum number of failed attempts.
- Enforce a minimum OS version.
- Block access after an offline grace period.
These are useful guardrails for phones that fall behind on updates. Set them with your users in mind: a very strict offline period will frustrate people who travel or work in low-signal sites.
Choosing a protection level
Microsoft frames app protection around three levels: enterprise basic, enterprise enhanced and enterprise high data protection. They help you prioritize how much hardening you need rather than deciding every setting from scratch.
A sensible way to match them to a business:
| Situation | Where to start |
|---|---|
| General staff reading email and calendar on personal phones | Basic level, then tighten once you see how people work |
| Staff handling client financials, contracts or health information | Enhanced level, with the access and conditional launch settings reviewed |
| A small group with highly sensitive data, such as executives or finance | High level, applied to a named group only |
This is our suggested mapping, not a Microsoft rule. If your business handles regulated data, confirm the requirements with your compliance advisor or the regulation's own guidance before you settle on a level.
Prerequisites before you build
Per Microsoft's setup guidance, each user needs:
- A Microsoft Entra account.
- An assigned Intune license.
- Membership in a security group that the policy targets.
The policy must also target the app the user actually uses. Build your groups first. Assigning to a group rather than to individuals keeps the rollout reviewable, and it lets you separate pilot users, standard users and high-risk users.
If you plan to enforce the policy through Conditional Access, there is one more requirement: Microsoft Entra ID P1 or P2 licensing, plus a broker app. That is Microsoft Authenticator on iOS or Company Portal on Android, which registers the device with Microsoft Entra ID. Tell users ahead of time that they will be asked to install one.
How to create and deploy a policy
The flow in the Intune admin center follows Microsoft's documented steps:
- Create a new app protection policy and choose the platform: iOS/iPadOS or Android. Each platform needs its own policy.
- Select the apps the policy covers. Choose the Microsoft 365 apps your people actually use first.
- Configure data protection settings: data transfer, encryption and related controls.
- Configure access requirements, such as the PIN.
- Configure conditional launch: failed PIN attempts, minimum OS version, offline grace period.
- Assign the policy to a user group.
- Review and create.
Two habits help here. First, name policies by platform, level and audience (for example, "iOS, Basic, All Staff"), so you can find them six months later. Second, write down why each non-default setting exists. When someone asks why they cannot paste into a personal app, you will have an answer.
Making the policy enforceable with Conditional Access
An app protection policy on its own is a rule for apps that opt in. Nothing stops a user from reaching Exchange Online through a mail app that does not support the policy. Conditional Access closes that gap.
Using the "require app protection policy" grant control, users can reach corporate data only through apps that have APP enforced. Access from unapproved or non-compliant client apps is blocked. Microsoft describes this as the two working in tandem so that only client apps that support APP can reach Microsoft 365 services such as Exchange Online.
Avoid locking people out
Microsoft recommends multiple granular Conditional Access policies and careful scoping so you do not inadvertently block access. In practice:
- Roll out to a pilot group before the whole company.
- Keep break-glass accounts out of scope, and document them.
- Make sure every targeted user already has the license, the group membership and the broker app.
- Use report-only mode where available to see what a policy would have blocked before you turn it on.
For a phased approach written for smaller teams, see our Conditional Access design guide for SMBs. Conditional Access sits alongside other tenant hygiene, and our Entra security best practices cover the neighboring controls.
A rollout plan that respects your users
The technical setup is the easy half. The harder half is people. A policy that changes how they open email on their own phone will generate questions.
- Pick a pilot of 5 to 10 people across roles: someone in sales, someone in finance, one frequent traveler, and one person who is not technical.
- Write a one-page note in plain language. Explain what the company can and cannot see, which is app data, not personal photos or messages. Explain what the user will notice: a PIN prompt, a broker app install, and limits on copying.
- Run the pilot for a couple of weeks, collect friction points, and adjust conditional launch settings that cause avoidable lockouts.
- Expand by group, not all at once. Keep the helpdesk script ready.
- Review logs. Microsoft documents app protection policy logs that show how settings are applied, which is where you start when one user's app behaves differently from another's.
Mistakes we see to avoid
- Assigning to the wrong group type. Users who are not in the targeted group simply are not protected.
- Forgetting a platform. An iOS policy does nothing for Android users.
- Applying one policy to managed and unmanaged devices alike. Differentiate them as Microsoft's FAQ suggests.
- Turning on Conditional Access before the pilot is licensed and ready. This is the usual cause of surprise lockouts.
- Treating the policy as set and forget. New apps, new OS versions and staff changes all affect coverage.
Perspective
Most small businesses we speak with are not asking for a perfect mobile security program. They want to stop customer data from leaking through personal phones without turning every employee's device into company property.
App protection is a good answer to that, and it is also easy to get wrong. The failure is rarely the policy itself. It is the missing group assignment, the unlicensed user, or the Conditional Access rule switched on before the pilot finished.
Our approach to technology work is to rank by risk and return rather than by what sounds impressive, build into the tools a team already uses, and hand over a plain-language plan the client owns. For mobile data, that means a short list: who needs protection, which apps hold the data, which level fits, and how we will know it is working. Then we pilot, adjust and roll out.
A policy you understand and can explain to your staff is worth more than a long settings list nobody remembers.
jaras
Get a second pair of eyes on your setup
If you are not sure which of your users, apps and devices are covered, our team can walk through it with you. Mindpod starts with a free technology assessment, then produces a prioritized plain-language plan that you own. We can also deliver and run the work if you want help.

You can book a free assessment with Mindpod Technologies to review your Intune and Entra setup, and decide what to fix first.
FAQ
Do I need to enroll devices in Intune to use app protection policies?
No. App protection policies work at the app level, so personal and unenrolled phones can be covered. Microsoft designed them to separate work data from personal data without managing the device. The user still needs an Entra account, an Intune license and membership in a targeted group.
Is MAM the same as an app protection policy?
Not exactly. MAM, Mobile Application Management, is the approach of applying controls to apps rather than devices. App protection policies are the rule sets you create to do it. When people say "Intune MAM policies," they almost always mean app protection policies.
What do I need for Conditional Access to require app protection?
You need Microsoft Entra ID P1 or P2 licenses and a broker app: Microsoft Authenticator on iOS or Company Portal on Android. Then you add a Conditional Access policy that uses the require app protection policy grant. Pilot it first with a small group.
Which apps can app protection policies cover?
Microsoft 365 apps such as Outlook, Teams, Word, Excel and Edge are supported, along with partner apps, per Microsoft's supported apps list. Check the list for any third-party or line-of-business app before you rely on it. An unsupported app cannot enforce the policy.
Sources
- App Protection Policies Overview, Microsoft Learn
- Add, Configure, and Protect Apps with Intune, Microsoft Learn
- Review Unenrolled BYOD MAM, Zero Trust Assessment workshop
- Frequently asked questions about MAM and app protection, Microsoft Learn
- Supported Microsoft Intune Apps, Microsoft Learn
- Require local client device security compliance for Windows App, Microsoft Learn
- Review App Protection Policy Logs, Microsoft Learn
- Create and Deploy App Protection Policies, Microsoft Learn
- Use app-based Conditional Access policies with Intune, Microsoft Learn
- Conditional Access: require approved app or app protection policy, Microsoft Learn
