Only show these results:

Microsoft guide for Email Administrators

⛔️ As of October 1, 2022, Microsoft has deprecated Basic authentication support for all Exchange Online accounts. For more information, see Nylas' Microsoft Exchange Online Basic authentication changes guide.

If you're an Email Administrator, there are a few things you can do to make sure your organization gets the most out of Nylas. This page explains recommended setups, best practices, and some basic troubleshooting for working with Microsoft accounts.

The following recommended settings apply to all setups:

  • Nylas recommends using Modern Authentication or OAuth for all Microsoft accounts.
  • End users cannot use an alias to authenticate with Nylas.
  • If an email account requires two-factor authentication (2FA), the end user needs to use their app password to sign in.
  • If you're working with Office 365, Nylas recommends reviewing the suggested Office 365 settings.

The following recommendations apply to accounts using Office 365 only:

  • If you're using Basic authentication and your app passwords aren't enabled, you won't be able to integrate with Nylas. To resolve this, you can either enable app passwords, or enable Modern Authentication or OAuth.
    • If you choose to set up Modern Authentication or OAuth, follow the steps in Create an Azure App to set up OAuth for Office 365.
  • If the account is accessible only through a corporate network, a VPN, or a firewall, you must allow Nylas to connect to the account.
  • During the development process, you might be asked to approve your Azure app if you're using Modern Authentication or OAuth.
  • You might need to add Nylas IP addresses to your allowlist. You can find a list of current IP addresses by making a v2 Get IP Addresses request. Keep in mind that these IP addresses may change at any time.
  • Nylas cannot sync end user accounts that are in admin groups. This is a limitation on the provider.
  • If your application uses Exchange Web Services (EWS) scopes and Nylas cannot connect to the app, it falls back to using Exchange ActiveSync (EAS).

The following recommendations apply to accounts using Microsoft Exchange only:

  • Set up a Microsoft Exchange login process.
  • If the account is accessible only through a corporate network, a VPN, or a firewall, you must allow Nylas to connect to the account.
  • Be sure to enable Exchange ActiveSync (EAS) outside of the corporate network, and check the quarantine list for any Nylas connections.
    • If your application requires access to contacts, you must use EAS, and the Contacts scope must be enabled for both Nylas and your Azure project.
  • Make sure to turn on Exchange Web Services (EWS). EWS must be visible outside of the corporate network, and enabled for the account's individual mailbox.
    • Because Nylas uses EWS to sync email messages and calendars, your end users must have it enabled. If you cannot get your end users to enable EWS, contact Nylas Support for help enabling EAS.
  • If auto-discovery is available, Nylas attempts to use it. If it's not available, you must provide all settings information.
    • If an end user has to enter server settings information, Nylas cannot use auto-discovery.
  • During the development process, you might be asked to approve your Azure app if you're using Modern Authentication or OAuth.

Troubleshooting

Below are some common issues you might experience as you configure your Microsoft setup: