Understanding Virtual Tenants

Modified on Thu, 08 Dec 2022 at 08:44 AM

In this article, you will learn how setting up virtual tenants in CoreView will help you: 

  • Organize your IT teams the way you want 
  • Scale your Microsoft 365 operations
  • Empower your operators to do more in Microsoft 365 


Filtering Office 365 Users

The scope of data associated with a 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 screenshots below, you can configure a Virtual Tenant to limit data based on any or all of your organization’s UPN Domains, one or more specific Delegation Filter, or any Groups.  


The term Filter is used to denote that you are filtering out (or in) data that you want to associate with the Virtual Tenant you are creating (or editing).  Below is an overview of the page displayed when clicking on the Users tab, identified as "A" below.  This tab allows you to establish the scope (boundaries) of data associated with this Virtual Tenant.  The Filters applied under the Users tab apply only to user account objects. 

 



1. Users Tab


Any of the filters can be used alone or together.  The value of CoreView's filtering capability is that it lets you control the degree and depth to which you can limit the scope of data to which an Operator has access using CoreView.   A Virtual Tenant can be as broad or as limited as may be needed by your Organization's business requirements.


2. Delegation Filters


The Delegation Filter allows you to specify how you want to limit the scope of data associated with any user (account) objects.  You first define the attribute you want to use, the filtering criteria, and then the value(s) as depicted below.  Multiple filters can be used with an AND or an OR, as appropriate.



 

3. Domain Filters


This Filter applies only to an account object's UPN Domain.  You can search for a Domain by typing into the search field below the Column titled Domain.




4. Distribution, Security and/or Office 365 Groups


We'll use Distribution Groups in the example, because the same rules apply to Security or Office 365 Groups.  You can search for a Group by typing into the search field below the Column titled Display Name or Name. 




Filtering Office 365 Groups

You can also specify what Groups you want to give Operators access to in the context of a Virtual Tenant.   This can be configured to be as broad or as narrow as may be required by your organization.  




1. Groups


Below is a view of the Groups page, along with a description of each Filtering option.

,


2. Domain Filters


Just like under the Users tab, this Filter applies only to an account object's UPN Domain.  You can search for a Domain by typing into the search field below the Column titled Domain, and you can add a Domain to the Filter by clicking on the "+" icon.  Clicking on the "-" icon under removes a domain from the Filter.



3. Distribution, Security and/or Office 365 Groups 

As with filtering by User, the same rules apply to Distribution, Security and Office 365 Groups.   You can search for a Group by typing into the search field below the Column titled Display Name or Name. 



What's Next

Once you have created your Virtual Tenants, you 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.


We strongly recommend that TenantAdmins assign a new or modified Virtual Tenant to a test Operator account and then log in to CoreView using that test Operator account to validate that the configuration of the Virtual Tenant meets your expectations.


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 smaller customers whose plan for structuring your License Pools is the same as what you would want to use for Virtual tenants.  While we do make this option available, it's not a recommended practice.




---

Published: 03/15/2019

Updated:12/8/2022


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article