5.2.2. Conditional Access for App Protection
💡 First Principle: An app protection policy only protects apps that receive it. A user who reaches Exchange Online through an unmanaged mail app simply walks around it. Conditional Access closes that gap by making app protection a condition of access: no protected app, no data. Think of app protection as the rules inside the building and Conditional Access as the door that only admits people following them.
The grant you use now. Conditional Access has offered two app-focused grant controls: Require approved client app and Require app protection policy. The approved client app grant was retired on June 30, 2026 (after an extension from March 2026). On that date the control — and any policy that includes it — became read-only: you can no longer create or edit policies that use it, but you can disable or delete them, and existing enabled policies keep being enforced. New policies should use Require app protection policy alone. Microsoft's migration guidance, written for the run-up to the retirement, was to change such policies to "Require approved client app or Require app protection policy" (Require one of the selected controls) and test them in Report-only mode. Now that the control is read-only, the practical route is to create a replacement policy that uses Require app protection policy, test it in Report-only mode, then disable or delete the old one. Creating or editing Conditional Access policies needs at least the Conditional Access Administrator role.
The mobile template. Microsoft's template targets All users (excluding break-glass accounts), All resources, and device platforms Android and iOS, with the app protection grant.
What has to be on the device. Require app protection policy needs the device registered through a broker app: Microsoft Authenticator on iOS or Company Portal on Android. Users without the broker are redirected to the app store to install it. If an app doesn't support the app protection grant, its users are blocked. Supported apps include Edge, Excel, Word, PowerPoint, Outlook, OneDrive, OneNote, Teams, SharePoint, Loop, Power BI, Viva Engage and Windows App.
Windows and Edge. A separate template protects browser access from personal Windows devices. It targets Office 365 resources, the Windows device platform and the Browser client app, and grants on Require app protection policy or Require device to be marked as compliant (Require one of the selected controls). That "or" matters: if you require only app protection, or use "Require all", target only unmanaged devices, or MDM-managed devices are blocked from every app. The policy applies to Microsoft Edge on Windows 11 (and on Windows 10 20H2 or later with the required update). The user experience is a prompt to switch Edge profile and sign in with the work account; at the MDM enrollment prompt the user should choose No, because Yes enrolls the device in MDM instead of MAM. Microsoft also recommends a second policy that blocks unsupported or unknown device platforms, so nobody slips through on a platform the template doesn't cover.
Why apply app protection first. If you switch on the Conditional Access policy before users have received their app protection policy, the grant fails and they're blocked. Assign app protection, let it reach users, then enforce.
⚠️ Exam Trap: "Require approved client app" still appears in older study material, but it's not the answer for a new policy. It was retired on June 30, 2026: existing policies that use it still enforce but are read-only, and new policies use Require app protection policy. If an answer option tells you to create a policy with the approved client app grant, it's wrong — that's no longer possible.
Reflection Question: A company's existing Conditional Access policy for iOS uses only "Require approved client app", and a new requirement asks you to add Android to it. Why can't you just edit the platform list, and what should you build instead?