Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Publish your Office Add-in

Office Add-ins

Make your add-ins available to users via an add-in catalog, a shared folder, or an Exchange server. Extend the reach of your add-ins to your end users.

Last modified: September 28, 2015

Applies to: Access apps for SharePoint | apps for Office | Excel | Office Add-ins | Outlook | PowerPoint | Project | Word

Learn more about supported hosts and other requirements.

Note Note

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

In this article
Publishing task pane and content add-ins to an add-in catalog
Publishing task pane and content add-ins to a shared network folder
Publishing mail add-ins to an Exchange server
Add-in experience for end users
Broaden the reach for your add-in
Additional resources

You can publish your add-ins to the Office Store or upload them to a private shared folder add-in catalog on SharePoint, a shared network folder, or an Exchange server. The options that are available depend on the type of add-in you create.

Options for publishing Office and SharePoint Add-ins


Office Store

Corporate add-in catalog

Shared folder add-in catalog

Exchange server

Task pane add-in




Content add-in




Mail add-in



Note Note

For information about publishing to the Office Store, see Upload Office and SharePoint Add-ins and Office 365 web apps to the Office Store.

Before you publish your add-in, you'll need to package it by using Napa or Visual Studio. In addition to making your add-ins available to end users, you'll want to consider how you can broaden your add-in's reach.

For task pane and content add-ins, IT departments can deploy and configure private corporate add-in catalogs to provide the same Office-solution catalog experience that the Office Store provides. This new catalog and development platform lets IT use a streamlined method to provision Office and SharePoint Add-ins to managed users from a central location without the need to deploy solutions to each client. You can then use the telemetry tool to monitor add-in usage, verify compatibility, and troubleshoot end user issues. To learn more, see:

Alternatively, in a corporate setting, IT can deploy task pane and content add-ins created either by in-house or third-party developers to a shared network folder, where the manifest files will be stored and managed. In either case, when developers update their add-ins, they don't have to push updates to end users or IT does not have to redeploy them to corporate users. For information about setting up a shared network folder add-in catalog, see Create a network shared folder catalog for task pane and content add-ins.

Mail add-ins are published to an Exchange catalog that is available to users of the Exchange server on which it resides. It enables publishing and management of mail add-ins, including internally created ones as well as solutions that are acquired from the Office Store and licensed for corporate use. Mail add-ins are installed into an Exchange catalog by using either the Exchange Admin Center (EAC) or by running remote Windows PowerShell commands (cmdlets). For information about publishing a mail add-in, see Deploy and install mail add-ins for testing in Outlook.

Add-ins are easy for end users to acquire, insert, and run. Users have the same experience regardless of whether they access add-ins from any of the following:

  • The public Office Store, by using their Microsoft account.

  • A SharePoint add-in catalog, by using their company ID.

  • A shared network folder.

  • An Exchange server.

To acquire a new task pane add-in in Excel, for example, users log on to Office with their Microsoft account, open an Excel workbook, and select My Add-ins on the Insert tab of the ribbon. The Office Add-ins dialog box appears.

In the Office Add-ins dialog box, the user chooses Find more add-ins at the Office Store. After users log on to Office.com, using the same Microsoft account, they can download the add-in of their choice and pay for it with a credit card.

In Excel, in the Office Add-ins dialog box, the user chooses Refresh, selects the add-in they downloaded, and then chooses Insert.

When they sign in to their account, they have access to their add-ins from any computer, anywhere, including those running Office 365.

To ensure that your add-in reaches more end users, make sure that it works across platforms. The Office.js version 1.1 includes support for Office Online, and the Office Store validation process verifies add-in support for Office Online. Before you publish, test your add-in to make sure that it works in Office Online.

To make your add-in available in the Office Store, see Upload Office and SharePoint Add-ins and Office 365 web apps to the Office Store.

Office Add-ins are also supported on Office for iPad. Make sure to test your add-in on the iPad before you submit it to the Seller Dashboard. When you have verified that your add-in works as expected, you can mark your submission as iOS-compatible in the Seller Dashboard. For validation, you will need to provide your Apple developer ID. See also Debug Office Add-ins on iPad

To address user issues with your add-ins, see Troubleshoot user errors with Office Add-ins.

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