Microsoft Edge Add-ons
Microsoft Edge Add-ons
Role
Distribution channel for every oriz-*-ext extension on Microsoft
Edge — separate listing from the Chrome Web Store even though Edge
will side-install extensions sourced from CWS. The native Edge
listing is what shows up in Edge's in-browser add-ons surface and
what Microsoft promotes to its user base.
Free tier
- Unlimited submissions and unlimited published versions.
- No developer-registration fee for the Edge Add-ons program specifically (distinct from the Microsoft Store / Windows Store $19 individual / $99 company fee — those apply to packaged Win32/UWP apps, not browser extensions).
- No review fee, no per-install fee.
Card / subscription required?
NO. Microsoft Partner Center for Edge Add-ons requires only a Microsoft account; no payment method on file at any stage.
CI auto-publish
The same .zip produced by web-ext for AMO
is submitted to the Edge Add-ons partner-center API from GitHub
Actions:
- name: Submit to Edge Add-ons
uses: wdzeng/edge-addon@v2
with:
product-id: ${{ secrets.EDGE_PRODUCT_ID }}
zip-path: dist/extension.zip
client-id: ${{ secrets.EDGE_CLIENT_ID }}
api-key: ${{ secrets.EDGE_API_KEY }}
The action wraps Microsoft's Edge Add-ons API. Credentials in Doppler → GitHub Secrets.
Alternatives
- Chrome Web Store — sibling, covers Edge via cross-browser install. This native Edge listing is complementary, not redundant.
- Firefox Add-ons (AMO) — sibling, free.
Swap cost
Low — the action is per-store. Dropping the Edge step removes one job; the artifact and manifest stay untouched.
Why this is our pick
Edge ships pre-installed on every modern Windows machine. Even though most users will install our extensions via the Chrome Web Store on Edge, a native Edge Add-ons listing is what surfaces in Edge's promoted-extensions UI, in Microsoft's editorial picks, and in Bing search. Free + no card means the cost is purely the CI step.