Win32 Requirement Rule Builder
Browser-onlyRequirements decide whether an app is even applicable to a device. Build them here, export Graph-ready JSON, and test whether a described device would satisfy them.
Hardware and OS
File requirement (optional)
Registry requirement (optional)
Script requirement (optional)
How it works
Configure hardware and OS requirements, and optionally a file, registry or script
requirement. The builder produces JSON you merge into a win32LobApp when you
create or update it with Microsoft Graph.
Hardware and OS requirements map to properties on the app object
(applicableArchitectures, minimumSupportedWindowsRelease,
minimumFreeDiskSpaceInMB, minimumMemoryInMB,
minimumNumberOfProcessors, minimumCpuSpeedInMHz). File, registry
and script requirements map to entries in the rules array with
ruleType: requirement.
Test on a device
The Test on a device tab simulates whether a device would meet your requirements. Enter the device's architecture, Windows release, free disk space, memory, processor count and CPU speed, and it reports pass or fail for each. File, registry and script requirements are evaluated on the actual device, so they are reported as not simulated rather than guessed.
Supported scenarios
- Gating an app on a minimum Windows release such as Windows 11 23H2.
- Requiring minimum hardware so a heavy app is not deployed to underpowered devices.
- Checking a requirement set against a device profile before you deploy.
Common problems
- Requirements gate applicability, not detection. A requirement that passes while detection fails causes repeated install attempts.
- An architecture requirement of x86 marks the app not applicable on x64 devices; use x64 unless the app is genuinely 32-bit only.
- A script requirement must exit 0 and write a value to STDOUT to pass.
Related
Detection Rule Generator · Win32 App Health Checker · Guide: Win32 apps · All tools