Introduction to on-premises import process

CoreView will only import on-premises objects that are not part of the AADConnect synchronization process. These objects are already being imported to your CoreView tenant from the Microsoft 365 cloud tenant.

Therefore, the on-premises import process focuses on objects not covered by AADConnect. To select these objects, go to "Settings" > "My Organization" > "On-Premises" > "Import" and choose the desired Organizational Units.

When you start a CoreView management session from the portal, a Docker container is activated. This container manages the opening of runspaces for:

1. Azure Active Directory
   2. Exchange Online
   3. MSOL Service
   4. Microsoft Teams
   5. Microsoft Graph
   6. Exchange On-Premises
   7. Active Directory On Premises

For those with an On-Premises MultiForest setup, the CoreView Hybrid Connector will open runspaces for Exchange On-Premises and Active Directory On-Premises for each forest you have configured.

Operators execute management actions through the runspaces provided by CoreView. These runspaces are set up using the service account linked to your CoreView Tenant.

Runspaces 1 to 5

For runspaces 1 to 5, CoreView utilizes the cloud service account:

4ward365.admin@yourdomain.onmicrosoft.com 

This account was established during the configuration of your CoreView Management Session.

Remaining channels

The additional workspaces are accessed using the service account you have specified in the On-Premises section of your CoreView portal.

Please note that the previously mentioned channels are not used for the on-premises import. Instead, CoreView activates an additional Docker container every six hours to connect to your on-premises environments, such as Active Directory On-Premises and Exchange On-Premises.

The CoreView Hybrid Connector only imports objects that are not synchronized by your AADConnect. It also updates the objects that have already been imported into the CoreView tenant through the standard daily import process.

To carry out an on-premises import, the CoreView Hybrid Connector initiates a Docker container, conducts the import through the outlined steps, and then shuts down. This process is independent of the other Docker container that is already running for CoreView native management actions and custom actions.

Here's a detailed explanation of the on-premises Active Directory structure and the objects that CoreView imports:

In the structure of a domain controller, as depicted in the screenshot below, not every object you see is an Organizational Unit (OU). Some are known as containers. While containers may have a similar name to Docker containers, they function differently.

As you may know, not all these objects are OUs. Some of these are called containers. The symbol is a little bit different compared to the OU icon – the name is the same as the docker container, but those work with different behaviors.

In the image, containers are indicated with a red underline.

To keep it simple, just like OUs, containers can hold various objects such as users, groups, and computers. However, it's important to note that CoreView does not import any objects from these containers.

This means that any object placed within a container will not appear in your CoreView reports, nor can it be included in any management actions within CoreView.

CoreView updates and displays information about an object immediately after a management action is taken.

Please be aware that changes made through the on-premises Active Directory Users and Computers snap-in or CoreView custom actions may not be reflected instantly. The updated information for an object you modify will be visible after the next cycle of the Hybrid Connector import process completes. Expect a short delay before these changes appear in CoreView.