The Windows Taskbar Policy in Swif allows administrators to centrally control which applications are pinned to the Windows taskbar across managed devices. By defining a consistent taskbar layout, organizations can standardize user environments, improve productivity, and ensure quick access to critical applications.
What the Taskbar Policy Does
Pin Applications: Specify the exact set of applications that should appear on the Windows taskbar.
Support for Multiple App Types: Works with both Universal Windows Apps (UWA) and traditional Desktop Applications.
Consistent User Experience: Ensures all users within a device group see the same taskbar shortcuts.
Automated Deployment: Once applied, devices automatically update their taskbar layout according to the policy.
Requirements
The Windows Taskbar Policy is supported on the following editions:
Windows Pro 10+
Windows Enterprise 10+
Windows Education 10+
Windows SE 10+
IoT Enterprise / IoT Enterprise LTSC 10+
How to Configure
Navigate to Policy Creation
Go to Device Management → Policies.
Click Create New Policy and select Windows Taskbar Policy.
Enter Basic Information
Provide a Policy Name (e.g., “Windows Taskbar Policy”).
Review the Policy Description for supported app types.
Add Applications (App IDs)
For UWA apps: use
AppUserModelID(e.g., “app!” prefixed IDs).For Desktop apps: use
DesktopApplicationID(full executable name or path).Example:
AppUserModelID:Microsoft.Office.Word_8wekyb3d8bbwe!AppDesktopApplicationID:C:\\Program Files\\Mozilla Firefox\\firefox.exe
Apply the Policy
Assign the policy to the desired devices or device groups.
Click Continue and complete the review process.
Applying & Refreshing
A device reboot may be required for pinned apps to appear.
Alternatively, you can refresh the shell by restarting Explorer:
CMD:
taskkill /f /im explorer.exe && start explorer.exe
PowerShell:
Stop-Process -Name explorer -Force; Start-Process explorer
Common App IDs for Taskbar Pinning
Here are some frequently used AppUserModelID and executable paths for common business applications:
Application | Type | Example App ID / Path |
Microsoft Edge | UWA |
|
Google Chrome | Desktop App |
|
Mozilla Firefox | Desktop App |
|
Microsoft Word | UWA (Office 365) |
|
Microsoft Excel | UWA (Office 365) |
|
Microsoft PowerPoint | UWA |
|
Microsoft Teams | UWA |
|
Outlook (Office 365) | UWA |
|
Windows Terminal | UWA |
|
File Explorer | System App |
|
Notepad | Desktop App |
|
Calculator | UWA |
|
⚠️ Note: App IDs can differ between Windows versions or Office distribution types (e.g., Office 365 vs. perpetual Office installs). Always test IDs in your environment before broad deployment.
🔎 How to Find an AppUserModelID (AUMID)
Use one of the methods below to retrieve the AUMID for UWP/Microsoft Store apps. For classic Win32 apps, use the executable path (see the Desktop Apps section).
Method 1 — PowerShell (fastest)
Open PowerShell.
List all Start apps and their AUMIDs:
Get-StartApps | Sort-Object Name | Format-Table Name, AppID -Auto
Filter by name:
Get-StartApps | Where-Object Name -match "Edge|Calculator|Teams" | Format-Table Name, AppID -Auto
(Optional) Export for easy search:
Get-StartApps | Sort-Object Name | Export-Csv "$env:USERPROFILE\Desktop\StartApps.csv" -NoTypeInformation
The value in AppID is the AUMID you can paste into the Taskbar Policy.
Method 2 — Shell “AppsFolder” (no scripting)
Press Win + R, type
shell:Appsfolder, press Enter.Find the app, right-click → Create shortcut (confirm to create on Desktop).
On the Desktop, right-click the shortcut → Properties.
In Target, you’ll see something like:
shell:Appsfolder\Microsoft.WindowsCalculator_8wekyb3d8bbwe!App
The text after the last backslash is the AUMID (here:
Microsoft.WindowsCalculator_8wekyb3d8bbwe!App).
Method 3 — From Appx manifest (advanced)
Get the package family name:
Get-AppxPackage -Name *WindowsCalculator* | Select-Object -Expand PackageFamilyName
Open the app’s
AppxManifest.xmlto find the<Application Id="...">.Build the AUMID as:
<PackageFamilyName>!<Application Id>
🖥 Finding the Path for Desktop (Win32) Apps
For non-Store apps, pin using the executable path.
Start menu → Right-click app → More → Open file location → Properties → Target (copy the full path).
Or use the command line:
where.exe chrome where.exe firefox
Quote paths with spaces, e.g.:
"C:\Program Files\Google\Chrome\Application\chrome.exe"
Tip: 32-bit apps on 64-bit Windows may live under C:\Program Files (x86). Ensure the path points to a build installed for all users if you want universal pinning.
Summary
The Windows Taskbar Policy helps IT teams create a consistent, productivity-focused Windows environment by managing pinned taskbar applications centrally. With support for both UWA and desktop applications, and reference IDs for common tools, you can ensure that every managed device provides the right apps, right where users need them.