Multi-Tenant & Virtual Environments

Tenant-level scaling

Multi-tenant support handles the case where an organization has more than one Microsoft 365 tenant. Most enterprises end up here eventually, M&A produces tenant proliferation, regional regulations push toward separation, dev/prod isolation drives splits. MSPs are multi-tenant by definition.

A single Rencore instance registers multiple tenants and applies governance uniformly across them. Each tenant retains data isolation; cross-tenant reporting is opt-in and respects per-tenant access controls. Adding a tenant is a configuration change, not a new platform deployment.

Sub-tenant scaling

Virtual environments handle the case where one tenant needs multiple governance scopes. A large enterprise with a single M365 tenant but ten business units that each manage their own SharePoint estate can give each business unit its own virtual environment, separate dashboards, separate delegation, separate scope, without provisioning ten tenants.

Up to 200 virtual environments per tenant. Each can be parameterized through a template, letting MSPs and IT operators bulk-create virtual environments for new customers or new business units with consistent configuration.

When to use which

Multi-tenant for tenant-boundary scope (M&A, regional, dev/prod, MSP). Virtual environments for sub-tenant scope (business units, departments, customer-of-tenant patterns). Both compose: an MSP with multiple tenants, each containing multiple virtual environments for customer sub-accounts, is fully supported.