Requirements

Infrastructure requirements

The following requirements apply to the key infrastructure components that support CoreView's on-premises functionality. 

¹ The Hybrid Connector should be installed on a standalone virtual or physical server and not coexist with other business services.

² Under Exchange 2013 and higher, each Exchange Server is also a CAS server. The CoreView Hybrid Connector must be configured to point to a specific Exchange server, and not a Virtual IP (VIP).

Network / Firewall requirements

The following requirements apply to network traffic that supports CoreView’s on-premises functionality. Please note that these network requirements pertain only to traffic between the on-premises connector and CoreView or the Microsoft Azure Service Bus infrastructure. 

The CoreView On-premises Connector will also need to communicate with the customer’s Active Directory and, optionally, a select Exchange Server. 

For additional information on the requirements for accessing the Azure Service Bus, please refer to the Microsoft documentation.

Important note about Multi-Factor authentication

If you implemented Multi-Factor Authentication (MFA) for accessing your Microsoft 365 cloud services, please mind creating a conditional access policy that excludes your on-premises Hybrid Connector IP address for asking any second-factor authentication for the CoreView service account CoreView named:

4ward365.admin@yourdomain.onmicrosoft.com

Without that exception policy, your CoreView tenant won’t be able to open any management session.

Please also mind your Hybrid Connector IP address could be behind a NAT applied by your network gateway for connecting to public networks such as the Internet. We recommend checking with your network specialist to identify your public IP address used by your on-premises for connecting to the public networks.

For more information about conditional access exception policy, please refer to the Microsoft documentation.

Security requirements

The following security requirements apply to CoreView’s on-premises functionality:

(*) Important note about Exchange Virtual Directory configuration:

There are two methods for configuring authentication when setting up the PowerShell virtual directory for remote access. If Basic authentication is enabled, SSL must also be enabled and configured with a valid public certificate.  

(**) If your company has security policies that don't allow setting service accounts with domain admin permission, please refer to the chapter “Hardening CoreView Hybrid Connector service accounts’ permissions” below.

If SSL is not enabled, then Windows Authentication should be set. In this scenario, you must configure gMSA for the Hybrid Connector hosting server and configure your CoreView Hybrid Connector to support the gMSA settings.

For more information about the settings of Exchange Powershell virtual directory refer to the Microsoft documentation.

Software requirements

The following software requirements apply to CoreView’s on-premises functionality:

Docker engine installation

Please refer to the Microsoft documentation for the instructions to deploy docker service in your hosting server.