Microsoft Edge Add-ons readiness

Porting is compatible, not automatic

Microsoft's official guidance says Chrome extension APIs and manifest keys are largely code-compatible with Edge, while directing developers to review API support, remove update_url, and replace Chrome-specific branding before submission.

ExtensionGate's Edge profile applies target-specific rules but cannot replace clean-profile sideloading and feature tests.

What the Edge lens checks

• Edge-specific update_url and Chrome-only branding signals
• Permission, privacy-disclosure, listing, and certification-note evidence
• Package availability and reviewer-testability prompts

Runtime behavior and backend availability are manual checklist items. The static lens does not claim that Chrome and Edge behave identically.

Partner Center preparation

The current publishing workflow uses a ZIP and asks for listing details, markets, privacy information, permission justifications, remote-code information, data practices, and certification notes. Gated functionality should be testable through the store's designated review workflow.

Policy lens

Microsoft's developer policies emphasize a clear single purpose, accurate descriptions, stable behavior, essential permissions, secure data handling, dependency disclosure, and a fully testable extension. Static evidence cannot prove all of those product and operational facts.

Official sources

• Microsoft: port a Chrome extension to Edge
• Microsoft: publish an Edge extension
• Microsoft Edge extension developer policies

Human-reviewed 2026-07-29. Microsoft updated its Edge Add-ons developer policies on 2026-07-24. Recheck official requirements at submission time. No scan guarantees approval.