Diagnostic Tool: requirements and preparation

  • Last update on March 7th, 2024

The article discusses prerequisites and network configurations for the CoreView Diagnostic Tool, emphasizing Docker RTE setup, server and proxy considerations, and specific network/firewall settings for Azure and enterprise connectivity.

Docker RTE installation

The CoreView Diagnostic Tool utilizes the Docker Runtime Environment (RTE) to operate. Please refer to the Hybrid Connector requirements article for installation recommendations regarding the Docker RTE.


We recommend running the CoreView Diagnostic Tool from the same server where you plan to deploy the CoreView Hybrid Connect. This allows you to perform connection tests from the same host that will run the CoreView Hybrid Connector in your production environment.


Please note that if you're running the CoreView Hybrid Connector behind a proxy, you'll first need to verify if your proxy settings are assigned to your Windows PowerShell session. If you're unsure, please run the following command for the HTTP proxy:

$env:http_proxy = "http://xxx.xxx.xxx.xxx:port"

Or the following for the HTTPS proxy:

$env:https_proxy = "https://xxx.xxx.xxx.xxx:port"

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, CoreView, and the Microsoft Azure infrastructure.

The CoreView Diagnostic Tool will also need to communicate to your Active Directory and, optionally, a selected Exchange Server:

Network Components Target Hostnames  Port Requirement
Diagnostic Tool Azure Blob Storage cvhybridtool.azurecr.io 80, 443 (TCP)
Diagnostic Tool Azure Service Bus *.windows.net 443, 5671, 9354 (TCP, AMQP)
Diagnostic Tool Azure Blob Storage *.windows.net
443 (TCP)
Diagnostic Tool AD Domain Controller TBD by Customer 443 (TCP) , 5985 (TCP), 5986 (TCP)
Diagnostic Tool Exchange PowerShell Host TBD by Customer 80, 443 (TCP)
Diagnostic Tool Sectigo Certification Authority *.sectigo.com 80, 443 (TCP)
Diagnostic Tool Microsoft O365 workloads *.microsoft.com 80, 443 (TCP)
Diagnostic Tool Azure AD *.windows.net
80 (TCP), 443 (TCP), 5985 (TCP), 5986 (TCP)
Diagnostic Tool MSOL *.microsoftonline.com
80 (TCP), 443 (TCP), 5985 (TCP), 5986 (TCP)
Diagnostic Tool Exchange Online *.Office365.com
80 (TCP), 443 (TCP), 5985 (TCP), 5986 (TCP)
Diagnostic Tool SharePoint Online         *.sharepoint.com 80 (TCP), 443 (TCP), 5985 (TCP), 5986 (TCP)
Diagnostic Tool Teams *.lync.com
80 (TCP), 443 (TCP), 5985 (TCP), 5986 (TCP)
Diagnostic Tool GoDaddy Certification Authority *.godaddy.com 80 (TCP), 443 (TCP)
  CoreView All Services *.4ward365.com  

80 (TCP), 443 (TCP) , 5985 (TCP), 5986 (TCP)


The target audience for this document includes senior technology staff in your organization who support enterprise services. The activities described in this section typically require the participation of one or more of these individuals.

The relevant personnel must review this document thoroughly and contact CoreView with any queries before arranging a deployment.