Engineering service
Microsoft Edge extension development
We publish your Chrome extension on Microsoft Edge and make it deployable in companies that run Edge: feature-by-feature testing, Partner Center submission to Edge Add-ons, and force-install through Group Policy and Intune. No extension yet? We build one that targets Chrome and Edge from day one.
- 11+ years of experience
- 300+ projects delivered
- Remote team, clients worldwide
- NDA on request
Overview
What it is and when it fits
Edge is built on Chromium, so most Chrome extensions run in it with few or no changes. The extra work is rarely about code. It is about being listed in Edge's own store, how companies deploy the extension, and how it behaves on the managed Windows machines your users have.
We handle the Edge side: compatibility testing, publishing to Edge Add-ons through Microsoft Partner Center, and deployment through Edge policies. If you have no extension yet, we build it once for Chrome and Edge.
Who this is for
- Teams with a Chrome extension who want it listed on Microsoft Edge Add-ons for Edge users.
- 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)
The same Manifest V3 service worker as in Chrome. Edge 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.
Chromium extension APIs
Nearly all of Chrome's chrome.* APIs; identity.getAuthToken is the notable gap. Company policies can force-install and configure the extension.
Web page
Content you do not control. Treat everything from it as untrusted input.
What we offer
What's included
Edge compatibility check
Your extension installed and tested feature by feature in Edge, with any API, manifest or interface difference from Chrome listed and fixed.
One source, two store packages
A build that produces the Chrome and Edge packages from the same source tree. With no extension yet, we build it this way from the start.
Edge Add-ons publishing
Partner Center registration, listing content, screenshots and permission explanations, submitted to the Microsoft Edge Add-ons store.
Group Policy and Intune rollout
Force-install policies such as ExtensionInstallForcelist, delivered through Group Policy or Intune, so IT can push the extension to managed Windows devices.
Testing on managed devices
Checks on machines with Edge policies, proxies and restricted settings applied, since that is closer to what enterprise users run.
Automated Edge releases
After the first submission in Partner Center, new versions go to Edge Add-ons from your CI pipeline through the Edge Add-ons API, next to your Chrome release.
Deliverables
What you get
- 01
Compatibility report
Each feature marked as working, changed or failing in Edge, with the fix we applied.
- 02
Edge package from your build
The Edge package produced by the same build command as your Chrome package, with Edge-only values kept in one place.
- 03
Edge Add-ons listing
A submitted Partner Center listing with text, images, privacy details and notes for the store's testers.
- 04
IT deployment guide
The extension ID, update URL and policy values an administrator enters in Group Policy or Intune to force-install it.
- 05
Managed-device test notes
Results from a test deployment on a managed Windows device, with the policies and proxy you specify.
- 06
Release automation
A CI step that uploads each new version to Edge Add-ons alongside your Chrome Web Store release.
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. | Google sign-in through chrome.identity.getAuthToken does not work in Edge and needs launchWebAuthFlow instead. A few 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, with its own account and listing. Registration is free. |
| Enterprise deployment | An administrator can install the extension for a group of users. | Deployment uses Edge's own policies, such as ExtensionInstallForcelist, delivered through Group Policy or Intune. |
| 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
Edge users with little extra upkeep
Most Manifest V3 code carries over unchanged, so an Edge version adds little to your maintenance.
Found where Edge users look
An Edge Add-ons listing puts the extension in Edge's own store and search, not only in the Chrome Web Store.
Rollout that does not hold up a sale
Your customers' IT teams get policy values they can apply, so deployment is not the step that delays an enterprise deal.
The size of the Edge work, known up front
A feature-by-feature report comes first, so you know what an Edge version involves before you commit to it.
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
- Your extension already runs in Edge, your Edge users are happy installing it from the Chrome Web Store, and you do not sell to companies that run Edge. An Edge listing can wait.
- You need deep integration with a Windows feature Edge does not expose to extensions. A native app, or a native messaging host next to the extension, fits better.
Tech stack
Technologies we use
The engines, APIs and tools we use on this service.
TypeScriptFAQ
Common questions
Not always. Edge users can install extensions from the Chrome Web Store, so your Chrome listing already reaches them. A listing on Edge Add-ons makes the extension appear in Edge's own store and search, and publishing there is free, so it is usually worth adding once Edge users or Edge-based companies matter to you.
Often it will, because both browsers use the Chromium engine and support the same extension APIs. Features that rely on Google services are the usual exception: Google sign-in through chrome.identity.getAuthToken does not work in Edge, so we move it to launchWebAuthFlow. We test every feature in Edge before calling it done.
A Microsoft or GitHub account to register as an Edge developer, the extension package, listing text and images, a privacy policy link if the extension handles personal data, and test notes or a test login if features sit behind sign-in.
Yes. Edge supports managed storage, so administrators can push settings such as a server address or license key through policy, and the extension reads them at startup. We define the settings schema and document it for your customers' IT teams.
Porting a working extension to another browser typically takes 2–6 weeks, and Edge ports are often at the short end because the code rarely changes. That is a typical range, not a quote. Edge Add-ons review time comes on top and varies, so leave room for it in your release plan.
Related reading
Our services
Related services
Start a project
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.
