Dynamics 365: Units, Teams & Security

Key insights

• Organization hierarchy: Describes how a company structures legal entities, business units and teams so processes, reporting and security work correctly across Dynamics 365.
  It shapes data flow and access across apps like Finance & Operations and Customer Engagement.
• Core building blocks include Legal entities, Business units, Teams and Operating units.
  Each serves different roles: legal entities for statutory work, business units for departmental boundaries, teams for shared responsibility, and operating units for broader operational grouping.
• Product differences matter: Customer Engagement treats Business units as a main security boundary, while Finance & Operations uses hierarchies of legal and operating units and explicitly excludes teams from those hierarchies.
  Assume terms do not mean the same thing across Dynamics 365 apps.
• The hierarchy directly affects the Security model: security roles and record access usually follow business unit boundaries unless you grant cross-unit access.
  Design hierarchies with security and reporting needs in mind to avoid later rework.
• Microsoft now positions hierarchies as reusable, purpose-driven structures for reporting and operations rather than just an org chart.
  Plan hierarchies as part of your Dynamics strategy, assign clear purposes, and reuse them for reporting, tax, commerce or internal views.
• Basic setup steps (Finance & Operations): go to Organization administration > Organizations > Organization hierarchies, create a new hierarchy, assign a purpose and add organizations, then save and publish changes.
  Follow purpose-driven design and test security and reporting after publishing.

Keywords

Dynamics 365 organization hierarchy, Dynamics 365 business units, Dynamics 365 teams and security, Dynamics 365 security model, Dynamics 365 role-based security, parent-child business units Dynamics 365, Dynamics 365 sharing and access, Dynamics 365 organizational structure