Edge extension review: what the Featured badge means

Microsoft has updated Edge extension reviews and Featured badge refreshes. Use this release checklist without assuming approval times or guaranteed badges.

Harllens George | 2026-09-14

Microsoft Bing Homepage listing on Microsoft Edge Add-ons with a Featured badge beside its name.
The Featured badge beside Microsoft Bing Homepage in Microsoft Edge Add-ons documentation. It illustrates badge placement, not approval of our extension. Image source. Microsoft and contributors. Original image, displayed proportionally. CC BY 4.0.

Microsoft's September 8, 2026 announcement describes automated Edge extension-review checks with unchanged standards and Featured badge refreshes every 15 days. It gives no fixed approval deadline. Edge announcement.

Sources checked September 12, 2026. No extension submission or measured review times underlie this article.

Keep three outcomes separate

Record package validation, store certification and observed badge status separately. One does not prove another. Keep the launch date conditional on the actual store outcome.

Selective expedited reviews began in February 2025; that priority process is distinct from September's update. Earlier announcement. The Featured badge is temporary and revocable, with no manual application or appeal. Absence does not establish that an extension is unsafe. Badge documentation.

Prepare a reproducible release

Microsoft's best practices cover permissions, privacy, usability, listings and stability, without guaranteeing a badge. Use three acceptance steps:

  1. Freeze the candidate. Record version, source revision and ZIP checksum. Have a teammate reproduce the package. Keep the tested archive separate from later builds. For each permission, identify its user action and test; investigate leftovers from abandoned features.
  2. Test installation and upgrade. Use a clean browser profile, then upgrade one containing earlier settings. Verify preferences, failed sign-in recovery and advertised workflows in the packaged extension. Screenshots must match that revision and use synthetic data.
  3. Prepare support evidence. Check monitored support links. Document what users see when a service fails, a session expires or access is denied. Include reproducible examples and recovery steps, not just console errors. Compare the listing with the candidate before submission.

Pitfalls after submission

The 15-day refresh is not a review SLA. Check the live listing before announcing a badge; do not promise more installs from it. Attach unresolved feedback to the exact submitted package.

These are recommended checks, not a claim that our extensions passed Edge certification. Your acceptance record still matters after a successful store review.

Related guide

The Codex Thread Renamer Patcher is a separate VS Code maintenance tool, not an Edge add-on or evidence of store approval.