Repository navigation
[Bug - Partner Center] The "No, testers can access and test all functionality without any additional info" preference is not remembered #752
Description
Activity
Thank you for sharing this feedback.
I understand that when publishing a new version of an extension in Partner Center, the selection for the test account requirement does not persist from the previous submission. As a result, developers need to repeatedly select the same option ("No, testers can access and test all functionality without any additional info") for each update, which adds unnecessary steps to the publishing workflow.
I appreciate you bringing this to our attention. I will review the behavior with the engineering team to determine whether this is the expected experience and whether improvements can be made to streamline the process. I will share any updates or guidance as soon as I receive more information from the team.
Thank you for your feedback and patience.
Reacted by carlosjeurissenWe introduced this step because we observed a significant number of extension submissions failing review due to missing or incomplete testing information. Requiring developers to explicitly review and confirm the testing requirements during submission has helped reduce this issue and improved the overall submission experience.
That said, we understand that repeatedly selecting the same option for updates can add unnecessary friction, especially for extensions that do not require test accounts. We appreciate your suggestion to remember the previously selected choice and have shared this feedback with the team for consideration as we continue to look for ways to balance submission quality with a more streamlined publishing experience.
Reacted by carlosjeurissen
When publishing a new version of a browser extension on Partner Center, Microsoft asks if test accounts are needed to test the functionality of the extension.
However, after answering "No, testers can access and test all functionality without any additional info", this choice is not remembered for the next update. This adds a lot of extra steps to publishing new versions to extensions.
Ideally the last used option would be highlighted when walking through these steps.