Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

4.1.6. App Control for Business

💡 First Principle: Antivirus asks "is this file known to be bad?"; App Control asks "is this file known to be allowed?" Flipping from a block list to an allow list stops malware nobody has seen yet — and also stops every legitimate app you forgot to allow. So the real work is choosing trust sources that keep the allow list current without someone maintaining it by hand.

What it is. App Control for Business — formerly Windows Defender Application Control (WDAC) — is an endpoint security policy that uses the Windows ApplicationControl CSP. Don't confuse it with the ASR Application control profile, which uses the older AppLocker CSP: Windows still supports AppLocker but no longer develops it, and the legacy Application Control profiles are slated for deprecation. Supported devices include Windows 10 Enterprise or Education 1903 or later, Windows 11, Windows Pro with the November 2022 updates, and Azure Virtual Desktop. On co-managed devices, the Endpoint Protection workload must be set to Intune.

One scope rule surprises people: App Control policies apply only to the device scope. Target a group containing users and only those users' devices receive the policy.

Building a policy. Go to Endpoint security > App Control for Business > App Control for Business tab > Create Policy. Apps not explicitly allowed are blocked — unless the policy is in audit mode, which allows everything and logs what would have been blocked. You configure it in one of two formats: paste custom XML, or use built-in controls, which combine trust sources:

Trust sourceWhat it allowsWatch out for
Windows components and Store appsThe OS and Microsoft Store apps (Enabled by default; can be set to Audit only)Covers nothing you deploy yourself
Apps with a good reputationFiles the Microsoft Intelligent Security Graph (ISG) considers trustworthyReputation-based, not a fixed list
Apps from managed installersAnything installed by a tagged installer such as the Intune Management ExtensionNo retroactive tagging
Supplemental policySpecific apps you add in XMLMust reference one base policy's Policy ID

Supplemental policies extend a base policy without replacing it. Each must be XML, must reference the base policy's Policy ID and extends exactly one base, though several supplementals can extend the same base. Assign them to the same groups as the base. You author the XML with the App Control Wizard or PowerShell. Multiple base and supplemental policies on one device are supported, and the old limit of 32 active policies is gone on patched Windows 10 1903 and later.

The managed installer. When the Intune Management Extension is set as a managed installer, an AppLocker rule tags every app it installs as trusted, so an App Control policy that trusts managed installers lets your Intune-deployed apps run automatically. The configuration moved in August 2025: the old single tenant-wide opt-in was replaced by managed installer policies you assign to selected groups (Endpoint security > App Control for Business > Managed installer tab > Create). Existing tenant-wide setups were converted to a policy targeting all devices. Enabling a managed installer requires the Intune Administrator role.

Three managed installer behaviors cause real outages:

  • No retroactive tagging. Apps deployed before the managed installer was enabled aren't tagged and need explicit allow rules. The tag also does nothing on its own; it only matters to an App Control policy that trusts it.
  • Empty AppLocker collections. Enabling the managed installer deploys an AppLocker policy with a dummy rule. If a device already has an AppLocker rule collection set to NotConfigured with no rules, that collection becomes enforced — apps can fail and devices can even fail to boot or sign in. Remove such collections first.
  • Hybrid joined devices need domain controller connectivity for the managed installer policy to apply, which often fails during Autopilot. Microsoft prefers Entra join, or deploying apps after provisioning.

Rolling out and removing. Microsoft recommends enabling the managed installer early, then deploying new policies in audit mode and reviewing the audit events with advanced hunting before enforcing. Removal needs care too: deleting a policy in Intune removes it from devices, but enforcement remains until the next reboot. To back out cleanly, deploy an "allow all" policy first, then delete. Policy reports show per-setting status (Success, Error, Conflict), and managed installer reports can take up to 24 hours to update.

⚠️ Exam Trap: Turning on the managed installer doesn't make existing apps trusted. Tagging starts from the moment it's enabled; apps installed earlier — even by Intune — aren't tagged and need explicit allow rules (for example a supplemental policy) before you enforce.

Reflection Question: You enforce an App Control policy that trusts Windows components and managed installers. A line-of-business app Intune deployed last year is blocked, while one deployed yesterday runs. Explain why, and name two ways to fix it.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned