Imagine you've released a Chrome extension and want to reach Edge users. Migration is almost trivial — both browsers run on Chromium. However, publishing in Edge Add-ons has its own nuances: Partner Center registration, packaging with Edge-specific adjustments, passing review, and automating updates. We've helped publish 30+ extensions in both stores. Average time from registration to launch is 2–5 days. For example, one client's extension was rejected due to a missing privacy policy — we drafted the document within an hour, and the extension passed moderation afterward. 97% of our extensions pass moderation without comments. Get a free project assessment — we'll prepare a tailored proposal.
Why Publish in Edge Add-ons?
Registration in Partner Center is free, unlike Chrome Web Store ($5). Average review time is 1.5 days vs. 3–5 days in Chrome. This is especially important for urgent releases. Additionally, Edge supports corporate distribution via GPO and Intune, simplifying deployment in organizations.
How to Prepare Your Extension for Publication
Registration. Go to Microsoft Partner Center and sign in with a Microsoft account. No fees.
Compatibility. Chrome extensions work in Edge almost unchanged. The only addition is Edge-specific settings in browser_specific_settings:
{ "manifest_version": 3, "browser_specific_settings": { "edge": { "browser_action_next_to_addressbar": true } } } These settings do not affect Chrome. Use them to improve UX.
Import from Chrome. Use the Import from Chrome Web Store function in Partner Center. Just provide the Chrome extension ID — Edge will copy metadata and screenshots. This saves 1–2 hours of manual entry.
Publication Process: From Build to Release
Requirements for the ZIP package are standard:
cd dist/ zip -r ../edge-extension-1.0.0.zip . --exclude "*.map" --exclude ".DS_Store" Icons: 16, 32, 48, 128 px. Double-check manifest.json. Upload in Partner Center:
- Create a new extension in Dashboard.
- Upload ZIP — metadata is extracted automatically.
- Complete description, screenshots, category.
- Provide a Privacy Policy URL if you collect data.
- Submit for review.
| Step | Action | Timeline |
|---|---|---|
| Registration | Create Partner Center account | 1 hour |
| Package preparation | Validate manifest, icons, browser_specific_settings | 1–2 days |
| Upload | Fill listing, upload ZIP | 1 day |
| Review | Wait for moderation | Up to 3 days |
| Publication | Release extension | 1 hour |
According to Microsoft, average review time in Edge Add-ons is 1.5 days.
Automating Publication via API
How to Set Up CI/CD for Automatic Releases?
Microsoft provides a REST API for programmatic upload and publishing. Example script to get a token and upload a new version:
# Get access token TOKEN=$(curl -s -X POST "https://login.microsoftonline.com/$TENANT_ID/oauth2/v2.0/token" \ -d "client_id=$CLIENT_ID&client_secret=$CLIENT_SECRET&grant_type=client_credentials&scope=https://api.addons.microsoftedge.microsoft.com/.default" \ | jq -r '.access_token') # Upload new version curl -X POST \ "https://api.addons.microsoftedge.microsoft.com/v1/products/$PRODUCT_ID/submissions/draft/package" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/zip" \ --data-binary @extension.zip # Publish draft curl -X POST \ "https://api.addons.microsoftedge.microsoft.com/v1/products/$PRODUCT_ID/submissions" \ -H "Authorization: Bearer $TOKEN" PRODUCT_ID is taken from the Partner Center URL. We configure CI/CD with this API for automatic releases. Details in documentation.
Corporate Distribution and Policy Specifics
For internal extensions, you can use Group Policy without publishing to the Store:
<enabled/> <data id="ExtensionInstallForcelistDesc" value="1extension-id;https://edge.microsoft.com/extensionwebstorebase/v1/crx"/> Or through Intune for MDM-managed devices.
Edge is more lenient toward corporate extensions with broad permissions if the account is verified. Extensions with <all_urls> pass review more easily when justification is provided in the description. The principle of minimal permissions remains standard.
| Criteria | Edge Add-ons | Chrome Web Store |
|---|---|---|
| Registration | Free | $5 (one-time) |
| Typical review time | Hours – 3 days | 2–7 days |
| Import from another store | Yes | No |
| Corporate distribution | GPO/Intune | Google Admin |
What Our Support Includes
We offer full support for publishing your extension in Edge Add-ons:
- Consultation on preparation and publication strategy.
- Package preparation: structure, icons, browser_specific_settings.
- Upload and review handling: listing completion, moderator responses.
- CI/CD setup: build and publication automation via API.
- Documentation and training for your team.
- Post-release support — help with updates and bug fixes.
Contact us for a free consultation — we'll assess your project and provide a tailored proposal for turnkey extension publication. Guaranteed first-time moderation pass if policies are followed.
Common Publication Mistakes
Missing privacy policy — mandatory when collecting data. Prepare it in advance. Incorrect icon sizes — use 16, 32, 48, 128 px. Prohibited APIs — check the list of allowed APIs in Edge documentation. Remote code — ensure all code is bundled in the extension. These issues lead to rejection but are easily avoidable with careful review.