Sophos UTM 9.4 WAF and Exchange 2016 (without RPCoverHTTP)

At the end of last year, I had already written an article on the subject of RPCoverHTTP, better known as Outlook Anywhere:

Exchange 2016: Is RPCoverHTTP still needed?

I therefore switched off Outlook Anywhere in my environment in December 2016. I have not encountered any problems so far. Outlook 2016 works perfectly with MAPIoverHTTP.

Now that more than two months have passed, I'm taking this opportunity to publish my current configuration of Sophos UTM Webserver Protection in conjunction with Exchange 2016. The environment is still the same. There is a domain controller and an Exchange 2016 with the current CU 4:

RPCoverHTTP

Since I don't want to constantly reinvent the wheel, this article is based on the original configuration, or the UTM configuration including RPCoverHTTP is adapted so that only MAPIoverHTTP is supported for Outlook remote access. ActiveSync and EWS remain unaffected and continue to function:

Sophos UTM 9.4 WAF and Exchange 2016

The UTM Web Application Firewall is configured as follows:

Real web server

First of all, the settings for the "real web server", in this case Exchange:

WAF

Here I have only adjusted the HTTP-Keep-Alive to the default setting of Exchange 2016.

Autodiscover Firewall Profile

I have left the Autodiscover Firewall profile unchanged:

Entry URLs:

/autodiscover
/autodiscover

Skip Filter Rules:

  • 960015
  • 960911

image

image

Web services firewall profile

I deactivated the option "Let Outlook Anywhere pass" in the firewall profile for the web services. I also adapted the initial URLs to support the future REST api:

/ecp
/ECP
/ews
/EWS
/Microsoft-Server-ActiveSync
/oab
/OAB
owa
/OWA
/
/mapi
/MAPI
/api
/API

image

The filter rules have also been significantly reduced:

  • 960010
    960015
    981204
    981176

image

Web services exceptions

There have been some changes to the exceptions. There is now only one exception for the web services and one exception for Autodiscover and the web services:

image

/ecp/*
/ECP/*
/ews/*
/EWS/*
/Microsoft-Server-ActiveSync*
/oab/*
/OAB/*
/owa/*
/OWA/*
/api/*
/API/*
/MAPI/*
/mapi/*
/autodiscover/*
/autodiscover/*

image

Outlook Web Access Exceptions

Another exception is necessary for OWA:

SNAGHTML37740b

The exception applies to the following URLs:

/owa/ev.owa*
/OWA/ev.owa*

image

Autodiscover virtual web server

The virtual web server for Autodiscover remains unchanged and is only assigned the new firewall profile:

SNAGHTML3ad288

Web services Virtual web server

The virtual web server for the Exchange web services also remains unchanged and is only assigned the new firewall profile:

SNAGHTML3ba52a

Avoid MAPIoverHTTP authentication problems

To avoid authentication problems in connection with MAPIoverhTTP, it should be ensured that the login information is passed through accordingly. The settings can be made in the Internet options on the client. To do this, the option "Automatic login only in the intranet zone" is activated for the "local intranet" zone (if not already done):

image

It may also be necessary to add the corresponding URL to the intranet zone:

image

Here are the authentication methods for the Mapi directory:

image

5 thoughts on “Sophos UTM 9.4 WAF und Exchange 2016 (ohne RPCoverHTTP)”

  1. Hallo Frank,
    soweit alles eingerichtet. Ich komme auch über https://outlook….. auf den owa-Anmeldebildschirm. Wenn ich die emailadresse und das Passwort eingebe, dann kommt die Meldung, daß der Benutzername oder das Passwort verkehrt sind.

    Wo könnte der Fehler liegen?

    Gruß
    Christoph

    Reply
  2. Hi,

    wie sieht es aus, wenn man ein DAG Cluster mit 2 Exchange Servern in der Umgebung hat?
    Kann man dann einfach beide im WAF auf der Sophos eintragen?

    Reply
  3. Hi Franky,

    Betrifft zwar einen Exchange 2013 aber eventuell hast du hier eine Idee.
    Ich habe EWS freigegeben und die UTM wie in deinem älteren Post konfiguriert.
    Leider ist die Anmeldung über Basic Authentication nicht möglich; ich erhalte immer einen HTTP 401.1.
    So ziemlich alles was ich gefunden habe, habe ich ausprobiert aber es ändert nichts. Laut Tracing sieht es so aus als würde ich in die Windows integrierte Anmeldung laufen was natürlich fehlschlägt. Intern funktioniert die Anmeldung ohne Probleme.

    Reply
  4. Hallo, eine Frage du hast beim Exchange 2016 Outlook Anywhere abgeschaltet, d.h man greift von extern über MAPI over HTTP zu?

    Ich hab aktuell Exchange 2016, MAPI ist enabled, Outlook Anywhere ist enabled, aber von aussen zeigt es immer noch RPC/HTTP an. intern zeigt es HTTP an.

    somit einfach Outlook Anywhere abschalten und gut ist?

    mfg

    Reply

Leave a Comment