Validation policies for apps FAQ

apps for Office and SharePoint

Find information about submitting your app to the Office Store.

Last modified: April 01, 2015

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

Note Note

The names "apps for Office" and "apps for SharePoint" are changing to "Office Add-ins" and "SharePoint Add-ins". During the transition, the documentation and the UI of some Office and SharePoint products and Visual Studio tools might still use the terms "apps for Office" and "apps for SharePoint".

In this article
What are some common errors to avoid when submitting my app to the Office Store?
If I make updates to my app, when do I have to resubmit it to the Office Store?
Can I submit a paid app to the Office Store?
Can I submit an autohosted app for SharePoint to the Office Store?
Can I submit Access apps for SharePoint to the Office Store?
How do I reference the JavaScript APIs for Office in my apps?
Why do my apps have to be SSL-secured?
How do I declare language support for my app?
Additional resources

For the most current version of the validation policies, see Validation policies for apps submitted to the Office Store (version 1.7).

To help make your app submission as trouble-free as possible, we’ve listed some common submission errors, and how to avoid them, below:

  • Make sure that the app version number on the submission form exactly matches the app version number in the app version manifest.

    Note Note

    You must specify your app 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 app locations are SSL-secured (HTTPS).

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

    • For apps for Word, Excel, and Project, you are required to link to an image using the <IconUrl> element in the app manifest. The image specified must be 32 pixels by 32 pixels.

      For more information, see IconUrl.

    • For mail apps, you are required to link to an image using the <IconUrl> element in the app manifest. The image specified must be secured with HTTPS. This image is shown as the 64 pixels by 64 pixels image associated with your app in the installed apps dialogue. For best customer experience, specify a 64 pixel by 64 pixel image for the IconUrl element in app manifests for mail apps. Validation requires this image to be between 64 pixels by 64 pixels and 128 pixels by 128 pixels. The image must be in one of the following file formats: GIF, JPG, PNG, EXIF, BMP or TIFF

      For more information, see IconUrl.

    • For apps for SharePoint, you are required to include an icon in the app’s package. The image included must be 96 pixels by 96 pixels. The image that you include in your app’s package must match the image that you submit via the Seller Dashboard form.

  • Make sure your app’s ID is unique.

    A common mistake is creating a manifest for a second app based on a previously-submitted manifest and forgetting to change the app ID in the new manifest.

  • Make sure your app manifest is valid against the current manifest schema.

    For detailed manifest schema information, see Schema reference for apps for Office manifests (v1.1) and Schema reference for manifests of apps for SharePoint.

  • Make sure your app has been tested and is fully functional.

  • Make sure your apps for SharePoint specify their supported locales.

    You are required to specify supported locales, or your app will not be accepted by the Office Store. See Locale support information is required for all apps in the Office Store for details.

  • Make sure your OAuth client IDs match

    If your app for SharePoint accesses services using OAuth, make sure the OAuth client ID that you created in Seller Dashboard matches the client ID in your app manifest.

  • Make sure you specify a Support URL in the SupportUrl element of your app for Office manifest

  • Your app for SharePoint 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 containing a video related to your app.

One of the strengths of the app model is that, if you make updates to the web service for your app, you do not have to resubmit your app to the Office Store. However, if you make changes to any items or data you submitted for your app via the Seller Dashboard, such as the app manifest, screenshots, icons, or app submission form data, you’ll need to resubmit your app so that the Office Store can implement those changes. You must resubmit your app with an updated app manifest that includes a new version number. You must also make sure to update the app version number in the submission form to match the new manifest's version number.

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

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

  • Only mail apps priced as free are being accepted into the Office Store at this time.

  • Additional restrictions apply to autohosted apps.

    See Can I submit an autohosted app for SharePoint to the Office Store?, below, and policy 10.2 in Validation policies for apps submitted to the Office Store (version 1.7) for information on autohosted apps.

In addition, consider the following when deciding whether to submit a paid app:

The Office 365 Autohosted Apps Preview program will end on June 30, 2014. After June 30th, developers won't be able to create new autohosted apps in SharePoint. For more information, see Update on Autohosted Apps Preview program.

Yes, you can submit Access apps for SharePoint to the Office Store. The first set of approved apps will appear store by the end of 2013.

If your app 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 app, or reference a copy of the file hosted elsewhere.

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

There are two aspects of your app submission that relate to supported languages:

  1. The languages you declare in your app package or manifest

    You declare which languages your app supports differently depending on app type:

  2. As a first step to app submission, you will select a default language for the app in Seller Dashboard. As a second step, you are able to add additional languages via Add A Language.

    Note Note

    You can declare more languages in your app's package than are available for submission in Seller Dashboard.

© 2015 Microsoft