[KB6298] Install and setup ESET Secure Authentication with Microsoft Outlook Web Access (OWA)


  • Integrate ESET Secure Authentication with OWA
  • Best practices for securing access to Microsoft Exchange services


Before installing the ESET Secure Authentication application on your device

Before you can use the ESET Secure Authentication app on your mobile phone, you must install and configure the ESET Secure Authentication core service on your server and then provision the devices you want to use with the ESET Secure Authentication mobile app.

The instructions below detail the configuration of ESET Secure Authentication for use with Microsoft Outlook Web Access. For more information on server setup and provisioning, or to configure ESET Secure Authentication for use with a VPN, see the ESET Secure Authentication Installation Manual.

If after configuring the ESET Secure Authentication core service you are still experiencing issues, visit our ESET Secure Authentication (ESA) Setup Checklist.


The instructions below require the following prerequisites:

  • A working OWA environment
  • Access to an account with "Domain Administrator" privileges
  • A valid ESET Secure Authentication license

For further information, see the ESET Secure Authentication (ESA) Setup Checklist and the ESET Secure Authentication Installation Manual.


  1. Download the ESET Secure Authentication installer file.
  2. On the system providing the OWA environment, run the installer file with Admin rights.
  3. Review the license agreement and click I accept.

Figure 1-1

  1. Select the appropriate deployment type for the installation and click Next.

    Figure 1-2

  2. Make sure all startup checks are Successful and then click Next.

Figure 1-3

  1. Select which components you want to install and click Next. The following components are required:

    • Authentication Server 

      Do not install the Authentication Server unless the current system is also the system providing ESA services to other systems in the network

    • Microsoft Exchange Server

Figure 1-4

  1. Click Close when the installation completes.

Figure 1-5


  1. Open the ESET Secure Authentication web console.
  2. Click Settings > License, and then select the applicable license type.
Figure 2-1
  1. Enter the License Key and click Activate (or Reactivate).  
Figure 2-2
  1. Click Settings > Mobile Application, specify a token name and click Save.

    The Token Name will be shown to users using the ESET Secure Authentication app on their mobile devices

    For this example, "Demo Company" is used. 

Figure 2-3

  1. Click Components and make sure the slider bar next to 2FA is enabled is selected for both Exchange Control Panel and Outlook Web App.

    For enhanced security, we recommend deselecting the check box next to Allow NON-2FA for both Exchange Control Panel and Outlook Web App.

Figure 2-4

  1. Click Settings > IP Whitelisting and select the check box next to Enable per feature IP whitelisting and Outlook Web App. Type the following two addresses (for IPv6 and IPv4) to ensure that IT administrators cannot be completely locked out from the system if they are not able to use MFA:
    • ::1

It is possible to enable ESA for external IP addresses only by adding your own internal IP ranges to the whitelist

To allow all internal addresses to log in without using ESA, add the following IP ranges:

  1. Select the check box next to Exchange Control Panel to enable it.

Figure 2-5

Enroll Users

To allow access to ESET Secure Authentication, users need to be configured for one of the available Token Types. The most basic Token Type is SMS-Based OTP. To enable this token, make sure that all users have a mobile phone number configured for their account.

If all users have their mobile phone number set, follow the instructions below. 


  • If you need to allow a user to use a mobile application, select the check box next to Mobile Application OTP and then click Save.
  • Click Actions > Send Application and an SMS will be sent to the user containing all the information needed to install and provision the mobile application. For more information, see one of the following Knowledgebase articles for your mobile device:

    Windows Phone

  1. Click Users and select the applicable Realm.
  2. Click the User name you want to enroll.

    Figure 3-1

  3. Confirm that a valid phone number is entered, click the slider bar next to the token type you want to send to enable it, then click Actions and select Send Application.

    Figure 3-2

This user is now configured to use the assigned OTP. When the user attempts to log in to OWA, ESET Secure Authentication will request the user's OTP.

Enable Push token on Android mobile devices

If you want to use a push token instead of the SMS-Based OTP, follow the instructions below.

  1. Click Users and select the applicable Realm.
  2. Select the check box next to each user name you want to enable the push token for.

  3. Click 2FA, select Enable > Application Push

    Figure 4-1

ESET Secure Authentication will display a randomly generated login ID and on the currently enrolled device, the user will receive a push notification asking to Approve or Reject the authentication attempt.

Harden Exchange Services

This section provides some security best practices. 

A default installation of Microsoft Exchange Server will also provide a number of other services to the internet including ActiveSync and Exchange Web Services (EWS). Research shows that some of these services can be used to bypass MFA solutions such as ESET Secure Authentication. To prevent this, we strongly recommend that you limit access to these services from outside the company network.


Microsoft ActiveSync allows mobile devices to easily connect to Microsoft Exchange. ESET Secure Authentication does not support Microsoft ActiveSync and therefore, we recommend that you limit access to this service.

We recommend that you specify only certain devices (for example, company phones) to connect via ActiveSync. This can be done through the Exchange Control Panel as well as the Exchange Management Shell.

Exchange Services

For all publicly available services, we recommend that you restrict access to the following services based on IP addresses:

  • Autodiscover
  • EWS
  • mapi
  • Microsoft-Server-ActiveSync
  • OAB
  • PowerShell
  • Rpc
  1. To set these restrictions, open the OWA website in the Internet Information Services (IIS) Manager and navigate to IP Address and Domain Restrictions for each of the services listed above.

If IP Address and Domain Restrictions is not available

If IP Address and Domain Restrictions is not available, it may need to be installed separately. See https://technet.microsoft.com/en-us/library/cc725769(v=ws.10).aspx.

  1. In the Actions window, click Edit Feature Settings.
  2. From the Access for unspecified clients drop-down menu, select Deny.
  3. From the Deny Action Type drop-down menu, select Not Found.

    Security best practice

    For security reasons we recommend that you also change the “Deny Action Type” to “Not Found”. This can deter automated scanners and inexperienced attackers looking for Microsoft Exchange servers to attack.

Figure 5-1

  1. Click Add Allow Entry and in the Specific IP address field, add the following addresses (to prevent the system itself from being unable to access certain resources it might need during operation):
    • ::1

Optionally, the following addresses can be added to allow access from the internal network

  • IP address range: – Mask or Prefix: 8
  • IP address range: – Mask or Prefix: 12
  • IP address range: – Mask or Prefix: 16
  1. Repeat steps 1– 5 for all services.