If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. If you plan to run your add-in in Office on the web or publish your add-in to AppSource, it must be SSL-secured. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use.
While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. To be able to install and run any Office Add-in, you first need to deploy the manifest and webpage files for the UI and code of your add-in to the appropriate server locations.įor all types of add-ins (content, Outlook, and task pane add-ins and add-in commands), you need to deploy your add-in's webpage files to a web server, or web hosting service, such as Microsoft Azure. 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 Commercial marketplace certification 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 1120.3 and the Office Add-in application and availability page).įor a high-level view of where Office Add-ins are currently supported, see Office client application and platform availability for Office Add-ins.
0 kommentar(er)
