Flamingo Raises $4.5M Seed Round

Skip to content

WDAC: App Control for Business and allowlisting on Windows

Security
Technology
IT Operations
Aliaska VarievaAliaska Varieva
September 30, 2026
793 views
WDAC: App Control for Business and allowlisting on Windows

Includes a table of where each WDAC name appears in tools and logs, an Intune vs Group Policy comparison, a six-step Intune rollout, trust rules for Office and Teams, policy versioning with Set-CIPolicyVersion, and a rollback plan that covers signed policies.


Updated: November 2026

WDAC, short for Windows Defender Application Control and now called App Control for Business, flips the antivirus default on Windows: nothing runs unless your policy allows it. That covers executables, DLLs, drivers, scripts and installers, and Microsoft recommends it over AppLocker wherever you can use it. This guide is for MSPs and internal IT teams rolling it out across tenants and fleets, from the first audit-mode policy to Intune deployment, version control and a safe rollback.

TL;DR

  • WDAC is App Control for Business. Same feature, new name: only code the policy allows can run.
  • Prefer it over AppLocker. Keep AppLocker for per-user rules on shared PCs.
  • A base plus supplementals. One strict base for every device, one supplemental per app or team.
  • Audit first. Turn event 3076 and 8028 hits into rules before you enforce.
  • Deploy with Intune where you can. Group Policy only handles single-policy format.
  • Version every policy. Keep the XML in a repository and bump the version on each change.
  • Replace before you delete. Roll back with an allow-all policy, and give signed policies a signed replacement.

What is WDAC?

WDAC stands for Windows Defender Application Control. Microsoft now calls it App Control for Business, and the old name still shows up in the wizard, in Intune and in half the forum threads you'll read. It's the same feature.

It changes one default. Normally Windows runs any code unless your antivirus flags it. With an App Control policy, code runs only if the policy allows it. That covers executables, DLLs and drivers, plus scripts, MSI installers and PowerShell, which drops into Constrained Language Mode for anything the policy doesn't trust.

Policies apply to the whole device, not to individual users. It runs on Windows Pro, Enterprise and Education editions. Microsoft is clear that it doesn't replace antivirus software, so you keep both.

Windows Defender application control (WDAC) in tools and logs

The rename didn't reach every tool, so expect both names in one rollout. Here's where each shows up:

Where you lookWhat it's called
Microsoft Learn and the Intune admin centerApp Control for Business, under Endpoint security in Intune
The policy wizardApp Control Policy Wizard, installed as the Microsoft.WDAC.WDACWizard package
PowerShellConfigCI cmdlets such as New-CIPolicy and Set-CIPolicyVersion, plus CiTool.exe
Device managementThe ApplicationControl CSP; Intune's older Endpoint Protection and attack surface reduction profiles use the AppLocker CSP
Event ViewerCodeIntegrity > Operational, plus AppLocker > MSI and Script
Policy files on the deviceSiPolicy.p7b in single-policy format, {PolicyId}.cip in multiple-policy format

CI stands for code integrity, the part of Windows that enforces the policy. Whichever of these names a ticket uses, it's the same feature.

WDAC vs AppLocker vs Smart App Control

Windows ships three ways to control what runs. They overlap, so it helps to see them side by side.

App Control for Business (WDAC)AppLockerSmart App Control
Built forManaged business fleetsOlder or shared-PC setupsHome users and very small offices
ScopeWhole devicePer user or groupWhole device
Covers drivers and kernelYesNoYes
New featuresStill getting themSecurity fixes onlyConsumer feature
Managed byIntune, PowerShell, ConfigMgrGroup Policy, IntuneThe user, in Windows Security

Microsoft's own guidance is direct: if you can use App Control, use it over AppLocker. AppLocker still gets security fixes but no new features. It stays useful for one job App Control can't do, which is different rules for different users on a shared PC. You can run both, with App Control as the strict base and AppLocker tightening per-user rules on top.

Smart App Control is App Control with a fixed, cloud-reputation policy. It's the consumer version, and our guide on turning off Smart App Control covers why managed fleets swap it out. The good news is that its policy ships as an example you can start from, so you're not building from nothing.

This r/sysadmin thread from September 2026 is the question every pilot hits: the policy works, but is the upkeep worth it?

The top replies agree it goes quiet eventually. It gets there once you stop chasing every DLL and split the rules into an enforced base policy plus a supplemental policy per line-of-business app.

Base and supplemental policies

Since Windows 10 version 1903, a device can run several App Control policies at once. That's what makes the feature manageable.

A base policy sets the rules. If a device has two base policies, a file has to pass both to run. A supplemental policy extends one base policy with extra allow rules, and a file runs if the base or any of its supplementals allows it. The base needs rule option 17, Allow Supplemental Policies, for that to work.

The practical pattern is one strict base policy for every device, then one supplemental per app or per team. When the finance app updates, you edit its supplemental and leave the base alone. The old limit of 32 active policies per device is gone on Windows security updates released on or after April 9, 2024, except on Windows 11 21H2.

The rule options and file rules that matter

A policy has two parts: rule options, which switch behaviours on, and file rules, which say what you trust.

Five rule options do most of the work. Option 3, Audit Mode, logs what would be blocked without blocking it. Option 13 trusts apps installed by a managed installer, such as the Intune Management Extension. Option 14 trusts files with a good reputation in Microsoft's Intelligent Security Graph. Option 16 applies policy updates without a reboot, and option 17 allows supplemental policies.

File rules decide how specific each allow is. Publisher and FilePublisher rules trust a vendor's signing certificate, so updates keep working without policy changes. Hash rules match one exact file and break on every update. FilePath rules only work for folders that just admins can write to, which is why they fail in AppData.

App Control checks rules in a fixed order. Explicit deny rules come first, then explicit allow rules, then the managed installer tag, and the reputation check comes last. Use publisher rules wherever you can, path rules for admin-only folders, and hashes as the last resort.

Build a policy with the wizard

You don't write policy XML by hand. The App Control Policy Wizard, a free Microsoft tool, builds base and supplemental policies, sets rule options and merges policies.

Start from a template rather than an empty policy. Microsoft ships example policies in %windir%\schemas\CodeIntegrity\ExamplePolicies, including the Smart App Control policy. If you start from that one, remove the option Enabled:Conditional Windows Lockdown Policy first, as Microsoft's docs note.

For a reference machine with your standard apps installed, PowerShell can scan and build the policy:

powershell
New-CIPolicy -MultiplePolicyFormat -ScanPath "C:\Program Files" -UserPEs -FilePath .\base.xml -Level FilePublisher -Fallback SignedVersion,Publisher,Hash
Set-RuleOption -FilePath .\base.xml -Option 3   # audit mode
Set-RuleOption -FilePath .\base.xml -Option 17  # allow supplemental policies

More cmdlets like these are in our PowerShell commands guide.

Roll out in audit mode first

Every App Control deployment that goes smoothly starts in audit mode. Nothing gets blocked, and every would-be block gets logged.

The events live in two logs. Executables, DLLs and drivers go to Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational. Scripts and MSI installers go to the AppLocker > MSI and Script log. The IDs to watch:

  • 3076: the file would have been blocked if the policy were enforced (audit mode).
  • 3077: the file was blocked (enforce mode).
  • 3089: the signature details for a blocked file, matched to its 3076 or 3077 by Correlation ActivityID.
  • 8028 and 8029: the same audit and enforce pair for scripts and MSIs.

To pull audit hits on one PC:

powershell
Get-WinEvent -LogName "Microsoft-Windows-CodeIntegrity/Operational" |
  Where-Object Id -eq 3076 | Select-Object TimeCreated, Message -First 20

For scripts and MSIs, point the same command at Microsoft-Windows-AppLocker/MSI and Script and filter on 8028.

At scale, Microsoft points to Advanced Hunting in Defender for Endpoint, which queries these events across the fleet. Collect a couple of weeks of audit data, turn the hits into supplemental rules, then remove option 3 on a pilot ring. You can run the audit policy side by side with the enforced one while you test changes.

This walkthrough shows the Intune side of building an App Control for Business policy and testing it:

Deploy with Intune or Group Policy

In Intune, App Control lives under Endpoint security > App Control for Business. The built-in controls give you three switches: trust Windows components and Store apps, trust apps with a good reputation, and trust apps from managed installers. Each combination maps to a fixed base policy ID, and you add supplemental policies as uploaded XML.

Set the Intune Management Extension as a managed installer early. Apps you deploy through Intune afterwards get tagged as trusted. Tagging isn't retroactive, so anything installed before that needs explicit rules. Our Intune review covers where this fits with the rest of Intune.

Group Policy can deploy App Control too, but only single-policy format policies: one SiPolicy.p7b per device, with no supplementals. For Windows 10 1903 and later and Windows 11, Microsoft's Group Policy guide recommends another deployment method, and for multiple policies without Intune it points to the ApplicationControl CSP through the MDM Bridge WMI Provider.

Intune vs Group Policy for app control

IntuneGroup Policy
Policy formatMultiple-policy format: a base plus supplementalsSingle-policy format only
Windows versionsWindows 10 1903 and later, Windows 11Any, but Microsoft recommends another method from Windows 10 1903
DevicesEnrolled in Intune; Enterprise and Education, plus Pro with specific updatesDomain-joined
Managed installerOne Intune policy turns on the Intune Management ExtensionYour own AppLocker managed installer rule, plus the Application Identity service
Applying a changeWithout a restart, through the ApplicationControl CSPAt the next restart
Change historyIntune audit logsYour own change records

If you already manage client tenants in Intune, the first row settles it: a supplemental per line-of-business app needs multiple-policy format.

Removing a policy has one trap. Deleting it from Intune doesn't lift blocks until the next reboot, and a careless removal can stop a device from booting. Microsoft's fix is to push an allow-all version of the policy first, then delete it.

Intune WDAC deployment, step by step

Order matters more than any single setting, because the managed installer only tags apps installed after it's switched on. For each tenant:

  1. Turn on the managed installer. In the Intune admin center, go to Endpoint security > App Control for Business, open the Managed installer tab and create a policy with Enable Intune Managed Extension as Managed Installer set to Enabled. This step needs the Intune Administrator role.
  2. Create the base policy in audit mode. On the App Control for Business tab, select Create Policy, then pick built-in controls or upload your own XML. Built-in controls trust Windows components and Store apps by default and offer an Audit only mode.
  3. Add supplemental policies. Upload one XML per line-of-business app or team, each pointing at the base policy's ID.
  4. Assign in rings. Start with a pilot group of IT devices, then add a group per department or client site.
  5. Read the 3076 events. Turn the hits into supplemental rules until the audit log shows only what you expect.
  6. Enforce ring by ring. Move the pilot ring to an enforced policy first, and keep an audit policy on a test group for trying changes.

Microsoft's Intune App Control guide lists the editions: Windows 10 1903 and later and Windows 11 Enterprise and Education, plus Pro with specific updates. Staff who manage these policies need the App Control for Business permission in their Intune role. For MSPs, each client tenant gets its own copy of the base and supplementals, which is why the version control below matters.

Deploy Microsoft 365 apps and teams under app control

Office and Teams need their own trust rule, because neither stays inside the managed installer tag.

The Microsoft 365 Apps app type in Intune isn't installed by the Intune Management Extension, so the managed installer never tags it. Teams is provisioned with teamsbootstrapper.exe -p, which installs the Teams MSIX for every user on the device, and from then on Teams updates itself.

Both ship with Microsoft signatures, so trust the signer. Start the base from the AllowMicrosoft.xml example policy, which adds Microsoft's product root certificate to the DefaultWindows rules, or add a publisher rule in a supplemental. If you'd rather keep everything on the managed installer, package Microsoft 365 Apps as a Win32 app, which Microsoft also recommends for Autopilot devices on the Enrollment Status Page. Our Office Deployment Tool guide covers building that package.

Intune policy version control

Intune records who changed a policy; a repository keeps the copies you can go back to. Treat App Control XML like code:

  • Store it in a repository. Microsoft's App Control management guide recommends a version-controlled repository every admin can reach, such as GitHub, Azure Repos or SharePoint Online.
  • Bump the version on every change. Set-CIPolicyVersion writes the version into the XML, and the policy name, ID and version show up in App Control event data.
  • Set the PolicyID once. Keep it for the life of the policy. A separate ID for the audit and enforced versions is a common pattern.
  • Read the audit log. Tenant administration > Audit logs records who created, changed, assigned or deleted a policy and lists the properties that changed. Auditing can't be switched off, and Microsoft Graph returns two years of events.
powershell
Set-CIPolicyIdInfo -FilePath .\finance-supp.xml -PolicyName "Finance apps" -SupplementsBasePolicyID "{base PolicyID}"
Set-CIPolicyVersion -FilePath .\finance-supp.xml -Version "1.0.0.3"
git commit -am "Finance apps 1.0.0.3: trust the new PDF plugin publisher"

Across several tenants, Microsoft365DSC, an open-source project led by Microsoft engineers, can snapshot a tenant's configuration, compare two configurations and watch for drift, and it includes an IntuneAppControlForBusinessPolicyWindows10 resource. Its site also notes that Microsoft's Tenant Configuration Management APIs on Graph entered public preview in January 2026. The same habit works for every other Intune policy too.

How to roll back a bad Intune policy change

Rolling back in Intune means pushing the old settings again. Deleting a profile isn't a reliable undo on Windows: Microsoft's profile troubleshooting guide notes that some CSPs remove a setting when its profile goes and some keep it, which it calls tattooing.

For any policy, the order is the same:

  1. Find the change. Tenant administration > Audit logs shows who changed the policy and which properties moved.
  2. Restore the previous version. Edit the policy back to the copy in your repository, or upload the previous XML.
  3. Let it sync. A saved change notifies online devices, which can take from a moment to a few hours; offline devices pick it up at their next check-in.

App Control adds four rules on top of the allow-all swap above:

  • Turn off other deployment methods first. If a script or another tool also pushed the policy, it comes back unless you stop that too.
  • Give signed policies a signed replacement. Deploy a signed policy with option 6, Enabled:Unsigned System Integrity Policy, the same PolicyId, an equal or higher version and an UpdatePolicySigners section, then restart. Skipping the restart causes a boot failure.
  • Remove locally on Windows 11. From the Windows 11 2022 Update, CiTool.exe -rp "{PolicyId GUID}" -json removes a policy, and from the Windows 11 2024 update unsigned policies go without a restart.
  • Check before offboarding. Microsoft warns that unenrolling a device with App Control policies, or removing them, can cause boot stop failures, so follow the removal steps before a client leaves.

If a device won't boot, Microsoft's removal guide has you choose Disable Driver Signature Enforcement in Advanced Boot Options, which suspends code integrity checks for one boot, then remove the policy by script. Signed policies also need Secure Boot off first, which can bring up BitLocker recovery. Rule option 10, Boot Audit on Failure, drops an enforced policy into audit mode when a boot-critical driver fails, so set it before you enforce.

What breaks, and how to fix it

Four things cause most App Control tickets.

Unsigned line-of-business apps have no publisher to trust. Ask the vendor to sign them, or fall back to hash rules and accept updating them with every release.

Self-updating apps come back untagged. The managed installer tag only lands on files written by the installer or a process it started. An app that updates itself through its own updater needs a publisher rule.

Apps that install into AppData fight FilePath rules. App Control ignores path rules for folders standard users can write to, because that's an easy bypass. You can switch that check off with option 18, but you're accepting the risk.

Scripts are the fourth. PowerShell scripts that aren't trusted run in Constrained Language Mode instead of failing outright, so they break in odd ways. Sign your admin scripts, or allow them by publisher.

When not to use WDAC

App Control is worth it where apps are managed and users aren't local admins. It's a hard fit in a few cases.

Shared PCs that need different rules per user are an AppLocker job. Fleets where every user installs their own software will drown in audit events. And if nobody owns the policy, it rots: the first blocked update gets "fixed" by switching enforcement off.

Check your fleet before you start. OpenFrame can run the Get-WinEvent check above as a script across a client's devices and collect the 3076 counts in one place, which shows how noisy enforcement would be.

Flamingo, which publishes this guide, builds OpenFrame, open, AI-native infrastructure for IT and security with AI agents working inline. It covers large areas of RMM, patching and MDM and sits alongside App Control and your EDR rather than replacing them. It costs $1 per device a month, including 10M AI tokens, with a 14-day free trial.

The short version

WDAC, now App Control for Business, lets only approved code run. Use it over AppLocker unless you need per-user rules, build one strict base policy plus supplementals, prefer publisher rules, and stay in audit mode until the 3076 events go quiet. On Intune, turn on the managed installer first, keep every policy version in a repository, and replace a policy before you delete it. If admin rights are the bigger gap on your fleet, read our guide to endpoint privilege management next.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/wdac

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions