Extension rejected twice after 7-day review — identical code approved on Chrome Web Store

[JackDan9]

Hi team,

I'm hoping someone from the Edge Add-ons certification team or the community can help me look into a certification issue.

Summary:

• I submitted an update to my extension and waited about 7 days before it was rejected.
• I resubmitted after reviewing the rejection notice, and it was rejected again after another full review cycle.
• The exact same codebase was submitted to the Chrome Web Store and was approved without issues.
• My previous versions of this extension have all been reviewed and approved smoothly on Edge Add-ons, so this is unusual for my product.

What I'm looking for:

• Clarification on what specifically is triggering the rejection, since the feedback I received is not specific enough for me to identify the actual policy concern.
• Any guidance on what changed recently in the Edge certification process that might explain why a previously-approved extension (with a small delta from the last approved version) is now failing.
• If anyone from Microsoft can take a closer look at the submission, I'd really appreciate it.

Details I can share if helpful:

• Product ID: 2da79c4b-1d91-4ec6-8ee6-aa73ee4dc36a
• URL: https://microsoftedge.microsoft.com/addons/detail/ljlnbmmmgnflklegiafalpieckpihffn
• Microsoft Store ID: 0RDCKC1R9HCD
• CRX ID: ljlnbmmmgnflklegiafalpieckpihffn
• Chrome Web Store listing of the same version: https://chromewebstore.google.com/detail/autoglm/jelniggicmclhfgnlapbkgfibmgelfnp

I'm happy to provide the full rejection email, test steps, a demo video, or a test account if that helps speed things up. Just let me know what would be useful.

Thanks in advance for any help — this is blocking our release and any pointers would be hugely appreciated.

kind regards

i hope this email finds you well
email: zai_extension@outlook.com