Office Store app and add-in submission FAQ

Office and SharePoint Add-ins

Find information about submitting your Office 365 web app or Office and SharePoint Add-ins to the Office Store.

Last modified: September 13, 2016

Applies to: apps for Office | apps for SharePoint | Office 365 | Office Add-ins | Office Mix add-ins | SharePoint Add-ins

For the most current version of the validation policies, see Validation policies for apps and add-ins submitted to the Office Store (version 1.9).

To avoid common submission errors:

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

    Note Note

    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 for your app or add-in in your package or manifest, and that the icon is correctly sized and formatted. For details, see Checklist for submitting Office and SharePoint Add-ins and Office 365 web apps to the Seller Dashboard.

  • 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 the version of your JavaScript API for Office and manifest schema files.

  • For Office Add-ins, make sure that you specify a Support URL in the SupportUrl element of your Office Add-in manifest.

  • 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 the Office Store. For details, see Locale support information is required for all add-ins in the Office Store.

  • 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 in Seller Dashboard 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 any video links you submit actually go to a video file or a page that includes a video.

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

If you make updates to the web service for your add-in, you do not have to resubmit it to the Office Store. However, if you make changes to any items or data you submitted for your app or add-in via the Seller Dashboard, such as the manifest, screenshots, icons, or submission form data, you’ll need to resubmit so that the Office Store 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.

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

  • You submit your revised add-in and add-in manifest to the Office Store via the Seller Dashboard. The revised add-in goes through the validation process, and when approved, is made available in the store.

  • You can choose to continue to offer the previous version of your add-in in the store, or you can unpublish the previous version via the Seller Dashboard. For details, see Update, unpublish, and view app and add-in metrics in the Seller Dashboard.

  • 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.

Note Note

You cannot have two or more versions of the same add-in in the store 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 Office Store 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.

You can now submit paid apps and add-ins to the Office Store through the Seller Dashboard, with the following restrictions:

  • If your SharePoint Add-in contains an Office Add-in, it must be priced as free in the Office Store. Paid SharePoint Add-ins that contain Office Add-ins will not be accepted until these commerce capabilities are enabled.

  • Additional restrictions apply to autohosted add-ins. For information, see Can I submit an autohosted SharePoint Add-in to the Office Store? and policy 10.2 in Validation policies for apps and add-ins submitted to the Office Store (version 1.9).

In addition, consider the following:

For paid apps and add-ins in the Office Store, 20% goes to Microsoft.

The Office 365 Autohosted Add-ins Preview program ended on June 30, 2014. You cannot create new autohosted add-ins in SharePoint. For more information, see Update on Autohosted Add-ins Preview program. For information about how to convert your autohosted add-in, see Convert an autohosted SharePoint Add-in to a provider-hosted add-in.

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.

Apps and add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. For this reason, all apps and add-ins submitted to the Office Store are required to be SSL-secured.

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 your Seller Dashboard submission first step, you select a default language . As a second step, you can add additional languages via Add A Language.

    Note Note

    You can declare more languages in your or add-in package than are available for submission in Seller Dashboard.