Supported client and server environments for Outlook Add-in

In this article:

Server requirements
Client requirements
API requirements


Note: Even when all the client and server requirements are met, a non-admin user may still not be able to install the Add-in because the admin might have disabled the Add-in option.


Server requirements

To test and run an Outlook add-in, the user’s Outlook email account must reside on Exchange 2013 or later, which is available through Office 365, Exchange Online, or through an on-premises installation. The user or administrator installs manifest files for Outlook add-ins on that server.

Note: POP and IMAP email accounts in Outlook don’t support Office Add-ins.

See here for more information on server requirements.


Client requirements

Windows desktop and tablet

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:

  • For Windows x86 and x64 desktops, and tablets such as Surface Pro:
    • The 32- or 64-bit version of Office 2013 or a later version, running on Windows 7 or a later version.
    • 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. Office desktop clients can be installed on-premises or via Click-to-Run on the client computer.

    If you have a valid Office 365 subscription and you do not have access to the Office client, you can download and install the latest version of Office.

  • 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. 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. See Browsers used by Office Add-ins for more details.

Note: Internet Explorer’s Enhanced Security Configuration (ESC) must be turned off for Office Web Add-ins to work. If you are using a Windows Server computer as your client when developing add-ins, note that ESC is turned on by default in Windows Server.

  • One of the following as the default browser: Internet Explorer 11, or the latest version of Microsoft Edge, Chrome, Firefox, or Safari (Mac OS).
  • An HTML and JavaScript editor such as Notepad, Visual Studio and the Microsoft Developer Tools, or a third-party web development tool.


OS X desktop

Outlook on Mac, which is distributed as part of Office 365, supports Outlook add-ins. Running Outlook add-ins in Outlook on Mac has the same requirements as Outlook on Mac itself: the operating system must be at least OS X v10.10 “Yosemite”. Because Outlook on Mac uses WebKit as a layout engine to render the add-in pages, there is no additional browser dependency.

The following are the minimum client versions of Office on Mac that support Office Add-ins.

  • Word version 15.18 (160109)
  • Excel version 15.19 (160206)
  • PowerPoint version 15.24 (160614)


Browser support for Office web clients and SharePoint

Any browser that supports ECMAScript 5.1, HTML5, and CSS3, such as Internet Explorer 11, or the latest version of Microsoft Edge, Chrome, Firefox, or Safari (Mac OS).


Non-Windows smartphone and tablet

Specifically for Outlook running in a browser on smartphones and non-Windows tablet devices, the following software is required for testing and running Outlook add-ins

Note: The native apps OWA for Android, OWA for iPad, and OWA for iPhone have been deprecated and are no longer required or available for testing Outlook add-ins.

See here for more information on client requirements.


API requirements

The minimum API requirement sets for TimeSolv Add-in is Mailbox 1.3.

The user must make sure that their server environment supports this requirement.

See here for more information to determine if your platform meets the minimum API requirement sets.



Related Post