rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Delegate governance by country or subsidiary

AI summary

Virtual Environments divide a shared Microsoft 365 tenant so each country, subsidiary or business unit can govern its own part with custom roles, permissions, policies and dashboards. Central IT keeps overall visibility while local admins manage their unit independently, though automations, reviews and provisioning must run from the root environment.

Let each country, subsidiary or business unit govern its own part of the tenant. A Virtual Environment holds one unit's objects, and custom roles and teams set what each local admin can do.

Each Virtual Environment has its own permissions, appearance, dashboards and reports, custom roles and teams go down to single actions, and central IT keeps the full view.

Who it is for: central IT that shares one tenant across units, and the local admins of each unit.

Virtual Environments come with Tenant segmentation (virtual tenants), which is included in the Enterprise Plan and is not sold as a separate add-on. See Add-ons.

Steps

  1. Add a Virtual Environment for the unit, with filters such as all users based in one country. See also Virtual Environment.
  2. Decide what the local admins may do. Start from the default roles and permissions, or create a custom role and a custom team.
  3. Invite the local admins to the environment and assign them a role and team.
  4. Give the unit its own policies, reports and dashboards when you set up the Virtual Environment.

Policy templates

Any policy template can be used inside a Virtual Environment. Start with the templates of the services the unit uses, for example Teams policies, SharePoint policies and Microsoft 365 policies.

Limits

  • Automations are not available in a Virtual Environment.
  • Reviews and provisioning are not available in a Virtual Environment either. Run them from the root environment.
  • In a Virtual Environment, search covers inventory, reports and policies only.
  • Read permissions cannot be removed from a custom role.
  • Every Virtual Environment adds time to the end of each Microsoft 365 scan.

Frequently asked questions

Which features are not available inside a Virtual Environment?

Automations, reviews and provisioning are not available in a Virtual Environment. Run reviews and provisioning from the root environment. Search in a Virtual Environment covers inventory, reports and policies only.

How do I let a local admin manage only their own country or subsidiary?

Add a Virtual Environment for the unit, using filters such as all users based in one country. Then start from the default roles and permissions or create a custom role and team, and invite the local admin with a role and team assigned.

Can I remove read permissions from a custom role in a Virtual Environment?

No. Read permissions cannot be removed from a custom role. Custom roles and teams can still be set down to single actions to control what each local admin can do.