Deploy and publish your Office Add-in
You can use one of several methods to deploy your Office Add-in for testing or distribution to users.
|Sideloading||As part of your development process, to test your add-in running on Windows, Office Online, iPad, or Mac.|
|Centralized Deployment||In a cloud or hybrid deployment, to distribute your add-in to users in your organization by using the Office 365 admin center.|
|SharePoint catalog||In an on-premises environment, to distribute your add-in to users in your organization.|
|AppSource||To distribute your add-in publicly to users.|
|Exchange server||In an on-premises or online environment, to distribute Outlook add-ins to users.|
|Network share||On a Windows computer on a network where you want to host your add-in, go to the parent folder, or drive letter, of the folder you want to use as your shared folder catalog.|
If you plan to publish your add-in to AppSource and make it available within the Office experience, make sure that you conform to the AppSource validation policies. For example, to pass validation, your add-in must work across all platforms that support the methods that you define (for more information, see section 4.12 and the Office Add-in host and availability page).
Deployment options by Office host
The deployment options that are available depend on the Office host that you're targeting and the type of add-in you create.
Deployment options for Word, Excel, and PowerPoint add-ins
|Extension point||Sideloading||Office 365 admin center||AppSource||SharePoint catalog*|
* SharePoint catalogs do not support Office for Mac.
Deployment options for Outlook add-ins
|Extension point||Sideloading||Exchange server||AppSource|
The following sections provide additional information about the deployment methods that are most commonly used to distribute Office Add-ins to users within an organization.
For information about how end users acquire, insert, and run add-ins, see Start using your Office Add-in.
Centralized Deployment via the Office 365 admin center
The Office 365 admin center makes it easy for an administrator to deploy Office Add-ins to users and groups in their organization. Add-ins deployed via the admin center are available to users in their Office applications right away, with no client configuration required. You can use Centralized Deployment to deploy internal add-ins as well as add-ins provided by ISVs.
For more information, see Publish Office Add-ins using Centralized Deployment via the Office 365 admin center.
SharePoint catalog deployment
A SharePoint add-in catalog is a special site collection that you can create to host Word, Excel, and PowerPoint add-ins. Because SharePoint catalogs don't support new add-in features implemented in the
VersionOverrides node of the manifest, including add-in commands, we recommend that you use Centralized Deployment via the admin center if possible. Add-in commands deployed via a SharePoint catalog open in a task pane by default.
If you are deploying add-ins in an on-premises environment, use a SharePoint catalog. For details, see Publish task pane and content add-ins to a SharePoint catalog.
SharePoint catalogs do not support Office for Mac. To deploy Office Add-ins to Mac clients, you must submit them to AppSource.
Outlook add-in deployment
For on-premises and online environments that do not use the Azure AD identity service, you can deploy Outlook add-ins via the Exchange server.
Outlook add-in deployment requires:
- Office 365, Exchange Online, or Exchange Server 2013 or later
- Outlook 2013 or later
To assign add-ins to tenants, you use the Exchange admin center to upload a manifest directly, either from a file or a URL, or add an add-in from AppSource. To assign add-ins to individual users, you must use Exchange PowerShell. For details, see Install or remove Outlook add-ins for your organization on TechNet.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.