Microsoft AppSource submission FAQ

This topic answers common questions about submitting add-ins to Microsoft AppSource via Partner Center.

For the most current version of the certification policies, see Certification policies.

How can I avoid errors when submitting my add-in to Microsoft AppSource?

To avoid common submission errors:

  • Make sure that the version number on the submission form matches the version number in the add-in manifest.


    Specify your add-in version using the following syntax: a . b . c . d Where a is an integer between 1-9999, and each of b , c , d are each integers between 0-9999. For example:

  • Make sure that all locations are SSL-secured (HTTPS).

  • Make sure you that you specify an icon in your manifest, and that the icon is correctly sized and formatted.

  • Make sure your ID is unique. For example, do not create a manifest for a second add-in based on another add-in manifest you submitted without changing the ID in the new manifest.

  • For Office Add-ins, make sure that you are using manifest schema version 1.1. For information about updating your manifest to version 1.1, see Update to the latest JavaScript API for Office library and version 1.1 add-in manifest schema.

  • For Office Add-ins, make sure that you specify a support URL in the SupportUrl element of your Office Add-in manifest. Your support URL should be a publicly available webpage, and should not require authentication. You cannot use personal social media pages or GitHub repositories for the support URL. You also can't use links to files hosted online such as a Word document on OneDrive, DropBox or Google Docs.

  • For all add-ins, make sure that your manifest is valid against the schema. For schema validation information, see Schema reference for Office Add-ins manifests (v1.1) or Schema reference for manifests of SharePoint Add-ins.

  • Make sure your app or add-in is tested and is fully functional.

  • Make sure your SharePoint Add-ins specify their supported locales.

    If you don't specify supported locales, your add-in will not be accepted by Microsoft AppSource. For details, see Locale support information is required for all add-ins.

  • Make sure your OAuth client IDs match

    If your SharePoint Add-in accesses services using OAuth, make sure the OAuth client ID that you created matches the client ID in your add-in manifest.

  • Your SharePoint Add-in package must conform to the Open Packaging Convention.

  • Make sure that you submit a privacy link.

  • Make sure that any video links you submit actually go to a video file or a page that includes a video.

  • If your Office Add-in is available on iOS, do not include "app" in the Add-in Title or Add-in Short Description.

If I make updates to my submission, when do I have to resubmit it to Microsoft AppSource?

If you make updates to the web service for your add-in, you do not have to resubmit it. However, if you make changes to any items or data you submitted via Partner Center, such as the manifest, screenshots, or icon, you need to resubmit it so that Microsoft AppSource can implement those changes. You must resubmit add-ins with an updated manifest that includes a new version number. You must also make sure to update the version number in the submission form to match the version number of the new manifest.

What happens when I update my add-in to a new version in Microsoft AppSource?

The following is the update process for Office Add-ins:

  • You submit your revised add-in and add-in manifest to Microsoft AppSource via Partner Center. The revised add-in goes through the validation process, and when approved, is made available in Microsoft AppSource.


If your submission is an update and you schedule the availability of your add-in to a date in the future, your existing add-in will be unpublished from Microsoft AppSource until the release date you specified.

  • You can choose to continue to offer the previous version of your add-in in Microsoft AppSource, or you can unpublish the previous version.

  • When an existing customer launches the updated add-in for the first time, a notification appears either in the task pane or the body of the document that prompts the user to update their add-in. When the user chooses Update, the latest version of the add-in launches.

    If the updated version includes new permissions, the user must consent to them.


You cannot have two or more versions of the same add-in in Microsoft AppSource at the same time, because each add-in has a unique asset ID. If you publish an updated version of your add-in without unpublishing a previous version, you will have two listings and will potentially split your customer base.

Updates to SharePoint Add-ins are handled by the license-management tools that are part of the SharePoint Add-in catalog. For more information, see SharePoint Add-ins update process.

Can I submit a paid app or add-in to Microsoft AppSource?

All add-ins submitted to Microsoft AppSource via Partner Center are free. For details, see Moving from paid to free add-ins. You can monetize your add-in through the Microsoft Commercial Marketplace; for details, see Monetize your add-in.

How do I reference the JavaScript APIs for Office in my add-ins?

If your add-in uses the JavaScript APIs for Office, you must reference the Microsoft-hosted Office.js file from its CDN URL. Don't include a copy of the Office.js file in your add-in, or reference a copy of the file hosted elsewhere.

Why do my add-ins have to be SSL-secured?

Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. For this reason, all add-ins submitted to Microsoft AppSource are required to be SSL-secured.

How do I declare language support?

Two aspects of your submission relate to supported languages:

  1. The languages you declare in your app package or manifest. You declare which languages your add-in supports differently depending on type:

  2. In Partner Center, you can select languages on the Store listings page.


    You can declare more languages in your add-in package than are available for submission in Partner Center.

See also