Repository navigation
Certification rejected as "requires a working account" despite valid test account provided — extension uses enrolment-key auth, not a login screen #656
Description
Activity
Thank you for providing the detailed explanation.
Based on the information shared, it appears that your extension uses a device enrollment flow rather than a traditional username/password sign-in within the extension. To help the certification team validate the extension correctly, I recommend including these details directly in the Certification Notes section of your submission, along with clear step-by-step instructions describing how the extension should be authenticated, enrolled, and tested. If applicable, please also provide the enrollment key, test URL, sample workflow, or a screen recording demonstrating the enrollment process.
You can find guidance on providing information to reviewers in the certification notes here:
https://learn.microsoft.com/en-us/microsoft-edge/extensions/publish/publish-extension#step-8-enter-certification-testing-notes-and-submit-the-extensionWhen resubmitting, please ensure the review notes clearly state that:
- The extension does not contain an in-extension username/password login screen.
- The provided portal credentials are intended for accessing the web dashboard only.
- The extension is authenticated through a device enrollment key and not through user login credentials.
- Detailed steps are included for reviewers to successfully enroll and test the extension.
Providing this information directly in the review notes should help reviewers follow the intended test flow and avoid confusion during certification. Once you have updated the notes, please resubmit the extension for review.
Reacted by Matt RosserClosing this issue for now. Please feel free to open a new bug report if you encounter any issues in the future. Thank you!
Reacted by Matt RosserThank you for your help
Our extension submission was rejected during certification with the message:
The extension requires a working account. Please provide us with a working account in the Notes for certification and resubmit the extension.
We provided a working test account (username/password for our web portal) in the certification notes at submission, and the review still failed with the same message on re submission. We believe this is a mismatch between how the reviewer is testing the extension and how the extension actually works, rather than an issue with the account we provided.
How the extension actually authenticates
TestFiltering+ does not have a username/password login screen inside the extension itself. It authenticates a device (not a user session) via a per-issued enrollment/account key, delivered one of two ways:
Manually — via an "Add Device" button on our web portal (testfiltering.com), which the extension's content script picks up and registers automatically, or
Via enterprise policy — an IT admin pushes the key through Chrome/Edge managed storage (chrome.storage.managed) as part of a mass deployment (GPO/Intune/Google Admin console).
There is no in-extension login form for a reviewer to enter a username/password into — that's likely why the account credentials we supplied appear "not to work": they're portal credentials for viewing device status on the web dashboard, not extension login credentials, because the extension itself has no such login concept.
What we've already provided
Portal login (username + password) in the certification Notes field, at both submission and re submission.
[Add/attach here: the account key itself, and/or the exact "Add Device" URL/steps if you want to give them a fully turnkey repro]
What would help
Could a reviewer confirm:
Whether they attempted to find a login screen inside the extension popup/options page (there isn't one by design), and
What specific interaction they expected the "working account" to satisfy, so we can either (a) point them to the correct enrollment flow, or (b) add a documented test path in the Notes that matches what certification actually checks for.
Happy to provide a short screen recording of the enrollment flow (key entry → device shows as registered on the portal) if that helps the reviewer verify functionality without a traditional login.
Extension: TestFiltering+
Store ID: 0RDCKC917CH1
Submission date(s) of rejection: July 7th 2026