# Edge Add-ons test account and live server in certification

> Submit certification notes with a working test account and functioning backend whenever login is required, because Edge reviews fail when reviewers cannot actually run the extension.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/edge-add-ons-test-account-and-live-server-in-certification/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/legal/microsoft-edge/extensions/developer-policies)
- GrowthDex source hub: [Microsoft Learn: Developer policies for the Microsoft Edge Add-ons store](/sources/microsoft-learn-developer-policies-for-the-microsoft-edge-add-ons-store-/)
- Last checked: 2026-06-06T11:04:17Z
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Product, Support
- Stages: browser extensions, microsoft edge add-ons, certification, qa handoff


## Why this can grow

A surprising number of extension teams polish the listing and forget the reviewer. Microsoft makes the certification dependency plain: the product must be fully testable, the steps must be provided, login flows need usable credentials or a clear explanation, and any required server has to be up. That turns review prep into a conversion tactic too, because the same setup discipline usually makes onboarding cleaner for the real buyer.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where edge add-ons test account and live server in certification can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Product channel.
3. Use the evidence from learn.microsoft.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Microsoft requires extensions to be fully testable at submission, asks for test credentials or an explanation in certification notes when login is needed, and says any required server must be functional for review.

## Adjacent tactics in the same lane

- [Edge Add-ons duplicate assets across locales after primary proof](/growth-ideas/edge-add-ons-duplicate-assets-across-locales-after-primary-proof/) - 1 shared channel, 2 shared stages
- [Chrome Web Store review reply loop with direct review link](/growth-ideas/chrome-web-store-review-reply-loop-with-direct-review-link/) - 2 shared channels, 1 shared stage
- [Chrome Web Store verified publisher URL and support hub](/growth-ideas/chrome-web-store-verified-publisher-url-and-support-hub/) - 2 shared channels, 1 shared stage
- [Edge Add-ons short description comes from the manifest](/growth-ideas/edge-add-ons-short-description-comes-from-manifest/) - 1 shared channel, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Microsoft Edge Add-ons page should finish the review before the install](/blog/the-microsoft-edge-add-ons-page-should-finish-the-review-before-the-install/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.