Categories

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 your organization requires. As illustrated in 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 indicate that you are filtering out (or in) data that you want to associate with the Virtual Tenant you are creating or editing. The following is an overview of the page displayed when clicking on the Users tab. This tab allows you to define 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

Filters can be utilized individually or in combination. CoreView's filtering capability allows you to control the extent and depth of data access for an Operator. The scope of a Virtual Tenant can be tailored to be as broad or as narrow as your organization's business requirements dictate.


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. First, specify the attribute you want to use, followed by the filtering criteria, and then the value(s), as illustrated below. Multiple filters can be applied using AND or OR, as appropriate.



3. Domain Filters

This filter applies exclusively to an account object's UPN Domain. To search for a domain, type into the search field located below the column titled "Domain".



4. Distribution, Security, and/or Office 365 Groups

In this example, we'll use Distribution Groups, as the same rules apply to Security or Office 365 Groups. To search for a Group, type into the search field located below the column titled "Display Name" or "Name".




Filtering Office 365 Groups

You can also determine which Groups you want to grant Operators access to within the context of a Virtual Tenant. This can be configured to be as broad or as narrow as your organization may require.



1. Groups

Below is an overview of the Groups page, along with a description of each filtering option.


2. Domain Filters

Similar to the Users tab, this filter applies exclusively to an account object's UPN Domain. To search for a domain, type into the search field located below the column titled "Domain". You can add a domain to the filter by clicking the "+" icon. To remove a domain from the filter, click the "-" icon.



3. Distribution, Security, and/or Office 365 Groups

Just as with filtering by User, the same rules apply to Distribution, Security, and Office 365 Groups. To search for a Group, type into the search field located below the column titled "Display Name" or "Name".




What's Next

After creating your Virtual Tenants, you can delegate access to any individual in your organization based on your business needs. Please note that Virtual Tenants operate exclusively within the context of CoreView and are not implemented in Office 365 itself. This means that anyone you wish to delegate access to must be enrolled in CoreView as an Operator and will need to log into CoreView to perform their Office 365 administrative or analytical activities.


We highly recommend that Tenant Admins assign a new or modified Virtual Tenant to a test Operator account and then log in to CoreView using that test Operator account to ensure the configuration of the Virtual Tenant meets their expectations.



Setting up virtual tenants for numbers 


If you wish to delegate responsibility for managing numbers to delegated administrators, you can create or edit your virtual tenants to include number information. 


Please keep in mind that all phone number types can be delegated to virtual tenants, ensuring a comprehensive approach to number management.



Your V-tenants for users match your number distribution


If your virtual tenants for users match your number distribution, you can simply edit your existing virtual tenants. For example, you may break down your virtual tenants by country and want your numbers distributed by country, OR your virtual tenants are organized by department and your numbers will also be distributed to departments. However, if they don’t match, you can set up virtual tenants specifically for numbers. For example, you might want your phone numbers distributed by country, although your virtual tenants are broken down by Business Unit.   


You can populate your virtual tenants based on which users are already assigned direct routing numbers. When you upload the list of direct routing numbers, you can identify the user assigned to each number. If there is a conflict between the data provided by the SBC and the data contained within Teams you can see that on the Teams Numbers report. Use the “Mismatch between Teams and SBC assignee” field to find and resolve data conflicts. 


You can have a quick snapshot of your virtual tenant users who have a phone number assigned to them in a dedicated section. Please keep in mind that a user can be a part of multiple virtual tenants, in that the user and the number assigned to them will be visible in more than one virtual tenant. On the other hand, you can only distribute spare numbers to one virtual tenant, meaning that, depending on the scenario, the number assigned to a user can be allocated to your virtual tenant or not. 


You can then distribute the remaining inventory based on criteria with the ability to “cap” the number given to each virtual tenant. For example, you can allocate a virtual tenant 50 numbers from the remaining UK phone number inventory.  



Your V-tenants for numbers don't match your V-tenants for users


If your virtual tenants for numbers are not the same as your virtual tenants for users, an operator could have responsibility for managing a number but not the user who has the number. In this case, the operator would be able to do the following:     

  • Assign a number only to users matching delegation filters in the virtual tenant to which the operator delegated to managing the number is assigned. 
  • Unassign a number only to users matching delegation filters in the virtual tenant to which the operator delegated to managing number is assigned. 
  • View the User ID and UPN of the user assigned a number only to users matching the delegation filters set for users in the virtual tenant to which the operator delegated to managing number is assigned. This means that if a number that has been allocated to a virtual tenant is assigned, via means different than CoreView, to a user that is outside of the scope of that virtual tenant, the possibility to manage that number is lost until the number is unassigned from the “wrong” user. 



Instructions


  1. Go to Settings > Virtual Tenants 
  2. Create a new virtual tenant or access an already existing one 
  3. Go to the Phone number tab 
  4. Optional: Have a quick check of your configuration in the Overview tab, where you can see your number allocation rules and the amount of allocated and consumed numbers in your virtual tenant.
  5. Optional: Have a look at the Consumed tab to see which users assigned to your virtual tenant have a phone number assigned to them.
  6. Go to the Spare Numbers tab. Here, you can decide the criteria by which you want to allocate spare numbers (numbers that are not assigned to anyone or not part of any other virtual tenant) to your virtual tenant. You can decide to segregate based on a variety of attributes and, based on the amount of numbers that fit your criteria, decide to allocate all of the results or only a part of them. The filtering is dependent on the number plan type, so you can have different criteria for Teams numbers and direct routing numbers.
  7. Save and complete the configuration. 



License Pools as Virtual Tenants

Organizations can also choose to bypass the creation of Virtual Tenants and configure CoreView to rely on their License Pool configuration as their Virtual Tenants. This option might be more suitable for smaller customers whose License Pool structure aligns with their desired Virtual Tenant configuration. Although this option is available, it is not considered a recommended practice.