Other features or issues related to Microsoft Partner Center
Email [Email] to request a manual certification review and release of the locked product state; there is no documented publisher-side procedure for unlocking Update product after an enforcement removal.
Request the manual review
Send one consolidated appeal rather than opening more duplicate Engage Center tickets. Microsoft identifies this mailbox for questions about an app’s review or certification status and for specific certification failures.^1^^2^
Include:
- Product/app ID and exact product name.
- Submission ID, if one appears in Partner Center.
- Removal date: November 6, 2026.
- The complete Policy 10.2.6 notice or certification report.
- Existing Engage Center case numbers, noting that they remain unanswered.
- A screenshot showing Update product disabled.
- Package type and version.
- A concise explanation that the reviewed build contains no:
- on-device cryptocurrency mining;
- cryptocurrency wallet or trading functionality;
- remote management of cryptocurrency mining.
- A dependency list or software bill of materials, plus the package hash, if available.
- A specific request to:
- manually review the flagged package and identify the binary, dependency, behavior, or metadata that triggered 10.2.6;
- overturn or clarify the enforcement decision;
- restore submission access or explain the required remediation.
Policy 10.2.6 prohibits on-device mining. Wallets, trading platforms, and remote-management cryptocurrency apps are permitted only under a Company account; products that merely display public keys and associated transactions are allowed.^1^
Suggested message:
Subject: Manual review requested — Policy 10.2.6 removal and locked Update product
Product name: [name]
Product ID: [ID]
Submission ID: [ID, if available]
Removal date: November 6, 2026
Existing support cases: [case numbers]The product was removed for Policy 10.2.6, and Update product is disabled. A review of the codebase and dependencies found no on-device cryptocurrency mining, wallet/trading functionality, or remote mining management. Unknown third-party SDKs have also been removed.
Please manually review the flagged package and identify the specific binary, dependency, behavior, or listing metadata that triggered this policy. If the finding is overturned, please release the enforcement state so an updated build can be submitted. Attached are the removal notice, locked-control screenshot, dependency inventory, package version, and package hash.
If Microsoft sent a certification/removal email that accepts replies, reply to that message with the same information and reference the separate appeal. Replying to the certification report is explicitly documented for MSI/EXE submissions; the general Store policy establishes the certification mailbox for Store products broadly.^3^
Track the cases already opened
Since multiple Engage Center tickets already exist, do not create more unless Microsoft requests it:
- Sign in to Partner Center with the work account used for publishing.
- Select Help (?).
- Select View my support requests.
- Open each existing case and add the appeal details above if the case interface permits updates.^4^
If the problem is specifically that Engage Center itself is not showing or updating the cases, select its question-mark icon, then use How can we help? to report that platform problem. This is Engage Center platform assistance, not a substitute for the Store certification appeal.^5^
After Microsoft releases the lock
Only after Update product becomes available:
- Rebuild the cleaned package and increase its package version.
- Retest the exact release artifact.
- Create the updated submission.
- In Notes for certification, reference the appeal/case number and explain the dependency changes.
- Submit the new package for certification.
Microsoft’s general submission guidance requires fixing the reported policy issue, rebuilding and retesting, and increasing the replaced package’s version before resubmission.^6^
The certification mailbox can review the decision and status, but the documentation does not guarantee that emailing it will automatically unlock Update product. The request should explicitly ask Microsoft either to release the enforcement state or provide the exact prerequisite for doing so.
References
- Microsoft Store Policies version 7.20 - Windows apps | Microsoft Learn
- Help and guidance for Windows developers
- The app certification process for MSI/EXE app
- Support for Microsoft Marketplace program in Partner Center
- Microsoft Engage Center help
- Fix Microsoft Store submission and certification failures