Edge Add-ons Store Submission
Understand the specific submission process and guidelines for publishing your extension to the Microsoft Edge Add-ons store.
Edge Add-ons Store Submission is a free Browser Extensions Development (Chrome & Edge) lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Browser Extensions Development (Chrome & Edge) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Why Publish on Edge?
Publishing your extension to the Microsoft Edge Add-ons store expands your reach to a diverse user base. While Chrome holds a large market share, Edge users are also actively seeking useful tools and enhancements.
Submitting to the Edge Add-ons store is similar to the Chrome Web Store process, but has its own specific steps and guidelines you need to follow.
Create Your Dev Account
Before you can submit an extension, you need a Microsoft Developer account. This account grants you access to the Partner Center, where you'll manage your submissions.
- Go to the Microsoft Partner Center.
- Sign in with your Microsoft account (e.g., Outlook, Hotmail).
- Follow the prompts to register as a developer for Edge Add-ons. There might be a one-time registration fee.
The Partner Center Dashboard
Once registered, you'll access the Microsoft Partner Center dashboard. This is your central hub for all Edge extension activities.
From here, you can:
- Start new submissions.
- Manage existing extensions.
- View analytics and performance data.
- Access support resources.
Starting a New Submission
To begin, navigate to the "Extensions" section within the Partner Center and click "Create new extension".
You'll then be guided through a series of steps to provide all the necessary information and assets for your extension. It's crucial to have your extension package ready.
Uploading Your .zip File
The first key step is to upload your extension package. This should be a single .zip file containing all your extension's files, including the manifest.json.
Ensure your manifest.json specifies "manifest_version": 3, as the Edge Add-ons store also requires Manifest V3 for new submissions.
Detail Your Store Listing
Your store listing is what users see. It needs to be clear, compelling, and accurate. You'll provide:
- Extension Name: Unique and descriptive.
- Short & Long Description: Explain features and benefits.
- Categories: Help users find your extension.
- Screenshots & Promotional Images: Visually showcase your extension.
- Supported Languages: If localized.
Privacy Policy & Compliance
Microsoft takes user privacy seriously. You must provide a valid Privacy Policy URL that clearly explains what data your extension collects, how it's used, and how users can manage it.
Also, declare any permissions your extension uses and justify why they are needed. Transparency builds user trust and helps avoid rejection during review.
Distribution & Pricing
On this step, you'll decide how your extension is distributed:
- Pricing: Most extensions are free. If you plan to charge, you'll need to configure payment details.
- Availability: Choose which markets/countries your extension will be available in. You can select worldwide or specific regions.
The Review Process
After submitting, your extension enters the review queue. Microsoft reviewers will check for compliance with their policies, functionality, and security.
The review process can take a few days. You'll receive status updates via email and in the Partner Center. Be prepared to address any feedback or issues raised by the reviewers.
Quick Check: Edge Submission
Let's test your understanding of the Edge Add-ons store submission process.
Recap: Edge Submission
In this lesson, we explored the specific steps for submitting your browser extension to the Microsoft Edge Add-ons store.
- You need a Microsoft Developer account.
- Submissions are managed via the Partner Center.
- Your extension package must be a .zip file and use Manifest V3.
- Providing a clear store listing and a valid Privacy Policy are crucial.
- After submission, your extension undergoes a review process for compliance.
Congratulations! You now understand how to get your extension to Edge users.
Frequently asked questions
Is the “Edge Add-ons Store Submission” lesson free?
Yes — the full text of “Edge Add-ons Store Submission” is free to read here on the web, and the Browser Extensions Development (Chrome & Edge) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Browser Extensions Development (Chrome & Edge) course, upgrade to CoddyKit PRO.
What will I learn in “Edge Add-ons Store Submission”?
Understand the specific submission process and guidelines for publishing your extension to the Microsoft Edge Add-ons store. You practise Browser Extensions Development (Chrome & Edge) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Browser Extensions Development (Chrome & Edge)?
No prior experience is required. Browser Extensions Development (Chrome & Edge) on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Edge Add-ons Store Submission” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Browser Extensions Development (Chrome & Edge) lesson?
Yes. Every Browser Extensions Development (Chrome & Edge) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Preparing for Store Submission
- Chrome Web Store Guidelines
- Edge Add-ons Store Submission
- Versioning, Updates & Post-Launch Maintenance