The Application User Model ID (AUMID) is the identifier Windows uses to recognise a UWP app — and you’ll need it any time you want to launch one programmatically, pin it to the Start menu via Intune, target it in AppLocker, or surface a toast notification from the right “owner” application. The challenge is that this identifier is rarely visible in the UI, varies between OEM-installed apps and re-published store apps, and can change after an upgrade. This post documents the three reliable ways I retrieve the AUMID in production, plus how to use them in Intune assignments.
The AUMID is an ID which is assigned to each application installed on a device. It is used e.g. in the Kiosk multi app mode to select apps. Which possibilities exist to get this AUMID I want to explain you in this blog.
Why the Application User Model ID (AUMID) matters
Before we walk through the methods, it helps to understand what the Application User Model ID (AUMID) actually represents. For packaged (UWP/MSIX) apps the AUMID is built from the Package Family Name combined with the application ID declared in the app manifest, separated by an exclamation mark — for example Microsoft.WindowsCalculator_8wekyb3d8bbwe!App. For classic desktop apps the value is usually a relative path to the application’s shortcut. Because the format differs between app types, copying the value verbatim instead of guessing it is the only safe approach when you author Intune policy. Microsoft documents the underlying concept in detail on Microsoft Learn.