Content reviewed: 12 October 2026
Intune MAM can protect work data on a personal phone without taking the whole device into MDM. It requires a supported app, user entitlement and correctly assigned protection; enforcing access also needs the appropriate Entra entitlement. Mobile apps and Edge on Windows have different prerequisites.
An administrator can assign app protection and enable Conditional Access, yet still see “policy not found” on the phone. A Reddit report describes this with Business Premium. Its comments suggest several causes without establishing a single diagnosis. Check app protection, access evaluation and device management separately.
MAM, MDM and identity registration are different
MDM manages device configuration, state and supported device actions. MAM protects work data in a supported app, such as limiting transfers to personal apps, requiring a work-context PIN or selectively removing corporate data. Microsoft documents MAM without enrollment for Android, iOS/iPadOS and Windows.
For Require app protection policy, Microsoft lists Authenticator on iOS and Company Portal on Android. The Intune overview requires Android Company Portal to receive app protection policies. Do not copy a different broker list from an older approved-client guide. Entra device identity registration is not full MDM enrollment; the current MAM overview explicitly requires it for Microsoft 365 apps on Android.
| Requirement | MAM without MDM | Device management via MDM |
|---|---|---|
| Protect work data in supported Outlook or Teams | Yes, according to app support and policy | Yes, often combined with MAM |
| Set operating-system and device-compliance rules | No | Yes, within platform and enrollment limits |
| Remove only work data from a protected app | Yes, with selective MAM wipe | Also possible in managed-device scenarios |
| Factory-reset a personal phone | Not through MAM alone | Only where the managed-device scenario permits it |
| Manage a userless company kiosk | Not as the only management method | Usually, depending on the device type |
App, platform and access-path support determine the actual protection. Selective MAM wipe targets work data in protected apps; full-device wipe is a different MDM action.
Which licences do you need?
For a user who benefits from Intune app protection policies, verify entitlement to Microsoft Intune Plan 1 or the corresponding package. Intune Licensing Documentation states that a license is needed by a user or device that directly or indirectly benefits from the service; the device license itself without user assignment does not cover the app protection policy. If you want to enforce access via Conditional Access, also check the Microsoft Entra ID P1 or P2 permissions for the affected users. App-based Conditional Access documentation lists P1/P2 as a prerequisite.
Business Premium includes Intune Plan 1 and Entra ID P1. Check assignment to every targeted person, including external collaborators. Basic MAM does not by itself require Intune Suite; advanced features have separate requirements.
Protect the app before enforcing access

This rollout order reduces the risk of locking pilot users out of email:
- Choose scenarios and platforms. For example, Outlook and Teams on personal iPhones and Android phones. Include web access and other email clients in the inventory.
- Check licences and groups. A test user needs the relevant entitlements and membership of both the MAM and Conditional Access target groups. Test work and personal accounts on the same phone.
- Create an app protection policy for each platform. Configure protected apps, data transfer, saving copies, access conditions and loss-of-access behaviour. Microsoft documents the setup separately for iOS/iPadOS and Android.
- Test the app first. Sign in to a supported Outlook or Teams version and confirm that protection applies before using blocking Conditional Access as the only test.
- Add Conditional Access in report-only mode. Target the right platforms, apps and client types; exclude emergency accounts and review sign-in logs. Enable the policy for the pilot group only after testing.
- Test an employee departure. Confirm access revocation and selective removal of work data. Tell users in advance what is removed and what remains theirs.
For a mix of managed and private phones, app protection policies can be targeted by device management status. One group of users does not automatically mean the same restrictions for both corporate and personal devices.
What changed in Conditional Access in 2026?
Older guides recommend the “Require approved client app” grant. Microsoft made it read-only on 30 June 2026. Existing policies can still apply, but administrators can no longer create or edit them. New policies should use “Require app protection policy”. Check each client before migration: an app that met the old approved-client requirement may not support the new grant.
The app-protection grant checks protection in the supported client. Inventory real clients and test the replacement before disabling the old policy. Do not assume that every formerly approved app supports app protection.
Windows BYOD has narrower limits
Windows MAM does not provide universal protection for desktop Outlook or every browser. The current Intune guide calls App Protection Conditional Access generally available, while the older Entra grant reference still labels Edge on Windows as preview. Do not repeat an old label from a single page without qualification. Confirm the actual feature, client and cloud before deployment; the guides also disagree about government-cloud availability.
Additionally, on Windows, MAM for Edge applies to unmanaged devices. If the device is already managed via MDM, MAM enrollment for this scenario will be blocked; when switching to MDM, MAM rules no longer apply. Microsoft therefore combines the option "Require app protection policy" or "Require device to be marked as compliant" in the model policy. If both are requested at the same time, some users could be blocked. Before deployment, also verify the desktop applications you want to enable or disable on your private PC, separately from Edge access.
Checks on a personal Windows PC
The current Windows APP settings require the device not to be Entra joined or MDM enrolled in any tenant. Workplace registration for no more than two other users alongside the MAM user gives a total limit of three. “Not in our Intune” is insufficient: another organisation may manage or join the PC.
The Windows MAM guide specifies supported Windows versions and Edge channels. Its Windows Security Center threat connector requires Windows 11 23H2, build 22631, or later. That is a component requirement, not a licence for every security feature. Windows 10 being allowed in Intune does not guarantee functionality after its ordinary support ended.
The Windows Conditional Access procedure separates account/MAM confirmation from a subsequent MDM consent prompt. Accidental MDM enrollment can block MAM on a personal device. For repeated prompts, inspect the work Edge profile, completed MAM enrollment and “this app only” choice. Do not start by removing all organisational accounts or device joins.
When Intune cannot find the policy
Do not assume the licence is the cause. Check, in order: the user’s Intune and Entra entitlements; membership of the MAM and Conditional Access groups; the policy’s platform and app targets; app support for protection policies; identity registration and the required broker app; and any other policy that may block sign-in first. In Intune troubleshooting, check policy applicability and status. In the Entra sign-in logs, inspect the evaluated Conditional Access policies and the grant result. “Policy did not apply” and “policy applied but its grant failed” are different problems.
In the pilot, record protected Outlook opening work data and blocking prohibited transfers. During departure testing, verify access revocation and the separate selective-wipe outcome after the app contacts the service. Record remaining offline limitations and test personal context separately.
Access revocation does not prove data deletion
Selective wipe creates separate requests for protected apps. The app must process the request; Microsoft says it must be opened and that processing can take up to 30 minutes. This is not guaranteed deletion from an offline phone within 30 minutes. During offboarding, check individual request outcomes rather than merely recording command submission.
Windows offline grace settings distinguish access blocking in minutes from wipe in days. Defaults of 720 minutes and 90 days are neither a mandatory company policy nor an immediate-deletion promise. Disabled-account actions also cannot be enforced when connectivity or authentication prevents account-state confirmation. Choose and test intervals for the work risk.
MAM cannot retroactively delete every copy outside protected context. For Outlook, Microsoft describes removal of contacts synced directly to the native address book, but not copies subsequently synced to an external source. Control exports and sharing before an employee leaves.
| Situation | Expected result and evidence |
|---|---|
| iPhone with work and personal accounts | Restrict work sharing and verify personal context separately |
| Android without Company Portal | Add the required component without accidentally enrolling into MDM |
| Windows PC Entra joined to another company | Does not meet the described unmanaged Windows MAM scenario |
| Offline phone after a wipe request | Monitor processing and offline controls; submission alone does not prove deletion |
Frequently asked questions
Must an employee enrol a personal phone in Intune MDM to use MAM?
No. MAM without MDM enrolment is supported. Mobile Conditional Access may still require device identity registration in Entra through a broker app; that is not full device management.
Can IT erase my personal photos through MAM?
A selective MAM wipe removes work data from protected apps; it does not factory-reset the phone. Employers should explain their exact BYOD policy and the type of registration requested.
Is Microsoft 365 Business Premium enough?
It includes Intune Plan 1 and Entra ID P1, relevant to basic MAM with Conditional Access. Check assignment to each affected user, app support and configuration. A licence alone does not prove the rollout works.
Can one policy cover mobile Outlook and Outlook Desktop?
Do not assume that from the name MAM. iOS and Android have their own supported apps and policies. The documented Windows Conditional Access scenario centres on Edge; assess desktop Outlook separately.
Should we delete the old approved-client-app policy?
Not without a pilot. It is read-only but may still apply. Inventory the clients, prepare the app-protection-policy grant, test it with a pilot group and then retire the old rule.
Does submitting a MAM wipe immediately erase work data on an offline phone?
No. Access revocation, offline controls and wipe processing are separate checks. Monitor each app’s results; submission alone does not confirm data removal.
What should the pilot deliver?
The result should be more than a configured policy. Record the permitted apps and platforms, each target role’s licence, work-data rules, Conditional Access test results and selective-wipe procedure. Tell users plainly that the company protects the work account and data inside the app; it does not automatically control the entire personal phone.
Related article: Intune: license for user or device








