Study guide

2.2 Auditing Configuration & Log Management

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

2.2 Auditing Configuration & Log Management

Key Takeaways Explain This Topic AI

Dataverse auditing follows a strict 3-tier hierarchical structure: Environment (Organization) level, Table level, and Column level.

Auditing will not track field-level changes unless auditing is enabled at BOTH the Environment level AND the specific Table level, with the individual Column auditing flag set.

Audited operations encompass record Create, Update (old vs. new values), Delete, Share, Assign, Associate/Disassociate, security role assignments, and user logon access.

Audit logs consume the Dataverse 'Log' capacity tier and are stored in quarterly SQL database partitions.

Administrators manage log capacity in PPAC by defining audit retention policies or deleting historical quarterly audit partitions up to a specified cutoff date.

Last updated: August 2026

Auditing Configuration & Log Management

Enterprise organizations operating in regulated industries (healthcare, finance, government) must maintain strict traceability of data modifications, security role assignments, and user access patterns. In Microsoft Dataverse, Auditing provides an immutable, chronological record of transactions. For the PL-200 exam, functional consultants must understand how to configure the 3-tier auditing hierarchy , interpret audit logs, manage log storage capacity, and execute partition deletions.

1. The 3-Tier Auditing Hierarchy

Auditing in Dataverse operates as an inheritance model. If a higher tier is disabled, subordinate tiers cannot generate audit entries. +-----------------------------------------------------------------------------------+

  • | 3-TIER AUDITING HIERARCHY MODEL |
  • | |
  • | [TIER 1: ENVIRONMENT / ORG LEVEL] (PPAC / Environment Settings) |
  • | - Start Auditing: [Enabled] |
  • | - Log user access: [Optional] |
  • | - Read audit: [Optional] |
  • | | |
  • | | (Must be ON for any auditing to occur) |
  • | v |
  • | [TIER 2: TABLE LEVEL] (Table Properties / Advanced Options) |
  • | - Audit changes to its data: [Enabled] |
  • | | |
  • | | (Must be ON for table operations & columns to be audited)|
  • | v |
  • | [TIER 3: COLUMN LEVEL] (Column Properties / Advanced Options) |
  • | - Enable auditing: [Enabled] (Default is Enabled on most standard columns) |
  • | (Tracks specific attribute changes: Old Value ---> New Value) |
  • +-----------------------------------------------------------------------------------+
  • Auditing Tier Configuration Matrix

Level Where Configured Setting Name Effect When Disabled

Tier 1: Environment PPAC > Environment > Settings > Audit settings Start Auditing No audit records of any kind are written across the entire environment.

Tier 2: Table Maker Portal > Table Properties > Advanced options Audit changes to its data No create, update, delete, or share events are tracked for this table, regardless of column settings.

Tier 3: Column Maker Portal > Column Properties > Advanced options Enable auditing Changes to this specific column are ignored; table-level create/delete events still record.

Important

Rule of Auditing Inheritance: For a specific column modification to appear in the audit trail, auditing MUST be enabled at Tier 1 (Environment), Tier 2 (Table), and Tier 3 (Column) . If any layer in the chain is turned off, column value changes will not be logged.

2. Tracked Events & Auditing Capabilities

Dataverse captures a comprehensive array of data modification, relationship, and administrative security events. +-----------------------------------------------------------------------------------+

  • | DATAVERSE AUDITED EVENT SPECTRUM |
  • | |
  • | [DATA OPERATIONS] [SECURITY & ACCESS] [RELATIONSHIPS] |
  • | - Create Record - User Logon Access - Associate (N:N, 1:N) |
  • | - Update Field (Old->New) - Security Role Assigned - Disassociate |
  • | - Delete Record - Security Role Removed - Assign (Change Owner) |
  • | - Read / Export View - Business Unit Move - Share / Modify Rights |
  • +-----------------------------------------------------------------------------------+
  • Breakdown of Tracked Operations

Record Lifecycle Events:

Create: Logs the timestamp, creating user, and initial values.

Update: Captures the exact Old Value and New Value for every audited column changed during the transaction.

Delete: Records the deletion timestamp, user, and the primary name/GUID of the deleted record.

Security & Governance Events:

User Access Logging: Tracks when users log into the Dataverse environment (via Web, Outlook, Mobile, or API).

Security Role Changes: Tracks granting or revoking security roles to users or teams.

Business Unit Reassignment: Records when users or records move between business units.

Collaboration & Relationship Events:

Sharing & Rights: Records when a record is shared with users/teams and what specific privileges (Read, Write, Delete, Append) were granted or revoked.

Assign: Tracks changes in record ownership from one user/team to another.

Associate / Disassociate: Tracks linking or unlinking records across many-to-many (N:N) or one-to-many (1:N) relationships.

3. Reviewing Audit Trails

Dataverse provides two primary interfaces for inspecting audit data: +-----------------------------------------------------------------------------------+

  • | AUDIT DATA VIEWING INTERFACES |
  • | |
  • | +-------------------------------------+ +------------------------------------+ |
  • | | RECORD AUDIT HISTORY TAB | | AUDIT SUMMARY VIEW | |
  • | | (Model-Driven Form > Related > Audit)| | (PPAC / Environment Settings) | |
  • | | | | | |
  • | | - Single-record timeline view | | - Global system-wide audit stream | |
  • | | - Field-by-field delta display | | - Filter by Entity, User, Event | |
  • | | - Shows Old Value vs. New Value | | - Exportable for compliance review | |
  • | +-------------------------------------+ +------------------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Sample Record Audit Entry Structure
  • Changed Date Changed By Event Changed Field Old Value New Value
  • 2026-08-17 09:15 AM Sarah Davis Update Credit Limit $50,000 $100,000
  • 2026-08-17 09:15 AM Sarah Davis Update Payment Terms Net 30 Net 60
  • 2026-08-14 02:30 PM Alex Brown Assign Owner Alex Brown Enterprise Sales Team
  • 2026-08-10 11:00 AM System Create Account Name null Fabrikam Technologies
  • 4. Log Storage Governance, Retention & Partition Deletion

Audit records are stored in the Dataverse Log Storage Tier (distinct from Database and File storage tiers). Because high-volume transactional tables can rapidly generate gigabytes of audit records, administrators must implement active log governance. +-----------------------------------------------------------------------------------+

  • | AUDIT PARTITIONING & DELETION TIMELINE |
  • | |
  • | [Q1-2025 Partition] [Q2-2025 Partition] [Q3-2025 Partition] [Q4-2025 (ACTIVE)] |
  • | (Closed) (Closed) (Closed) (Open / Writing)|
  • | =================== =================== =================== ===================|
  • | [ DELETE CANDIDATE ] [ DELETE CANDIDATE ] [ DELETE CANDIDATE ] [ CANNOT DELETE ] |
  • | <--------------------------------------- |
  • | Admin can delete partitions up to a selected cutoff date |
  • +-----------------------------------------------------------------------------------+
  • Audit Log Retention Policies

In the Power Platform Admin Center, administrators can configure automated Audit Retention Policies :

Navigate to PPAC > Environment > Settings > Audit settings .

Under Retain these logs for , choose a retention window:

30 days , 90 days , 180 days , 1 year , Custom , or Forever .

Dataverse automatically purges audit partitions that exceed the configured retention horizon.

Quarterly Audit Partition Management

Dataverse divides audit storage into quarterly chronological database partitions (e.g., Q1, Q2, Q3, Q4 of each calendar year).

Caution

Partition Deletion Rules:

You can delete historical, closed audit partitions to reclaim Log capacity.

You CANNOT delete the current active partition (the partition currently receiving live transaction logs).

Deleting an audit partition removes all audit entries across all tables within that quarterly timeframe permanently. This action is irreversible.