Internet Explorer's Enhanced Security Configuration (ESC) must be turned off for Office Web Add-ins to work. See Browsers used by Office Add-ins for more details. To support Office Add-ins, the Office client that acts as host uses browser components that are part of Internet Explorer 11 or Microsoft Edge. Internet Explorer 11 or Microsoft Edge (depending on the Windows and Office versions) must be installed but doesn't have to be the default browser.
If you have a valid Microsoft 365 subscription and you do not have access to the Office client, you can download and install the latest version of Office. Office desktop clients can be installed on premises or via Click-to-Run on the client computer. Excel 2013, Outlook 2013, PowerPoint 2013, Project Professional 2013, Project 2013 SP1, Word 2013, or a later version of the Office client, if you are testing or running an Office Add-in specifically for one of these Office desktop clients.
The 32- or 64-bit version of Office 2013 or a later version, running on Windows 7 or a later version.The following software is required for developing an Office Add-in for the supported Office desktop clients or web clients that run on Windows-based desktop, laptop, or tablet devices.įor Windows x86 and 圆4 desktops, and tablets such as Surface Pro: Client requirements: Windows desktop and tablet POP and IMAP email accounts in Outlook don't support Office Add-ins. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine. 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)
