10.6 Capabilities: You do not have approval to use the following restricted capabilities
This comes in the certification report and names the capability, like "You do not have approval to use the following restricted capabilities: packageManagement", followed by "Please remove this capability from your application and resubmit."
What it means
Policy 10.6 says the capabilities you declare must relate to what your product does, follow Microsoft's capability declarations and not get around the operating system's checks.
Restricted capabilities need approval, which you ask for on the Submission options page. Microsoft says some are very rarely approved. In the GitHub issue, PWABuilder put packageManagement, which lets an app manage other apps, in the packages it made. Partner Center warned about it at upload, and the Store later failed the apps.
How to fix it
- Find the capability in your manifest's
Capabilitieselement. Restricted ones use therescapprefix. Microsoft says not to declare them unless your app truly needs them, so remove it if you can. - If a packaging tool added it, rebuild once the tool stops adding it. PWABuilder removed packageManagement and said regenerated packages would avoid the rejection. The developer who unzipped the bundle and edited the package by hand had it rejected. Our PWA guide covers packaging.
- If the app needs the capability, say why and how it uses it under Restricted capabilities on the Submission options page, with as much detail as you can. The runFullTrust page has an example.
- Create a new submission with packages that don't declare the capability, or with the explanation filled in.
Sending the fixed update with StoreFast
StoreFast can send your next update to Partner Center from a dashboard, CI or a coding agent. There's a free plan, and connecting Partner Center starts 14 days of Plus with no card.
Sources
Facts about Microsoft's tools were checked against these pages on November 13, 2026.