Study guide

13.2 Environment Governance, Groups, Routing & Capacity 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

13.2 Environment Governance, Groups, Routing & Capacity Management

Key Takeaways Explain This Topic AI

By default, all tenant users can create Trial and Developer environments, making it vital for administrators to restrict environment creation permissions to Global Admins and Power Platform Admins in PPAC settings.

Environment Groups enable centralized governance at scale, allowing administrators to organize environments into logical tiers and automatically apply uniform policies like Managed Environments activation and sharing limits.

Environment Routing automatically directs new makers to their own dedicated, personal Developer environments upon visiting Power Apps Studio, effectively preventing sprawl and unmanaged development in the Default environment.

Dataverse storage capacity is divided into three distinct, non-fungible consumption pools: Database Capacity (tables/schema), File Capacity (attachments/documents), and Log Capacity (audit and trace logs).

Exceeding tenant storage capacity freezes administrative environment operations (creating, copying, restoring, resetting, or converting environments) but does NOT cause runtime outages for existing user read/write operations or running flows.

Last updated: August 2026

Environment Governance, Groups, Routing & Capacity Management

As organizations scale their adoption of the Microsoft Power Platform, unmanaged citizen development can quickly lead to environment sprawl, fragmented security policies, and unexpected storage capacity overages. Enterprise governance requires establishing strict boundaries around who can provision environments, how environments are structured into manageable groups, how makers are onboarded, and how Dataverse storage consumption is tracked and remediated across the tenant.

1. PPAC Governance & Restricting Environment Creation

In an unmanaged Microsoft Entra ID tenant, default platform settings allow any licensed user to self-provision Trial and Developer environments. This self-service model frequently results in hundreds of unmonitored environments that consume shared resources and bypass organizational compliance. +-----------------------------------------------------------------------------------+

  • | PPAC TENANT-LEVEL GOVERNANCE CONTROLS |
  • | |
  • | [ENVIRONMENT CREATION PERMISSIONS] |
  • | - Production & Sandbox Environments: [Only Specific Admins] |
  • | - Trial Environments: [Only Specific Admins] |
  • | |
  • | [SECURITY GROUP FILTERING] |
  • | - Bind Entra Security Group to Environment |
  • | - Only members of the Security Group are synced to Dataverse |
  • | |
  • | [ENVIRONMENT ROUTING] |
  • | - New maker navigates to make.powerapps.com |
  • | - Platform auto-creates personal Developer environment |
  • | - Maker lands in their own workspace, leaving Default environment clean |
  • +-----------------------------------------------------------------------------------+
  • Restricting Environment Creation Permissions

Within the Power Platform Admin Center (PPAC) Tenant Settings , administrators can restrict provisioning rights:

Production and Sandbox environments: Can be configured to allow "Everyone" or restricted to "Only specific admins" (Global Administrators and Power Platform Administrators).

Trial environments: Can similarly be restricted to administrators to prevent users from consuming trial capacity or spinning up temporary silos.

Entra ID Security Group Association

To control which users can access a specific Dataverse environment:

Administrators can associate a Microsoft Entra Security Group with the environment in PPAC.

When a security group is linked, only users who are direct or nested members of that security group are synchronized into the Dataverse environment's systemuser table .

Any user not in the security group is denied access at the network and authentication boundary, even if they hold an active Power Apps per-user license.

2. Environment Groups & Environment Routing

Managing dozens or hundreds of environments individually creates administrative overhead and policy drift. Microsoft introduced Environment Groups and Environment Routing to automate governance. +-----------------------------------------------------------------------------------+

  • | ENVIRONMENT GROUPS ARCHITECTURE |
  • | |
  • | +-----------------------------------------------------------------------------+ |
  • | | ROOT ENVIRONMENT GROUP: "ENTERPRISE GOVERNANCE" | |
  • | | | |
  • | | +--------------------------+ +--------------------------+ | |
  • | | | DEV / SANDBOX GROUP | | PRODUCTION GROUP | | |
  • | | | - Solution Checker: WARN | | - Solution Checker: BLOCK| | |
  • | | | - Sharing Limit: Max 10 | | - Sharing Limit: Sec Group| | |
  • | | | - Weekly Usage Digest | | - IP Firewall Enforced | | |
  • | | +--------------------------+ +--------------------------+ | |
  • | +-----------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Environment Groups

Logical Containers: Environment Groups allow administrators to organize multiple individual environments into structured containers (e.g., Development, Testing, Production, or Regional business units).

Rule Inheritance: Group rules automatically cascade to all member environments. When an environment is moved into a group, it immediately inherits all group policies, such as:

Managed Environments Activation: Automatically enforces managed governance across all group members.

Sharing Limits: Caps the maximum number of users with whom canvas apps can be shared, or enforces sharing only with security groups.

Solution Checker Enforcement: Automatically inspects solutions during import and either issues warnings or blocks the import if critical security or performance violations are detected.

Backup Retention & Cadence: Establishes uniform backup and governance settings.

Environment Routing

The Citizen Developer Dilemma: When new makers access make.powerapps.com , they historically landed in the Default environment, leading to massive sprawl of test apps, temporary tables, and unmanaged connections in the tenant's primary container.

Routing Mechanics: When Environment Routing is enabled in PPAC, the platform automatically intercepts new makers on their first visit to Power Apps Studio and provisions a personal, dedicated Developer environment for them.

Maker Experience: The maker is automatically granted the System Administrator role in their personal sandbox, enabling them to explore Dataverse, build canvas apps, and test flows freely. Meanwhile, the Default environment remains protected from citizen-developer clutter.

Managed Environments Overview

Managed Environments is a premium governance suite that elevates administrative control across Power Platform environments (requiring standalone Power Apps/Automate licenses for active users):

Maker Welcome Content: Custom onboarding markdown and links displayed to makers when they enter the environment.

Usage Insights: Automated weekly email digests summarizing active apps, inactive flows, and license consumption.

Extended Security: Enables Customer-Managed Keys (CMK), IP Firewall restrictions, and Virtual Network (VNet) support.

3. Dataverse Storage Capacity Architecture

Microsoft Dataverse utilizes a tiered, cloud-scale storage model that separates relational data, binary files, and operational logs into three distinct physical storage engines. Storage capacity is pooled at the tenant level. +-----------------------------------------------------------------------------------+

  • | DATAVERSE STORAGE POOL ARCHITECTURE |
  • | |
  • | [1. DATABASE CAPACITY] [2. FILE CAPACITY] [3. LOG CAPACITY] |
  • | - Relational table data - Document attachments - Audit log history |
  • | - Column metadata & schema - PDF, Word, Excel files - Plug-in trace logs |
  • | - System jobs & workflows - Photos & video media - API telemetry data |
  • | - Security roles & privileges - App canvas images - System event logs |
  • | |
  • | Accrual: Base + Per User Accrual: Base + Per User Accrual: Base Only |
  • | (10 GB Base + 250 MB/User) (20 GB Base + 2 GB/User) (2 GB Base Tenant) |
  • +-----------------------------------------------------------------------------------+
  • The Three Storage Capacity Types

Database Capacity:

Stores: Relational table records, schema definitions, custom column metadata, entity relationship mappings, security role configurations, business process flows, and asynchronous system job records.

Engine: Azure SQL Database and Cosmos DB relational backends.

Accrual: Standard tenant allocation (e.g., 10 GB base) plus accrued capacity per paid user license (e.g., +250 MB per Power Apps Premium user).

File Capacity:

Stores: Binary attachments, document uploads (PDFs, Word documents, spreadsheets), high-resolution images, signatures, and media files associated with records.

Engine: Azure Blob Storage.

Accrual: Standard tenant allocation (e.g., 20 GB base) plus generous accrued capacity per paid user license (e.g., +2 GB per Power Apps Premium user).

Log Capacity:

Stores: Dataverse record audit history (record creations, updates, deletions, and access timestamps), plug-in trace logs ( plugintracelog ), and system telemetry.

Engine: Azure Cosmos DB and Azure Log Analytics storage.

Accrual: Fixed base tenant allocation (e.g., 2 GB base) with no per-user license accrual; additional capacity must be acquired via add-on packs.

Storage Category Backing Storage Technology Typical Data Stored Accrual Formula Add-On Unit Size

Database Azure SQL / Transact-SQL Tables, Rows, Solutions, Metadata Base (10 GB) + per-seat accrual 1 GB increments

  • File Azure Blob Storage Email attachments, PDFs, Photos Base (20 GB) + per-seat accrual 1 GB increments
  • Log Azure Cosmos DB / Telemetry Audit history, Plug-in traces Base (2 GB fixed) 1 GB increments
  • 4. Capacity Over-Quota Enforcement & Remediation

Understanding what happens when a tenant exceeds its allocated storage capacity is an essential operational skill frequently evaluated on the PL-200 exam. +-----------------------------------------------------------------------------------+

  • | TENANT OVER-QUOTA ENFORCEMENT SEMANTICS |
  • | |
  • | [OPERATIONS BLOCKED] [OPERATIONS PERMITTED (NO OUTAGE)] |
  • | - Creating new environments - Existing apps continue working |
  • | - Copying existing environments - End users can read/write data |
  • | - Restoring environment backups - Creating new rows and records |
  • | - Resetting existing environments - Power Automate flows continue run |
  • | - Converting Sandbox to Production - End users experience zero downtime |
  • +-----------------------------------------------------------------------------------+
  • Over-Quota Enforcement Boundaries

When an organization exceeds its total entitled capacity in any of the three storage categories (Database, File, or Log):

Administrative Operations are BLOCKED:

You cannot provision any new environments (Sandbox, Production, or Trial).

You cannot execute environment Copy, Restore, or Reset operations.

You cannot convert a Sandbox environment into a Production environment.

End-User Runtime is NOT BLOCKED:

Existing model-driven apps, canvas apps, and Power Pages sites remain 100% operational.

Users can freely create, read, update, and delete table records.

Power Automate cloud flows and background automations continue to trigger and execute normally.

Microsoft never causes sudden operational business outages due to storage capacity overages.

Minimum Creation Threshold

To create any new Dataverse environment or enable a database in an existing environment, the tenant must have at least 1 GB of available Database capacity .

Capacity Remediation Strategies

If a tenant is over quota, administrators have four primary remediation paths:

Purchase Capacity Add-Ons: Buy additional 1 GB Database, File, or Log Capacity add-on subscriptions through the Microsoft 365 Admin Center.

Purge Audit Logs: Delete historical audit partitions or disable auditing on high-frequency tables.

Clean Asynchronous Jobs & Traces: Bulk-delete completed system jobs, workflow execution histories, and plug-in trace logs using Dataverse Bulk Deletion jobs.

Offload File Storage: Re-architect solutions to store large document attachments in SharePoint or Azure Blob Storage rather than directly inside Dataverse file columns.