Microsoft Edge Add-ons store developer policies

Introduction and Objective of this document

Thank you for your interest in developing extensions for the Microsoft Edge Add-ons store. The Microsoft Edge Add-ons store developer policies (Add-ons store developer policies) apply to your extensions, including your submission of extensions through Partner Center and the provision of such extensions through the Microsoft Edge Add-ons.

The Microsoft Edge Add-ons store is also called the Microsoft Edge Add-ons website. The Microsoft Edge Add-ons store developer policies are also called the Microsoft Edge Add-ons website developer policies.


A few principles to get you started:

  • You should offer unique and distinct value within your extensions for Microsoft Edge. Provide a compelling reason to download your extensions from the Microsoft Edge Add-ons store (Microsoft Edge Add-ons).

  • You must not mislead our joint users about what your extension does, who is offering it, and so on.

  • You must not attempt to cheat users, the system or the ecosystem. There is no place in our Microsoft Edge Add-ons for any kind of fraud; be it ratings and review manipulation, credit card fraud or other fraudulent activity.

Adhering to the Microsoft Edge Add-ons store developer policies should help you make choices that enhance the appeal and audience of your extension.

Your extensions are crucial to the experience of hundreds of millions of users. We look forward to experiencing what you create and are thrilled to help deliver your extensions to the world.

1. Product Policies

1.1 Distinct Function & Value; Accurate Representation

Your extension and associated metadata must accurately and clearly reflect the source, functionality, and features that you describe.

1.1.1 Extensions must have a single purpose

Your extension must have a single purpose with narrow functionality.

1.1.2 Describe your extension

All aspects of your extension should accurately describe the functions, features and any important limitations of your extension, including required or supported input devices. The value proposition of your extension must be clear during the first run experience. Your extension may not use a name or icon similar to that of other extensions, and must not claim to represent a company, government body, or other entity if you don't have permission to make that representation.

1.1.3 Functionality

Your extension must be fully functional.

1.1.4 Search and Discovery

Search terms may not exceed seven unique terms and should be relevant to your extension.

1.1.5 Provide appropriate details

You must provide distinct and informative details about your extension and the functionality in listing (metadata) for your extension. Your extension must provide a valuable and quality user experience. Your extension must also have an active presence in Microsoft Edge Add-ons.

1.1.6 Stability and Performance

Your extension must not negatively impact the performance or stability of Microsoft Edge.

1.1.7 Obfuscation

Extensions with obfuscated code aren't allowed. This includes code within your extension package as well as any external code or resource fetched from the web. You may be asked to refactor parts of your code if it is not reviewable.

1.1.8 Altering Browser Settings

Your extension must not, without appropriate user consent, alter, or appear to alter, browser functionality or settings including, but not limited to: the address bar search provider and suggestions, the start or home page, the new tab page, and adding or removing favorite.

Any alteration to the browser settings should be explicitly documented in the description of your extension.

Your extension may only revise key settings to replace a Microsoft webpage or service with that of a third-party (such as require use of a third-party search engine or set the home page to a third-party web property) if you are employed by or otherwise associated with such third-party.

1.2 Security

Your extension must not jeopardize or compromise user security, or the security or functionality of the device, system or related systems.

1.2.1 Content Security Policies

If you make any changes to your extension beyond the described functionality, any changes to code must be compliant with the Microsoft Edge content security policy. For example, your extension should not download a remote script and subsequently run that script in a manner that is not consistent with the described functionality.

1.2.2 Unwanted and Malicious Software

Your extension must not contain or enable malware as defined by the Microsoft criteria for Unwanted and Malicious Software.

1.2.3 Dependency on other software

Your extension may depend on non-integrated software (such as another product, module, or service) to deliver the primary functionality, provided you disclose the dependency in the description.

1.2.4 Extensions Update

Unless otherwise permitted by Microsoft, your extensions must be updated only through Microsoft Edge Add-ons.

1.3 Product is Testable

Your extension must be testable. If it is not possible to test your extension for any reason, including, but not limited to, the items below, your extension may fail this requirement.

1.3.1 User Credentials

If your extension requires login credentials, provide a working demo account using the Notes for certification field.

1.3.2 Availability of services

If your extension requires access to a server, the server must be functional to verify that it works correctly.

1.4 Usability

Your extension must meet Microsoft Edge Add-ons store standards for usability, including, but not limited to, those listed in the subsections below.

1.4.1 Compatibility across platforms

Your extension should be compatible with Microsoft Edge on all the devices and platforms on which they may be downloaded. If an extension is downloaded on a device with which it is not compatible, it should detect that at launch and display a message to the user detailing the requirements that devices must meet in order to be compatible with your extension.

1.4.2 User Experience

Your extension must start up promptly and must stay responsive to user input. Your extension must continue to run and remain responsive to user input. Your extension must shut down gracefully and not close unexpectedly. Your extension should handle exceptions and remain responsive to user input after the exception is handled.

1.5 Personal Information

The following requirements apply to extensions that access Personal Information. Personal Information includes all information or data that identifies or could be used to identify a person, or that is associated with such information or data.

1.5.1 Collect Personal Information only when necessary

Your extension may collect, access, use, or transmit Personal Information (including web browsing activity); only if required by and only for use in a prominently disclosed, user-facing feature.

1.5.2 Maintain a privacy policy

Regardless of whether your extension accesses, collects, or transmits Personal Information; you must provide prominent notice of and comply with your privacy policy if required by law. Your privacy policy must inform users of the Personal Information accessed, collected, or transmitted by your extension, how that information is used, stored, and secured, and indicate the types of parties to whom it is disclosed.

Your privacy policy must describe the controls that users have over the use and sharing of their information, how they access their information, and it must comply with applicable laws and regulations. Your privacy policy must be kept up-to-date as you add new features and functionality to your extension.

If you provide Microsoft with your privacy policy, you agree to permit Microsoft to share such privacy policy with users of your extension.

1.5.3 Sharing data with third parties

You may publish the Personal Information of users of your extension to an outside service or third-party through your extension or associated metadata only after obtaining opt-in consent from those users. Opt-in consent means the users give their express permission in the user interface of your extension for the requested activity, after you:

  • Describe to your users how the information is accessed, used or shared and indicate the types of parties to whom it is disclosed.

  • Provide your users a mechanism in your extension user interface through which they have the option to later rescind the permission and opt-out.

1.5.4 Sharing information of non-Users

If you publish a person's Personal Information to an outside service or third-party through your extension or the metadata, but the person whose information is being shared is not a user of your extension:

  1. You must obtain express written consent to publish that Personal Information.

  2. You must permit the person whose information is shared to withdraw that consent at any time.

  3. Your privacy policy must clearly disclose that you may collect personal information in this manner.

  4. If required by applicable law you must delete the Personal Information of any individual upon request, including individuals whose information you collect in this manner.

  5. If your extension provides users with access to another person's Personal Information, this requirement also applies.

1.5.5 Transmit information securely

If your extension collects, stores, or transmits Personal Information; it must do so securely by using modern cryptography methods.

1.5.6 Highly sensitive information

Your extension must not collect, store, or transmit highly sensitive personal information, such as health or financial data, unless the information is related to the functionality of your extension. Your extension must also obtain express user consent before collecting, storing, or transmitting such information.

1.6 Permissions

Your extension must only request those permissions that are necessary for functioning. You must provide a description of how your extension works. Your extension must only perform as described. Your extension may not request permission for capabilities that go beyond the capabilities required to perform and function as declared.

1.7 Localization

You should localize your extension for all languages that your extension claims to support. The text of the description of your extension should be localized in each language that you declare.

If your extension is localized such that some features aren't available in a localized version, you must clearly state or display the limits of localization in your extension description. The experience provided by an Extension must be reasonably similar in all languages that it supports.

1.8 Financial Transactions

If your product includes in-product purchase, subscriptions, virtual currency, billing functionality, or captures financial information; the requirements in the following sections apply.

1.8.1 Paid Features

Your extension may enable users to consume digital content or services purchased through a third-party purchase mechanism or API.

You must use a secure third-party purchase API for purchases of physical goods or services. You must use a secure third-party purchase API for payments made in connection with any other services including real world gambling or charitable contributions.

  • If your extension is used to facilitate or collect charitable contributions or to conduct a promotional sweepstakes or contest, you must do so in compliance with applicable law.

  • You must also state clearly that Microsoft is not the fundraiser or sponsor of the promotion.

  • In-product offerings sold in your extension must not be converted to any legally valid currency (such as USD, Euro, and so on) or any physical goods or services.

The following requirements apply to your use of a secure third-party purchase API:

  • At the time of the transaction or when you collect any payment or financial information from the user; your extension must identify the commerce transaction provider, authenticate the user, and obtain user confirmation for the transaction. A commerce transaction provider maintains a secure platform for financial exchanges.

  • Your extension may offer users the ability to save this authentication, but users must have the ability to either require an authentication on every transaction or to turn off in-product transactions.

  • If your extension collects credit card information or uses a third-party payment processor that collects credit card information, the payment processing must meet the current PCI Data Security Standard (PCI DSS).

1.8.2 Disclosing paid features

Your extension and associated metadata must provide information about the types of in-product purchases offered and the range of prices. You must not mislead users and must be clear about the nature of your in-product promotions and offerings including the scope and terms of any trial experiences.

If your extension restricts access to user-created content during or after a trial, you must notify users in advance. In addition, your extension must make it clear to users that they are initiating a purchase option in your extension.

1.9 Notifications

Your extension must respect system settings for notifications. This means any presentation of ads and notifications to users must be consistent with user preferences, regardless of whether the notifications are provided by the Microsoft Push Notification Service (MPNS), Windows Push Notification Service (WNS), or any other service. If the user disables notifications, either on a product-specific or system-wide basis, your extension must remain functional.

If your product uses MPNS or WNS to transmit notifications, it must comply with the following requirements:

1.9.1 General Guidance

Notifications provided through WNS or MPNS are considered product content and are subject to all Add-ons Catalog Developer Policies.

1.9.2 Ownership of notifications

You must not obscure or try to disguise the source of any notification initiated from your extension.

1.9.3 No Confidential or Sensitive Information

You must not include in a notification any information users may reasonably consider confidential or sensitive.

1.9.4 Purpose of notifications

Notifications sent from your extension must relate to that extension or to other extensions you publish in Microsoft Edge Add-ons store and must not include promotional messages of any kind that aren't related to your extensions.

1.10 Advertising Conduct and Content

For all advertising related activities, the following requirements apply:

1.10.1 Purpose

The primary content of your extension must not be advertising, and advertising must be clearly distinguishable from other content in your extension.

1.10.2 Policies and Agreements

Any advertising content your extension displays must adhere to Microsoft Creative Acceptance Policy.

If your extension displays ads, all content displayed must conform to the advertising requirements of the App Developer Agreement and this Policy.

1.10.3 Quality of advertising

  • The primary purpose of your extension must not be to get users to click ads.

  • Your extension must not do anything that interferes with or diminishes the visibility, value, or quality of any ads that it does display.

1.10.4 Promotions

If you purchase or create promotional ad campaigns to promote your extensions through the ad campaign functionality in Partner Center, all ad materials you provide to Microsoft, including any associated landing pages, must comply with Microsoft Creative Specifications Policy and Microsoft Creative Acceptance Policy.

1.10.5 Notifying Users of Opt-Out for Interest-Based Advertising

Your privacy statement or terms of use must let users know you plan to send Personal Information to the ad service provider and must tell users how they may opt-out of interest-based advertising.

1.10.6 Other guidelines

If your extension is directed at children under the age of 13, as defined in the Children's Online Privacy Protection Act; you must notify Microsoft of this fact in Partner Center and ensure that all ad content displayed in your extension is appropriate for children under the age of 13.

2 Content Policies

The following policies apply to content and metadata (including publisher name, extension name, extension icon, extension description, extension screenshots, extension trailers and trailer thumbnails, and any other extension metadata) offered for distribution in Microsoft Edge Add-ons. Content means the images, sounds, videos and text contained in your extension, the tiles, notifications, error messages or ads exposed through your extension, and anything delivered from a server or to which your extension connects.

Because extensions and Microsoft Edge Add-ons are used around the world, these requirements are interpreted and applied in the context of regional and cultural norms.

2.1 Content Requirements for Microsoft Edge Add-on Catalog Listing

Metadata and other content you submit to accompany your extension may not contain mature content. Submissions that don't meet Microsoft Edge Add-ons store listings requirements are rejected or promptly removed.

2.2 Content Including Names, Logos, Original, and Third-party

All content in your extension and associated metadata must be either originally created by the you or appropriately licensed from a third-party rights holder and must be used only as permitted by the rights holder or as otherwise permitted by law.

2.3 Risk of Harm

2.3.1 Requirements

Your extension must not contain any content that facilitates or glamorizes the following real world activities: (a) extreme or gratuitous violence; (b) human rights violations; (c) the creation of illegal weapons; or (d) the use of weapons against a person, animal, or real or personal property.

2.3.2 Responsibility

Your extension must not: (a) pose a safety risk to, nor result in discomfort, injury or any other harm to end users or to any other person or animal; or (b) pose a risk of or result in damage to real or personal property. You are solely responsible for all extension safety testing, certificate acquisition, and implementation of any appropriate feature safeguards.

You must not disable any platform safety or comfort features and you must include all applicable legally required and industry-standard warnings, notices, and disclaimers in your extension.

2.4 Defamatory, Libelous, Slanderous, and Threatening

Your extension must not contain any content that is defamatory, libelous, slanderous, or threatening.

2.5 Offensive Content

Your extension and associated metadata must not contain potentially sensitive or offensive content. Content may be considered sensitive or offensive in certain countries/regions because of local laws or cultural norms. In addition, your extension and associated metadata must not contain content that advocates discrimination, hatred, or violence based on considerations of race, ethnicity, national origin, language, gender, age, disability, religion, sexual orientation, status as a veteran, or membership in any other social group.

2.6 Alcohol, Tobacco, and Drugs

Your extension must not contain any content that facilitates or glamorizes excessive or irresponsible use of alcohol or tobacco products or drugs.

2.7 Adult Content

Your extension must not contain or display content that a reasonable person would consider pornographic or sexually explicit.

2.8 Prohibited Content, Services, and Activity

Your extension must adhere to the following conditions.

  • Your extension must not contain content or provide services that facilitate online gambling. Online gambling includes but is not limited to online casinos, sports betting, lotteries, or games of skill that offer prizes of cash or other value.

  • Your extension must not provide unauthorized access to website content, such as by circumventing paywalls or login restrictions.

  • Your extension must not provide, encourage, or enable the unauthorized access, download, or streaming of copyrighted content or media.

  • Your extension must not mine cryptocurrency.

2.9 Illegal Activity

Your extension must not contain content or functionality that encourages, facilitates or glamorizes illegal activity in the real world.

2.10 Excessive Profanity and Inappropriate Content

  • Your extension must not contain excessive or gratuitous profanity.

  • Your extension must not contain or display content that a reasonable person considers obscene.

2.11 Country/Region Specific Requirements

Content that is offensive in any country/region to which your extension is targeted is not allowed. Content may be considered offensive in certain countries/regions because of local laws or cultural norms. Examples of potentially offensive content in certain countries/regions include the following:


  • Prohibited sexual content.
  • Disputed territory or region references.
  • Providing or enabling access to content or services that are illegal under applicable local law.

2.12 Age Ratings

2.12.1 Mature Content

When you submit your extension to Partner Center, you must indicate whether your extension displays content that should be marked "Mature". When determining the rating for your extension, consider all the content in your app, including user generated content and ads, and to the content that your extension links. If you indicate that your extension doesn't contain any "Mature" content, you are responsible for maintaining the accuracy of this rating.

Regardless of the rating given to your extension, it must still adhere to all the content requirements of Microsoft Edge Add-ons Developer policies.

2.12.2 Ratings Change

If your extension provides content (such as user-generated, retail, or other web-based content) that might be appropriate for a higher age rating than the assigned rating, you must require users to opt into receiving such content by using a content filter or by signing in with a pre-existing account.

2.13 Videos

If you submit a promotional video in the listing, it should follow all the content guidelines mentioned in this policy. If you choose to provide a YouTube link, you must ensure that advertisements are turned off for the specific videos that you want to embed. For more information on turning on or off ads on YouTube, see Set your default ad formats and Ads on embedded videos.

Edge Add-ons Certification Complaint and Appeal Process

All the extensions should adhere to the store policies listed above. If your extension failed in the review process, please review the store policies to understand the reason for failure. After submitting your extension using Partner Center, to ask a question about the review or certification status of it, go to New Support Request and complete the form.

Microsoft Edge Add-ons appeal statistics for FY2021

Numbers as reported on 8/1/2022

Statistic Count
App and/or Account Enforcement Action Appeals 42
Complaints about Technological Issues 27
Regulatory Compliance Complaints 0
Questions about certification, policy, submission, and technical help 76
Miscellaneous 15
Total Issues 160
Overturned decisions 8
Average Processing Time 3.6 days