Remove Default Windows Store Apps using Microsoft Intune

This document outlines the requirements, methods, and limitations for an IT administrator to remove pre-installed Microsoft Store apps (also known as inbox apps or bloatware) from Windows devices managed by Microsoft Intune.

1. Requirements

The requirements vary depending on the chosen method for removal. Microsoft now offers a native policy approach, but older methods (PowerShell or individual app assignments) are still available.

Feature / Method	Windows OS Requirement	Intune/License Requirement	Deployment/Timing
New Native Policy Method (Recommended for supported OS)	Windows 11, version 25H2 (or later, specifically Enterprise or Education editions).	Microsoft Intune subscription with appropriate licensing.	Policy should be applied before the first user sign-in for full effect on new profiles. For existing users, they must sign out and sign back in.
PowerShell Script (Custom Method)	Windows 10/11	Microsoft Intune subscription.	Deploy the script as a Win32 App or a PowerShell script policy. Should be configured to run in the System context and before the first user signs in for system-wide removal (`Remove-AppxProvisionedPackage`).

2. Native Policy Method: Remove Default Microsoft Store Packages

This method uses a dedicated Windows policy (available via Settings Catalog or Custom OMA-URI) for a cleaner, supported removal of a curated list of inbox apps.

Configuration (Settings Catalog)

Navigate to Devices > Windows > Configuration profiles.
Click Create profile > Platform: Windows 10 and later, Profile type: Settings catalog.
In Configuration settings, search for “Remove Default Microsoft Store packages from the system”.
Enable the setting.
Select True for each app in the list you wish to remove (e.g., Microsoft Solitaire Collection, Bing Weather).
Assign the policy to your target device group.

Configuration (Custom OMA-URI – for environments without Settings Catalog support or before the setting is available)

Navigate to Devices > Windows > Configuration profiles.
Click Create profile > Platform: Windows 10 and later, Profile type: Templates.
Templates window: Click Custom and then select Create.
Name and Discription“Remove Default Microsoft Store packages from the system”.
Configuration settings >

Setting	Value
Name	`Remove Default Microsoft Store Packages`
Description	Optional
OMA-URI	`./Device/Vendor/MSFT/Policy/Config/ApplicationManagement/RemoveDefaultMicrosoftStorePackages`
Data Type	`String`
Value	`<enabled/><data id="[PackageNameID]" value="true"/><data id="[AnotherPackageNameID]" value="true"/>` Note: This XML value requires the specific `id` for each app you want to remove. Setting `value="true"` removes the app.

Available values

<enabled/>
<data id="WindowsFeedbackHub" value="false"/>
<data id="MicrosoftOfficeHub" value="false"/>
<data id="Clipchamp" value="false"/>
<data id="Copilot" value="false"/>
<data id="BingNews" value="true"/>
<data id="Photos" value="false"/>
<data id="MicrosoftSolitaireCollection" value="true"/>
<data id="MicrosoftStickyNotes" value="true"/>
<data id="MSTeams" value="false"/>
<data id="Todo" value="false"/>
<data id="BingWeather" value="true"/>
<data id="OutlookForWindows" value="false"/>
<data id="Paint" value="false"/><data id="QuickAssist" value="false"/>
<data id="ScreenSketch" value="false"/>
<data id="WindowsCalculator" value="false"/>
<data id="WindowsCamera" value="false"/>
<data id="MediaPlayer" value="false"/>
<data id="WindowsNotepad" value="false"/>
<data id="WindowsSoundRecorder" value="false"/>
<data id="WindowsTerminal" value="false"/>
<data id="GamingApp" value="true"/>
<data id="XboxGamingOverlay" value="true"/>
<data id="XboxIdentityProvider" value="true"/>
<data id="XboxSpeechToTextOverlay" value="true"/>
<data id="XboxTCUI" value="true"/>

3. Custom PowerShell Script Method (Legacy/Fallback)

This is a common method for older Windows versions or apps not supported by the native policy, but it is not the officially supported method and can sometimes lead to issues.

Identify the PackageFamilyName of the app(s) to remove (e.g., Microsoft.BingWeather_8wekyb3d8bbwe).
Create a PowerShell script using commands like Get-AppxProvisionedPackage -Online | Where-Object DisplayName -like "*Name*" | Remove-AppxProvisionedPackage -Online.
Deploy the script via Devices > Scripts or as a Win32 App with an uninstall command.
Ensure the script is configured to run in the System context.

5. Limitations and Considerations

Category	Limitation / Consideration	Details
Windows Version/Edition	Native Policy Restriction: The new native removal policy is officially supported only on Windows 11 Enterprise/Education, version 25H2 and later.	Using the native policy on Pro editions or older Windows versions may not work or is unsupported.
User Scope vs. Device Scope	Timing & Existing Users: The native policy primarily prevents provisioning for new user profiles and is a device-level setting.	For existing users, apps are typically removed only after they sign out and sign back in after the policy applies.
Apps Not Removable	Microsoft Edge: Microsoft Edge is often a notable exception and cannot be removed using these methods.	Other third-party OEM applications (bloatware) are also generally not covered by the native Microsoft policy and still require custom scripts or third-party tools.
App Reinstallation	Users can reinstall: End-users can often re-install removed apps from the Microsoft Store unless the Store itself is blocked or restricted via policy.	To completely prevent reinstallation, you must block the Microsoft Store, or use AppLocker/Windows Defender Application Control (WDAC).
PowerShell Script Risks	Unsupported Method Risk: Using custom PowerShell scripts (especially `Remove-AppxProvisionedPackage`) is generally unsupported by Microsoft and carries the risk of breaking Windows functionality or future updates.	Always test custom scripts thoroughly in a lab environment.
Conflict Management	Multiple Policies: Avoid applying both a Group Policy Object (GPO) and an Intune (MDM) policy for app removal to the same device, as this can lead to unpredictable conflicts.	Choose a single method of management for this setting.