PPlatformAppStores

Microsoft Edge Add-ons

Browser

Microsoft Corporation · Browser & OS extension stores

Best for: Chrome-extension developers wanting a low-effort second distribution channel.

Overview

Microsoft Edge Add-ons accepts extensions built on the same Chromium extension platform as Chrome, letting developers submit the same package to both stores with minor manifest adjustments. Microsoft runs its own certification pipeline independent of Google's.

How to build & ship

  1. 1Register a free developer account in Microsoft Partner Center's Edge program
  2. 2Build the extension with Manifest V3 and the same Chromium/WebExtensions APIs as Chrome
  3. 3Package the extension as a ZIP
  4. 4Submit through Partner Center with listing details and store-availability settings
  5. 5Pass certification and publish

Key APIs & SDKs

Manifest V3
WebExtensions / chrome.* APIs
Service workers
declarativeNetRequest

Integration types

Extension

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: None
  • Security review: Required
  • Microsoft certification review before listing, similar scope to Chrome Web Store policies.
  • Certification checks for policy and security compliance, typically within about seven business days.
  • No platform-wide API rate limit; governed by whichever web APIs the extension calls.
Auth docs Store policies

Monetization

Free
Paid app
Onboarding
$0
Commission
15% on paid extensions via Microsoft Store commerce
Merchant of Record
Microsoft acts as MoR for paid listings

Pros & cons for builders

Pros

  • No registration fee
  • Chrome extensions port with little or no change
  • Access to enterprise Windows/Edge users

Cons

  • Much smaller audience than Chrome
  • Reviews can be slower than Chrome
  • Company-account verification can take weeks