Engineering service
Microsoft Edge Browser Extension Development
We take Chromium extensions into Edge as production products: API compatibility checks, Microsoft Partner Center publishing, and deployment on managed Windows devices through Group Policy and Intune.
- 15+ years of experience
- 300+ projects delivered
- Clients worldwide
- NDA available
Overview
What this is, and when it is the right call
Edge is built on Chromium, so most Chrome extensions run in it with few or no changes. The extra work is rarely about the code. It is about where the extension is published, how organizations deploy it and how it is tested on the machines your users have.
We handle the Edge side of that: checking compatibility, setting up publishing through Microsoft Partner Center, and preparing deployment through Edge policies for managed devices. If you have no extension yet, we build it once for Chromium browsers.
Who this is for
- Teams with a Chrome extension who want it available to Edge users on the Microsoft Edge Add-ons store.
- Software vendors selling to organizations that run managed Windows devices with Edge.
- IT teams that need an internal extension deployed to employees through Edge policies.
- Product owners who want to know how much extra work an Edge version really is.
How it works
Architecture at a glance
How an Edge extension is put together
Popup, side panel, options
The interface users see. Talks to the background through messages.
Service worker (background)
Handles events, alarms and network rules. The browser stops it when idle, so state must live in storage.
Content script
Runs inside pages you choose. Can read and change the page, in an isolated JavaScript world.
Browser extension APIs
tabs, storage, scripting, alarms, declarative network rules, identity
Web page
Content you do not control. Treat everything from it as untrusted input.
What we offer
What we engineer: Microsoft Edge Browser Extension Development
Chromium compatibility check
Your extension installed and tested feature by feature in Edge, with any API or manifest differences from Chrome listed out.
One source, two store packages
A build setup that produces Chrome and Edge packages from the same source tree, with Edge-specific manifest values isolated.
Microsoft Partner Center submission
Listing content, screenshots and permission explanations prepared and submitted through Partner Center to the Edge Add-ons store.
Group Policy and Intune deployment
Policy settings so IT teams can force-install the extension on managed Windows devices, similar to Chrome's equivalent policies.
Testing on managed device profiles
Checks on machines with Edge policies, proxies and restricted settings applied, since that is closer to what your users actually run.
New Chromium extension builds
If no extension exists yet, we build it once against the Chromium extension APIs so it targets Chrome and Edge from day one.
Deliverables
What you get
- 01
Compatibility check
A review of your extension against Edge, listing any API, permission or interface differences that need a change.
- 02
Edge-ready build
A package built from the same source as your Chrome extension, with any Edge-specific manifest values kept separate.
- 03
Microsoft Partner Center publishing
Help creating the listing, filling in the submission details and uploading the package to the Microsoft Edge Add-ons store.
- 04
Enterprise deployment setup
Instructions for installing the extension through Edge policies, similar to the force-install settings used for Chrome.
- 05
Testing on managed Windows setups
Checks on machines that resemble your customers' environments, with policies, proxies and restricted settings applied.
- 06
Release notes
A short guide to shipping updates to Chrome and Edge from one codebase.
Compare
Chrome to Edge: what stays and what changes
| Area | What stays | What changes |
|---|---|---|
| Manifest and APIs | Manifest V3 and the Chrome extension APIs work in Edge in most cases. | A few Chrome-specific integrations or newer APIs may behave differently, so each one is checked. |
| Publishing | The same package format and much of the same listing content. | You publish through Microsoft Partner Center to the Microsoft Edge Add-ons store, with its own account and listing. |
| Enterprise deployment | The idea of an administrator installing an extension for a group of users. | Deployment uses Edge policies rather than Chrome's, so the settings and management tools differ. |
| Users and testing | Most page behavior is the same, since both browsers use the Chromium engine. | Edge users often run on managed Windows devices with policies applied, which is where extra testing matters. |
Why it matters
What this gives you
Minimal rework from an existing Chrome build
Most Manifest V3 code carries over unchanged; we isolate the handful of values that differ by browser rather than forking the codebase.
A submission handled end to end
Partner Center account setup, listing content and permission explanations prepared so the submission matches what reviewers expect.
Deployment IT teams can act on
Group Policy or Intune settings documented clearly enough for an administrator to roll the extension out without guesswork.
Testing under real managed-device conditions
Checks run against policy-restricted, proxy-routed profiles instead of a clean developer machine.
Our approach
How an Edge extension project runs
Check compatibility
We install your extension in Edge and test every feature, noting anything that fails or behaves differently.
You get: A compatibility report
Fix and build
We change the code where needed and set up a build that produces the Edge package from your existing source.
You get: An Edge-ready package
Prepare the listing
We set up the Partner Center listing with descriptions, images and the permission explanations the store asks for.
You get: A listing ready to submit
Submit and respond
We submit the extension, then work through any feedback from the store together with you.
You get: A published or resubmitted extension
Enterprise rollout
Where relevant, we write the policy settings your administrators need and test a deployment on a managed device.
You get: Deployment instructions for IT
When this is not the right fit
A few cases where this approach may not be the best choice for you.
- Your extension already runs in Edge and you do not plan to publish there. A Chrome build may be enough.
- You need deep integration with a Windows feature Edge does not expose to extensions. A native app fits better.
Tech stack
Technologies we use
The engines, APIs and tools behind our microsoft edge browser extension development work.
Chromium Extensions APIMicrosoft Partner CenterEdge Add-ons StoreGroup PolicyMicrosoft IntuneService Workers
JavaScript
TypeScriptFAQ
Questions engineers ask before starting
Often it will, because both browsers use the Chromium engine and support the same extension APIs. We still test every feature in Edge before calling it done.
Our services
Related services
Explore more services that work alongside this one.
Talk to a Browser Engineer
Ship Your Extension on Edge
Tell us about your Chrome build and your managed-device requirements. We will scope the Edge work and the enterprise deployment.
