This chapter focusses on the integration of Microsoft Exchange 2016 / 2019 into the Airlock Secure Access Hub.
About Microsoft Exchange
Microsoft Exchange is a mail server that allows users to work from anywhere at any time.
- It offers features such as:
- Outlook on the Web (formerly Outlook Web Access): Access to mails, calendar and contacts through the webmail client.
- Outlook Anywhere: Outlook integration over HTTP.
- ActiveSync: Synchronization of mails, calendar entries and contacts on mobile devices.
MS Exchange allows employees to be more productive and collaborate. Typically, however, the MS Exchange services are reachable from the Internet. This increases the risk of being attacked. To enhance security, Airlock Gateway should be installed between MS Exchange and its clients. This gives users full access to MS Exchange's features while still maintaining a secure environment.
Requirements and limitations
The integration of Microsoft Exchange into Airlock has been tested with the Airlock modules and/or 3rd party software versions listed in the following table. The instructions in this manual are based on these modules/versions.
Component | Required version | Comments |
|---|---|---|
Airlock Gateway | Version 7.3 or newer | None |
Airlock IAM | Version 7.0 or newer | Optional: Only if authentication enforcement is used |
Microsoft Exchange | Version 2016 / 2019 | None |
Microsoft Outlook | Version 2016 / 2019 | Optional: Only if RPC over HTTP or MAPI over HTTP is used |
RPC Proxy | On Windows Server 2016 / 2019 | Optional: Only if RPC over HTTP should be used |
Medium – Although some functions might work with other Airlock Gateway, Airlock IAM, Airlock Microgateway, Airlock add-on modules and/or 3rd party software versions, it is highly recommended using the releases this documentation is based on.
Always install the latest bugfix release before proceeding.
Instructions
The following chapters explain how to integrate MS Exchange into Airlock Gateway, for Outlook on the Web, Outlook Anywhere, and ActiveSync, respectively. This also includes instructions on the configuration of authentication enforcement.