Export (0) Print
Expand All

Publish SharePoint Add-ins

SharePoint Add-ins

Find articles and resources to help you publish your apps for SharePoint.

Last modified: March 09, 2015

Applies to: apps for SharePoint | Office 365 | SharePoint Add-ins | SharePoint Foundation 2013 | SharePoint Server 2013

Note Note

The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see New name for apps for Office and SharePoint.

In this article
Get started with publishing your apps
Deciding where to publish your app for SharePoint
Additional resources

You've finished developing your app for SharePoint—the final step is making that app available to your users. You can do this by publishing the app to one of two places:

  • The public Office Store. Publish your app to the Office Store to make the app publically available, so that it can be acquired by users of any SharePoint deployment.

  • An internal organization app catalog. Publish your apps to an internal organization app catalog, hosted on your SharePoint deployment, to make them available to users with access to that SharePoint deployment.

For information about how to package your app for publication by using Visual Studio 2012, see Publish an SharePoint Add-ins by using Visual Studio.

Publishing to the Office Store

To publish an app to the Office Store, you must first sign up with the Microsoft Seller Dashboard. See Create or edit a Seller Dashboard seller account and add payout information.

When you upload an app to the Office Store for publication, Microsoft performs a series of verification checks to ensure your app adheres to the app content and behavior guidelines. For example, it checks whether the app manifest markup is valid and complete and verifies that any SharePoint solution packages (.wsp files) that are included in the app do not contain elements that aren't allowed, or SharePoint Features with a scope that is broader than Web. The package is also inspected for objectionable content. If the app package passes all tests, it's wrapped into a file and signed by Microsoft.

When you upload your app for publication on the Office Store, you can choose the terms of the license you want to offer users when they download it. Use this app license to decide:

  • Whether you are offering your app for free, trial, or for purchase.

  • Whether your app can be acquired on a per-user or site basis.

SharePoint does not enforce license terms for app usage—it provides a licensing framework that lets you include code logic in your app to enforce whatever licensing restrictions you choose. For example, you can include code logic in your app that enables users to access certain app features if they have a paid license, but not if they have a trial license. For more information, see License your Office and SharePoint Add-ins.

Publishing to an app catalog

If you're creating apps for SharePoint for your own company’s use or a specific corporate client, instead of the general public, you’ll likely want to publish your app to an internal app catalog hosted on SharePoint. A private app catalog is a dedicated site collection in a SharePoint 2013 web application (or a SharePoint Online tenancy) that hosts document libraries for apps for SharePoint and apps for Office. Putting the catalog into its own site collection makes it easier for the web application administrator or tenant administrator to limit permissions to the catalog.

Uploading an app for SharePoint to a corporate app catalog is as easy as uploading any file to a SharePoint document library. You fill out a pop-up form in which you supply the local URL of the app package and other information, such as the name of the app. When you upload the app to an app catalog, there are similar checks and apps that do not pass are marked as invalid or disabled in the catalog.

The following table offers a comparison of publishing to the Office Store or to an app catalog, and lists issues to consider when deciding where to publish your app. We recommend you decide where you plan to publish your app before you design and develop it; in some cases, such as licensing, where you publish your app will affect the design and development of your app.

Table 1. Considerations for where to publish your app

Office Store

App Catalog

App is publically available.

App is available to users with access to this SharePoint deployment

Licensing framework available.

Licensing framework is not available for use.

App package verified by Microsoft for technical and content adherence to policies.

App package verification performed by SharePoint when app is uploaded.

You must be signed up with Microsoft Seller Dashboard to upload apps.

No registration with Microsoft required.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft