Study guide

3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams

Microsoft Power Platform Functional Consultant PL-200

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Dataverse Tables, Relationships & Core Columns

1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx

2 Chapter 2: Dataverse Data Management & Governance

2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates

3 Chapter 3: Dataverse Security Model & Access Control

3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models

4 Chapter 4: Model-Driven App Fundamentals & Information Architecture

4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters

5 Chapter 5: Advanced Model-Driven App Components & Custom Pages

5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles

6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations

6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps

7 Chapter 7: Power Pages Site Design, Navigation & Content

7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets

8 Chapter 8: Power Pages Data Integration, Forms & Web Roles

8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration

9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers

9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References

10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls

10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls

11 Chapter 11: Business Process Flows & Guided Processes

11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle

12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility

12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics

13 Chapter 13: Power Platform Environment Architecture & Security

13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications

14 Chapter 14: Application Lifecycle Management (ALM) & Solutions

14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices

15 Chapter 15: Enterprise Interoperability & Service Integration

15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates

16 Chapter 16: Copilot, AI Capabilities & Exam Strategy

16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis

3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams

Key Takeaways Explain This Topic AI

Dataverse supports four primary team modalities: Traditional Owner Teams, Manual Access Teams, Template-Driven Access Teams, and Microsoft Entra (Azure AD) Group Teams.

Owner Teams can own records and have security roles assigned directly to them, with all members inheriting the team's security roles and ownership scope.

Access Teams cannot own records and cannot have security roles assigned; they provide lightweight, dynamic record sharing for ad-hoc cross-functional collaboration via Access Team Templates.

Microsoft Entra Group Teams automatically synchronize membership from Microsoft Entra ID Security Groups or Microsoft 365 Groups, eliminating manual user provisioning and offboarding overhead in Dataverse.

Entra ID Group Teams support two inheritance models: 'Direct User (Basic) access and Group privileges' vs 'Group privileges only', governing whether members can independently execute actions requiring User/Basic depth on personal records.

Last updated: August 2026

3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams

In modern enterprise deployments, assigning security roles to individual users creates significant administrative friction, compliance risks, and governance overhead. Microsoft Dataverse provides a powerful Teams Architecture that streamlines access management, supports cross-functional project collaboration, and integrates natively with corporate directory services.

Understanding the architectural distinctions between Owner Teams , Access Teams , and Microsoft Entra (formerly Azure Active Directory) Group Teams is a cornerstone of the PL-200 certification.

1. Architectural Taxonomy of Dataverse Teams

Dataverse provides four distinct team implementations, each tailored to specific operational requirements, data ownership patterns, and performance considerations. +-----------------------------------------------------------------------------------+

  • | DATAVERSE TEAMS TAXONOMY |
  • | |
  • | +---------------------------------------------------------------------------+ |
  • | | 1. OWNER TEAMS | |
  • | | - Can own records (`ownerid` = Team GUID) | |
  • | | - Can have Security Roles directly assigned | |
  • | | - Membership managed manually in Dataverse | |
  • | +---------------------------------------------------------------------------+ |
  • | | 2. ACCESS TEAMS (Template-Driven) | |
  • | | - CANNOT own records (No record ownership) | |
  • | | - CANNOT have Security Roles assigned | |
  • | | - Dynamically shares records via Access Team Templates & Sub-grids | |
  • | +---------------------------------------------------------------------------+ |
  • | | 3. MICROSOFT ENTRA (AAD) SECURITY GROUP TEAMS | |
  • | | - Auto-synced membership from Entra ID Security Groups | |
  • | | - Can own records AND have Security Roles assigned | |
  • | | - Enterprise identity lifecycle integration (Automated JIT access) | |
  • | +---------------------------------------------------------------------------+ |
  • | | 4. MICROSOFT ENTRA (AAD) OFFICE 365 GROUP TEAMS | |
  • | | - Auto-synced membership from Microsoft 365 Groups / Teams Channels | |
  • | | - Supports modern collaborative M365 workspaces | |
  • | +---------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • 2. Owner Teams: Shared Ownership & Role Aggregation

An Owner Team is a traditional Dataverse team designed to hold shared ownership of data records and propagate security roles to its members.

Core Characteristics

Record Ownership: An Owner Team can be set as the owner of any User/Team-owned record. When a record is assigned to an Owner Team, the record's ownerid field stores the Team's GUID, and the owningbusinessunit matches the Team's Business Unit.

Security Role Assignment: Administrators can assign one or more security roles directly to the Owner Team. Every member of the team inherits all privileges granted by those security roles.

Business Unit Membership: In classic mode, all members of an Owner Team had to belong to the same Business Unit as the team. In modern BU matrix security, users from any Business Unit can be added to an Owner Team.

Use Cases: Ideal for departmental queues (e.g., "Tier 1 Support Queue Team"), regional shared accounts ("Mid-Atlantic Account Team"), and functional processing pools where work items are picked up by any available team member.

3. Access Teams: Lightweight Collaboration & Template-Driven Sharing

When cross-functional groups of users need temporary, ad-hoc access to specific records without changing record ownership or assigning broad security roles, traditional Owner Teams cause administrative bloat. Access Teams solve this challenge. +-----------------------------------------------------------------------------------+

  • | ACCESS TEAM TEMPLATE CONFIGURATION FLOW |
  • | |
  • | [Step 1: Enable Table] |
  • | - Set Table Property: 'Access Teams' = Enabled |
  • | | |
  • | v |
  • | [Step 2: Create Template] |
  • | - Navigate to Settings -> Access Team Templates |
  • | - Target Entity: Opportunity |
  • | - Access Rights Selected: [X] Read [X] Write [ ] Delete [X] Append |
  • | | |
  • | v |
  • | [Step 3: Embed Sub-grid on Form] |
  • | - Add Sub-grid to Opportunity Main Form |
  • | - Entity: Users |
  • | - Selected Access Team Template: 'Deal Collaboration Template' |
  • | | |
  • | v |
  • | [RUNTIME USER EXPERIENCE] |
  • | - Opportunity Owner adds 'Alice' to the form sub-grid. |
  • | - Dataverse automatically instantiates a lightweight access team and shares |
  • | the record with Alice granting Read, Write, and Append permissions! |
  • +-----------------------------------------------------------------------------------+
  • Access Team Mechanics

Zero Record Ownership: Access Teams cannot own records. The record owner remains the original user or owner team.

Zero Security Roles: You cannot assign security roles to an Access Team. The team exists purely as a dynamic sharing mechanism.

Access Team Templates: A template defines the precise set of permissions granted to team members on records of a specific table. Supported access rights include: Read , Write , Append , Append To , Delete , Assign , and Share .

Sub-grid Automation: When an administrator adds a User sub-grid configured with an Access Team Template to a model-driven form, end users can add or remove colleagues directly on the record. Adding a user automatically creates a system-managed access team behind the scenes and shares the record with the specified rights; removing the user instantly revokes access.

Performance Advantage: Unlike static record sharing, template-driven Access Teams are optimized by Dataverse to minimize performance overhead on the PrincipalObjectAccess (POA) table.

4. Microsoft Entra (AAD) Group Teams: Automated Enterprise Governance

In enterprise IT environments, user provisioning and deprovisioning are centralized in Microsoft Entra ID (formerly Azure Active Directory). Managing Dataverse team memberships manually creates compliance drift and audit failures. Microsoft Entra Group Teams automate this lifecycle entirely. +-----------------------------------------------------------------------------------+

  • | MICROSOFT ENTRA (AAD) GROUP TEAM SYNCHRONIZATION |
  • | |
  • | +----------------------------------+ |
  • | | MICROSOFT ENTRA ID (AAD) | |
  • | | Security Group: 'SG-Finance-App'| |
  • | | Members: Alice, Bob, Carlos | |
  • | +----------------------------------+ |
  • | | |
  • | | (Automatic Just-in-Time & Background Sync) |
  • | v |
  • | +----------------------------------+ |
  • | | DATAVERSE ENVIRONMENT | |
  • | | Entra ID Group Team: 'Finance' | |
  • | | Azure AD Object ID: <GUID> | |
  • | | Security Role: Finance Analyst | |
  • | +----------------------------------+ |
  • | | |
  • | +-----------------+-----------------+ |
  • | | | |
  • | v v |
  • | When Alice logs in, Dataverse When Carlos is removed from Entra ID, |
  • | instantly grants 'Finance Analyst' Dataverse automatically revokes his |
  • | permissions via Group Team! permissions upon next token refresh! |
  • +-----------------------------------------------------------------------------------+
  • Entra Group Team Types

Entra Security Group Teams: Bound to an Entra ID Security Group. Ideal for role-based IT access governance.

Office 365 Group Teams: Bound to a Microsoft 365 Group (such as a Microsoft Teams channel). Ideal for collaborative business projects and shared departmental workspaces.

Configuration Parameters

AAD Object ID: The unique Object ID GUID of the group in Microsoft Entra ID.

Business Unit: The Business Unit in Dataverse to which the group team is assigned.

Membership Type: Controls who is synchronized into the team: Members and Guests , Members only , Owners , or Guests only .

Group Privilege Inheritance Options

When configuring an Entra Group Team, administrators select the Membership Privilege Inheritance model:

Inheritance Option Operational Mechanics When to Use

Direct User (Basic) access and Group privileges Members inherit both group privileges AND direct User (Basic) depth privileges. Users can create, modify, and own personal records using the role's privileges. Standard business roles where users perform daily transactional work (e.g., Sales Reps, Support Agents).

Group privileges only Members do NOT inherit User (Basic) depth privileges for personal execution. Users can only act within the context of the team on records owned by the team or business unit. Specialized, restricted roles such as System Auditors, Approvers, or Shared Service Processors who should not create personal records.

5. Architectural Decision Matrix: Choosing the Right Team Type

  • Criteria Owner Team Access Team (Template) Entra Security Group Team
  • Can Own Records? Yes No Yes
  • Can Have Security Roles? Yes No Yes
  • Membership Source Manual in Dataverse Dynamic via Form Sub-grid Automated via Entra ID
  • Dynamic Ad-Hoc Sharing Poor Excellent (Optimized) Poor

Identity Governance Cost High (Manual maintenance) Low (Self-service per record) Minimal (Automated via Azure AD)

Recommended Use Case Departmental record queues Deal/Case collaborative teams Enterprise role assignment

Loading diagram... Dataverse Team Type Decision Flowchart