trio.so
Explained

Multi-Tenant Active Directory: A Practical Guide

What multi-tenant Active Directory means, shared forests, separate forests with trusts, Entra multitenant organizations, and how to design and secure each.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

"Multi-tenant Active Directory" means one of two things. On premises, it is a single Active Directory (AD) environment that holds several organizations, each kept apart in its own organizational unit or domain, or a set of separate AD forests, one per organization, connected by trusts. In the cloud, it means several Microsoft Entra ID tenants working together, for example through a Microsoft Entra multitenant organization, cross-tenant synchronization or B2B collaboration. The key design fact is that in AD the forest, not the domain or the OU, is the security boundary: organizations that must be fully isolated from each other need their own forest or their own Entra tenant.

If you host directories for several companies, or you are joining two organizations' tenants, the comparison table below shows the options side by side; the sections after it cover design, security and the mistakes to avoid.

What Is Multi-Tenant Active Directory?

A tenant is an organization, or a part of one, whose users, computers and policies must be managed separately from everyone else's. Managed service providers (MSPs) and hosting companies serve many client tenants; groups of companies, and businesses after a merger, often run several. Multi-tenant Active Directory is any design that lets those tenants share infrastructure or work together while keeping their administration and data apart.

Two very different designs share the name:

  • Shared on-premises AD: one forest, with each tenant in its own organizational unit (OU) or domain, and administration delegated per tenant. It saves servers but gives limited isolation.
  • Connected separate directories: one AD forest or one Entra tenant per organization, linked by trusts or by Microsoft Entra's cross-tenant features. Each organization keeps its own boundary.

Multi-Tenant Options Compared

OptionHow tenants are separatedIsolationBest for
One forest, one OU per tenantOUs with delegated admin rights and separate Group PolicyLow: forest-wide admins and the shared schema reach every tenantDivisions of one company that trust each other
One forest, one domain per tenantChild or tree domains in a shared forestLow to medium: the forest is still the security boundarySeparate admin teams within one organization
One forest per tenant, with trustsSeparate forests linked by forest or external trustsHigh: each forest is its own boundary; trusts can be one-way and filteredHosting several companies, or keeping a merged company separate
Microsoft Entra multitenant organizationSeparate Entra tenants, joined with cross-tenant access and synchronizationHigh: each tenant keeps its own admins and policiesGroups of companies on Microsoft 365 that need to collaborate

Key Components of Multi-Tenant Active Directory

Forests and Domains

A forest is the outer container of Active Directory: it holds one or more domains that share a schema, a configuration and a global catalog. Microsoft treats the forest as the security boundary, because administrators of the forest root, such as Enterprise Admins, can reach every domain in it. A domain is a boundary for administration and replication, not for security.

Organizational Units

OUs group users, computers and groups inside a domain. In a shared design, each tenant gets its own OU, and tenant administrators are given rights over their OU only. Group Policy can be linked per OU, so each tenant gets its own settings.

Trusts

Trusts let users in one domain or forest sign in to resources in another. A forest trust connects two forests; an external trust connects two specific domains. Trusts can be one-way, so one organization's users can reach the other's resources but not the reverse, and selective authentication limits which users may cross.

Global Catalog

The global catalog holds a searchable, partial copy of every object in the forest. In a shared forest, that means every tenant's objects are visible to directory searches unless you restrict read permissions, which is one of the reasons shared forests isolate tenants poorly.

Group Policy Objects

Group Policy Objects (GPOs) apply settings to users and computers. Linking them per tenant OU keeps settings apart, but GPOs linked higher in the tree apply to every tenant below.

Microsoft Entra ID: Multitenant Organizations and Cross-Tenant Features

In the cloud, each organization normally has its own Microsoft Entra tenant, and Microsoft provides ways to connect them rather than share one:

  • B2B collaboration: users from another tenant are invited as guests and can use your apps and resources with their own sign-in.
  • Cross-tenant access settings: control which other tenants your users may collaborate with, and whether you trust their MFA and device compliance claims.
  • Cross-tenant synchronization: automatically creates and updates users from one tenant in another, so people in a group of companies can find and work with each other.
  • Multitenant organization: a Microsoft Entra feature that groups several of your tenants, so collaboration in Microsoft 365 apps such as Teams works more like a single organization.

Microsoft Entra Connect, or Cloud Sync, links an on-premises AD to a tenant. Check Microsoft Learn for the supported combinations of forests and tenants before you design, because they are specific and they change.

MSPs that manage clients' Microsoft 365 tenants usually do not join those tenants together at all. They work through Microsoft's partner tools with granular delegated admin privileges (GDAP), which give the MSP limited, time-bound admin roles in each client tenant.

Benefits of Multi-Tenant Active Directory

  • Lower cost for shared designs: fewer domain controllers and servers to run.
  • Central administration: one team can manage many tenants with the same tools and standards.
  • Collaboration across organizations: trusts and Entra cross-tenant features let people work together without duplicate accounts.
  • Consistency: a single design and a single set of standards across tenants make audits and changes easier.

Challenges in Implementing Multi-Tenant Active Directory

  • Isolation: in a shared forest, a compromise of a forest-wide admin account reaches every tenant. That risk is the main reason MSPs give each client its own forest or tenant.
  • Complexity: delegation, trusts and filtered permissions are easy to get wrong and hard to audit.
  • Schema and forest-wide changes: an application that extends the schema for one tenant changes it for all of them.
  • Compliance: tenants may have different data residency and retention requirements that a shared design cannot meet.
  • Exit: separating a tenant from a shared forest later, for example when a client leaves, is a migration project.

Best Practices for Managing Multi-Tenant Active Directory

  • Choose isolation first: if tenants are separate companies, give each its own forest or Entra tenant, and connect them only where they need to collaborate.
  • Use a tiered admin model: keep forest and domain admin accounts off ordinary workstations, and give tenant admins rights over their own OU or tenant only. See Active Directory security.
  • Apply least privilege: delegate the specific tasks each admin needs rather than broad groups. See the least privilege access model and excessive permissions.
  • Separate admin accounts: admins use a standard account for daily work and a separate account per tenant for admin tasks.
  • Make trusts as narrow as possible: one-way where you can, with selective authentication.
  • Audit and monitor: log changes to admin groups, delegation and trusts in every tenant, and review them regularly.
  • Automate provisioning: create and remove users from an authoritative source, such as HR, so accounts do not linger. See user provisioning.

Common Mistakes to Avoid

  • Treating OUs or domains as a security boundary between separate companies.
  • Two-way trusts with no filtering "to make things work".
  • One shared admin account used across tenants.
  • Group Policy linked at the domain root that silently applies to every tenant.
  • No plan for removing a tenant when a client or division leaves.

If you are weighing whether you need AD at all for new tenants, LDAP alternatives covers cloud directories and single sign-on.

Managing this across many devices

Whichever directory design you use, devices should belong to the right people without retyping users into another tool. trio.so syncs users from Microsoft Entra ID or Google Workspace and supports SCIM 2.0 user provisioning with Microsoft Entra ID, so users and their devices line up with your directory. For MSPs, trio.so manages several client companies from one console, with each client's devices, users and policies kept separate.

The trio.so Authentication and Security settings, Sign-in tab, with single sign on through Microsoft Entra ID turned on.
Single sign on with Microsoft Entra ID in the trio.so settings.

Conclusion

Multi-tenant Active Directory covers two designs: several tenants inside one AD forest, or separate forests and Entra tenants connected where they need to work together. The forest is the security boundary, so separate companies belong in separate forests or tenants. Delegate narrowly, keep admin accounts tiered and separate, make trusts one-way and filtered, and plan from the start how a tenant will leave.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Bring your users in from your directory

trio.so syncs users from Microsoft Entra ID or Google Workspace and supports SCIM provisioning with Entra ID.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

An Active Directory design that serves several organizations, either inside one forest with each tenant in its own OU or domain, or as separate forests or Entra tenants connected by trusts or cross-tenant features.

It can, using separate OUs or domains with delegated administration, but the companies are not fully isolated, because the forest is the security boundary. Separate companies are safer in separate forests or tenants.

A Microsoft Entra feature that groups several tenants owned by the same organization, using cross-tenant access and synchronization so people can find and collaborate with each other across tenants.

If the tenants are separate companies or need strict isolation, yes. A shared forest only suits parts of one organization that trust each other.

Usually by keeping each client in its own forest or Microsoft 365 tenant and working through partner tools with granular delegated admin rights, rather than putting clients into one shared directory.

Related

From the blog

The related industry news, interviews, technologies, and resources.