Microsoft Outlook On Mac Not Compatible


Office 2019 is compatible with Windows 10 and the three most recent versions of macOS. Outlook 'Manage email more efficiently' Updated contact cards. Office 365 Groups. @mentions. Microsoft Office 2019 for Mac provides 5 years of mainstream support. This 5-year term is aligned with the support model for Office 2016 for Mac.

This article describes the software and device requirements for running Office Add-ins.

Not Compatible With Windows


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 host and availability page).

For a high-level view of where Office Add-ins are currently supported, see Office Add-in host and platform availability.

Server requirements

Microsoft Outlook On Mac Not Compatible Iphone

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.

For 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.

While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. 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. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine.


When you develop and debug an add-in in Visual Studio, Visual Studio deploys and runs your add-in's webpage files locally with IIS Express, and doesn't require an additional web server.

For content and task pane add-ins, in the supported Office host applications - Excel, PowerPoint, Project, or Word - you also need an app catalog on SharePoint to upload the add-in's XML manifest file.

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.


POP and IMAP email accounts in Outlook don't support Office Add-ins.

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.


    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.

Client requirements: 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)

Client requirements: 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).

Client requirements: 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.

Host applicationDeviceOperating systemExchange accountMobile browser
Outlook on AndroidAndroid tablets and smartphonesAndroid 4.4 KitKat laterOn the latest update of Office 365 for business or Exchange OnlineNative app for Android, browser not applicable
Outlook on iOSiPad tablets, iPhone smartphonesiOS 11 or laterOn the latest update of Office 365 for business or Exchange OnlineNative app for iOS, browser not applicable
Outlook on the webiPhone 4 or later, iPad 2 or later, iPod Touch 4 or lateriOS 5 or laterOn Office 365, Exchange Online, or on premises on Exchange Server 2013 or laterSafari


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 also


Windows Telemetry

For Outlook add-ins to load and function properly, there are a number of requirements for both the servers and the clients.

Client requirements

Microsoft Office For Mac

  • The client must be one of the supported hosts for Outlook add-ins. The following clients support add-ins:

    • Outlook 2013 or later on Windows
    • Outlook 2016 or later on Mac
    • Outlook on iOS
    • Outlook on Android
    • Outlook on the web for Exchange 2016 or later and Office 365
    • Outlook on the web for Exchange 2013
    • Outlook.com
  • The client must be connected to an Exchange server or Office 365 using a direct connection. When configuring the client, the user must choose an Exchange, Office 365, or Outlook.com account type. If the client is configured to connect with POP3 or IMAP, add-ins will not load.

Mail server requirements

If the user is connected to Office 365 or Outlook.com, mail server requirements are all taken care of already. However, for users connected to on-premises installations of Exchange Server, the following requirements apply.

  • The server must be Exchange 2013 or later.
  • Exchange Web Services (EWS) must be enabled and must be exposed to the Internet. Many add-ins require EWS to function properly.
  • The server must have a valid authentication certificate in order for the server to issue valid identity tokens. New installations of Exchange Server include a default authentication certificate. For more information, see Digital certificates and encryption in Exchange 2016 and Set-AuthConfig.
  • To access add-ins from AppSource, the client access servers must be able to communicate with AppSource.

Add-in server requirements

Add-in files (HTML, JavaScript, etc.) can be hosted on any web server platform desired. The only requirement is that the server must be configured to use HTTPS, and the SSL certificate must be trusted by the client.

See also