Method | Use... |
---|---|
Sideloading | As part of your development process, to test your add-in running on Windows, iPad, Mac, or in a browser. (Not for production add-ins.) |
Network share | As part of your development process, to test your add-in running on Windows after you have published the add-in to a server other than localhost. (Not for production add-ins or for testing on iPad, Mac, or the web.) |
Centralized Deployment | In a cloud deployment, to distribute your add-in to users in your organization by using the Microsoft 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. |
Extension point | Sideloading | Network share | Microsoft 365 admin center | AppSource | SharePoint catalog* |
---|---|---|---|---|---|
Content | X | X | X | X | X |
Task pane | X | X | X | X | X |
Command | X | X | X | X |
Extension point | Sideloading | Exchange server | AppSource |
---|---|---|---|
Mail app | X | X | X |
Command | X | X | X |
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.