M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Dataverse business units

Concept

Security boundaries in a Dataverse environment arranged as a tree under a root unit; together with security roles they define which rows a user can reach.

✦ CONCEPTDataverse business unitsM365.FM
Title graphic: Dataverse business units (Concept)

Often discussed together

Episodes about Dataverse business units often also cover Dataverse column-level security, Dataverse security roles, Dataverse, Power Platform solution and Row-level security (RLS).

Description

Dataverse business units are security boundaries within a Dataverse environment. They are arranged as a tree beneath a single root unit, and together with security roles they determine what a user can access. Administrators use them to manage users and data by dividing a database into smaller units, each with its own set of users and records.

Every Dataverse database has exactly one root business unit. Child business units are created below it to split users and data into further boundaries, and each user belongs to one business unit. The structure may mirror the organization chart, but it does not have to; it can be designed around whatever separation of access is needed. Business units apply only to environments that have a Dataverse database and are managed separately in each environment.

Business units work together with security roles rather than replacing them. A security role defines which privileges a user holds, and the business unit structure defines the scope at which those privileges reach rows. Access can be granted at the business unit level, and it can be controlled so that data from child business units is either included or excluded. Permissions are cumulative: the broadest permission that applies to a user is the one that takes effect, and one security role cannot restrict another.

Ownership is part of the model. Each record carries an owning business unit, which by default is the business unit of the user who created it. That value can be changed only when the feature for record ownership across business units is enabled. Dataverse also creates a default team for every business unit, and this team always contains all users of that unit. Teams belong to a business unit, and a business unit can be linked to a Microsoft Entra security group through a group team, which connects directory groups to the Dataverse security structure.

Typical decisions around business units involve how deep the tree should be, whether it should follow the organizational hierarchy or a different logic, and at which scope privileges should be granted so that users see only the rows intended for them. Because permissions accumulate, the role design and the business unit layout need to be planned together, since a broad grant cannot be narrowed by adding another role.

The M365.FM episode "Building Multi-Tenant SaaS with Power Pages and Dataverse" discusses business units in the context of tenant isolation. The episode says that Power Pages uses Dataverse business units to keep tenant data separate, that business units create a security hierarchy, and that privileges can be granted at the business unit level. It also notes that each user belongs to one business unit and that access can be set to include or exclude data from child business units. According to the episode, this structure supports a strong tenant isolation model and helps enforce tenant-aware security, with partition-aware routing described as an additional layer.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Episodes about Dataverse business units

Episodes in which Dataverse business units is discussed:

The Dataverse Security Model Explained for Architects

2026-10-31

Most Dataverse security problems start when access is granted one ticket at a time instead of by structure. This episode walks architects through business units, security roles, teams, ownership, column and hierarchy security, and sharing, and shows how to…

Dataverse - Simply Explained

2026-07-14 · YouTube: Dataverse - Simply Explained

Dataverse is Microsoft's intelligent cloud data platform that powers Power Apps, Power Automate, Dynamics 365, and the wider Power Platform. While many people think of it as just another database, Dataverse is much more than that. It provides secure…

Timeline of episodes about Dataverse business units

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What are Dataverse business units? (AI)

They are security boundaries in a Dataverse environment, arranged as a tree under a root unit. Together with security roles they determine which rows a user can access.

How many business units does a Dataverse database have at the top level? (AI)

Every Dataverse database has exactly one root business unit. Child business units are created beneath it to divide users and data into smaller boundaries.

Can a security role limit another role's access in a business unit setup? (AI)

No. Permissions are cumulative, so the broadest permission that applies is the one in effect, and one role cannot restrict another.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: