Open a Support Case My Support Cases

4.E Understanding Virtual Tenants

I.  Overview

One of CoreView’s most mature functional competencies is its ability to allow the customer to partition or compartmentalize Office 365 data based on organizationally defined attributes.  These are known as Virtual Tenants.    

Why is this capability so important to organizations who have (or are moving) to Office 365?  Microsoft has designed Office 365 with a flat data structure.  For anyone familiar with Active Directory, it’s analogous to all of an organization’s account objects housed under a single Organizational Unit.  As a consequence of this design, it becomes especially difficult for organizations to manage and report on Office 365 data by business units.  Moreover, it creates significant challenges for organizations that desire to delegate the management of Office 365 to one or more business units.  Without a solution like CoreView, organizations often need to hire additional staff to cover the new Office 365 administrative activities.  You can find a brief video overview of this feature below.

II.   Partitioning Office 365 Data

The scope of data associated with CoreView Virtual Tenant can be configured to be as broad or as narrow as may be required by your organization.  As you can see from the screenshot below, you can configure a Virtual Tenant to limit data based on any or all of your organization’s domains, a delegation filter or groups.   

III. Delegation Filters

A Delegation Filter consists of one or more organizationally-defined account attributes that are appropriate to define a Virtual Tenant.  For example, you can define a Delegation Filter to use the “Department” attribute that is equal to Finance and that Virtual Tenant will now consist of the set of all accounts whose Department value is equal to Finance.

Once you have created your Virtual Tenants, you then can delegate access to that tenant to any individual in your organization based on your business needs.  Please be aware that Virtual Tenants only work in the context of CoreView and are not a construct that is implemented in Office 365 itself.  This means that anyone to whom you’d like to delegate access will need to be enrolled in CoreView as an Operator and will need to log into CoreView to perform their Office 365 administrative (or analysis) activities.

IV. License Pools as Virtual Tenants

Organizations also have the option to bypass the creation of Virtual Tenants and instead, configure CoreView to rely on your License Pool configuration as your Virtual Tenants.  This option is probably best for customers whose plan for structuring your License Pools is that same as what you would want to use for Virtual tenants.


Published: 03/15/2019


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.