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.

If your SharePoint Add-in accesses services using OAuth, make sure the OAuth client ID that you created in the 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 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 AppSource?

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

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

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

Important: The Release date field controls the date on which your add-in will be made available after it passes validation. If your submission is an update and you set this field to a date in the future, your existing add-in will be unpublished until the release date you specified.

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

You cannot have two or more versions of the same add-in in 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 AppSource 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 AppSource?

You can now submit paid apps and add-ins to AppSource 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 AppSource. Paid SharePoint Add-ins that contain Office Add-ins are not 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 AppSource? and policy 10.2 in the validation policies.

In addition, consider the following:

If you submit a paid app or add-in, you can also choose to offer a trial. If you choose to submit a trial offer, we recommend that you use the Office licensing framework.