Virtual Tenants: introduction

  • Last update on March 6th, 2024

What are Virtual Tenants?

CoreView's Virtual Tenants allow you to divide, limit, or organize your Microsoft 365 data within the boundaries you set for your organization.

Virtual Tenants do not alter your actual Microsoft 365 environment. They are virtualized within CoreView, meaning the segmentation happens in CoreView, not in your Microsoft 365 tenant.

 

How do Virtual Tenants work?

Imagine Virtual Tenants as separate “boxes” within your Microsoft 365 tenant. These boxes act as virtual compartments that you can tailor to your organization's needs.

Each V-Tenant operates independently, representing a specific segment of your business structure, such as teams, locations, or departments. V-Tenants help you organize and control the access and settings of users, groups, and other resources, aligning with your organizational structure.

Segmentation

When setting up your V-Tenants, think about the segmentation that best mirrors your company's layout. Common segmentation options include:

  • Geography: create a V-Tenant for each country, region, or location. A global company, for instance, may establish a V-Tenant for each branch to define the responsibilities of local IT support teams.
  • Structure: form V-Tenants for different divisions, such as subsidiaries or departments. A conglomerate with various entities might use V-Tenants to separate its Microsoft 365 data per brand or company.
  • Groups and domains: represent various teams, units, or domains within your organization with individual V-Tenants. During mergers, companies can use V-Tenants to manage the transition by assigning one to each company involved.
  • Organizational Units: use your company's Active Directory Organizational Units as a starting point for creating V-Tenants.

Filtering

With your V-Tenants structured, you can apply filters to control what goes into each “box”. Filters based on specific attributes help tailor the visibility of objects within a V-Tenant to meet particular needs.

You can filter the following objects:

  • Groups
  • Users
  • Phone numbers
  • Devices
  • Organizational Units

Filtering is possible for all attributes associated with Entra ID.

 

Examples

  • A multinational firm could establish a V-Tenant for each office to limit the scope of action of the local IT help desks, filtering Users and Groups by the “Country” attribute and Phone Numbers by certain prefixes.
  • Merging companies might set up a V-Tenant for each entity to ease the transition, filtering Groups and Users by their respective domains.