Power Platform Admin Center Monitoring
Building and deploying solutions is only half the job of a Power Platform professional. The other half is making sure those solutions keep running well — that environments have enough storage, that flows are not failing silently, that licenses are being used efficiently, and that the platform is not being misused. The Power Platform Admin Center is the control room for all of this. This topic teaches you what to monitor, what numbers matter, and how to respond when something goes wrong.
The Power Platform Admin Center: Your Control Room
Access the Admin Center at admin.powerplatform.microsoft.com. You need the Global Admin, Power Platform Admin, or Dynamics 365 Admin role in Microsoft Entra to access it. Everything that affects the entire organization's Power Platform deployment happens here — environment creation, policy management, capacity monitoring, license assignment, and health monitoring.
ADMIN CENTER NAVIGATION MAP
admin.powerplatform.microsoft.com
│
├── Environments
│ └── Create, configure, manage all environments
│
├── Analytics
│ ├── Power Apps (usage metrics, active users, errors)
│ ├── Power Automate (run history, flow performance)
│ └── Dataverse (API calls, storage trends)
│
├── Resources
│ ├── Capacity (storage usage, add-ons)
│ ├── Dynamics 365 apps (installed solutions)
│ └── Portals, AI Builder credits
│
├── Help + Support
│ └── Create support tickets, view service health
│
├── Data Policies
│ └── DLP policies (covered in Topic 21)
│
├── Billing
│ ├── Licenses assigned
│ └── Pay-as-you-go setup
│
└── Settings
└── Tenant-level feature flags, preview features
Environment Overview: Your First Dashboard
Click Environments in the left sidebar. You see a list of all environments in your tenant. Each row shows the environment name, type (Production, Sandbox, Developer, Default), region, and state (Ready, Preparing, etc.). Click any environment to open its detail page — this is where most day-to-day administration happens for that environment.
The Environment Detail Page
ENVIRONMENT DETAIL PAGE SECTIONS Overview tab: Environment URL → The web address used to access this environment Region → Where the data physically lives (India, Europe, etc.) Version → Current Dataverse version Created by / Created on → Who created it and when Security group → Entra group that controls who can access this env Edit settings link → Opens full configuration options Resources tab: Apps, Flows, Connections, Custom connectors, Gateways installed here Settings tab: Features, Product, Business, Audit, Users + permissions (Almost all per-environment configuration lives here) Activity tab: Recent admin actions performed on this environment (audit trail)
Restricting Environment Access with Security Groups
By default, every Microsoft 365 user in your organization can access every environment (assuming they have a Power Platform license). Linking a security group to an environment restricts access — only members of that group can use the environment. This is critical for production environments: you want only named, authorized users accessing live business data.
Open the environment detail page. Click Edit in the top-right of the Overview section. In the Security group field, search for and select a Microsoft Entra security group. Save. Now only group members can sign in to this environment. Anyone outside the group attempting to open an app hosted there receives an access-denied message.
Analytics: Understanding Platform Usage
Power Apps Analytics
In the Admin Center, click Analytics → Power Apps. The dashboard shows usage across all apps in the selected environment. Key metrics include total sessions per day, unique users, sessions per app, error rates, and median session duration. A spike in error rate after a deployment is your first signal that something broke in production. A drop in active users may signal that users abandoned an app because it was too slow or confusing.
POWER APPS ANALYTICS DASHBOARD TIME RANGE: Last 30 days ENVIRONMENT: Production ┌──────────────────────────────────────────────────────────────┐ │ Total Sessions: 4,820 Unique Users: 187 │ │ Avg. Daily Sessions: 160 Median Session Duration: 4m 32s │ ├──────────────────────────────────────────────────────────────┤ │ TOP APPS BY SESSIONS │ │ IT Help Desk App 2,150 sessions ● Healthy │ │ Expense Submission App 1,440 sessions ● Healthy │ │ Asset Register App 790 sessions ⚠ 12 errors │ │ Visitor Log App 440 sessions ● Healthy │ ├──────────────────────────────────────────────────────────────┤ │ ERROR RATE TREND (last 7 days) │ │ [Line chart — spike on June 3 after v2.1 deployment] │ └──────────────────────────────────────────────────────────────┘
Power Automate Analytics
Click Analytics → Power Automate. See total flow runs, pass rate, failure rate, and average run duration per day. Drill into individual flow run statistics. A flow with a 40% failure rate needs immediate investigation — either the underlying data has changed, an API it calls is unreliable, or a logic error has been introduced. The analytics identify which specific flows have the highest failure rates so you focus attention where it matters most.
Dataverse Analytics
Dataverse analytics shows API call volumes, storage consumption trends, and plugin execution times. Watch for API call spikes that may indicate a runaway flow (a flow stuck in an infinite loop calling the API thousands of times per hour). Storage trends help you forecast when you will need to add capacity before hitting the storage ceiling.
Capacity Management: Storage and Add-Ons
Power Platform storage is a shared pool across the entire tenant. Every Dataverse environment consumes from this shared pool. Running out of storage is catastrophic — new records cannot be saved, flows fail, apps stop working. Monitor capacity proactively and add storage before it is full.
The Three Storage Types
POWER PLATFORM STORAGE TYPES ┌─────────────────────────────────────────────────────────────┐ │ TOTAL TENANT CAPACITY │ ├───────────────────┬──────────────────────┬──────────────────┤ │ DATABASE Storage │ FILE Storage │ LOG Storage │ │ │ │ │ │ Dataverse table │ Attachments, │ Audit logs, │ │ data, records, │ file/image columns, │ plugin trace │ │ metadata │ SharePoint metadata │ logs │ │ │ │ │ │ Included: │ Included: │ Included: │ │ 1 GB base + │ 1 GB base + │ 2 GB per tenant │ │ per-user add-ons │ per-user add-ons │ │ └───────────────────┴──────────────────────┴──────────────────┘ Base allocation per licensed user (approximately): Per Power Apps/Automate Per User license: +250 MB Database + 2 GB File Per Dynamics 365 Enterprise user: +1 GB Database + 3 GB File
Viewing Capacity in the Admin Center
Click Resources → Capacity. A summary shows total tenant capacity, how much is used, and how much remains — broken down by Database, File, and Log. Scroll down to the Environment breakdown — each environment's consumption is listed individually. Environments with disproportionately high storage (perhaps from audit logs or large file attachments) stand out immediately and are candidates for cleanup or archival.
Reducing Storage Consumption
When storage is tight, several strategies help. Delete old records: flows that accumulate log or tracking records over years consume enormous database storage — archive or delete records older than a defined retention period. Remove plug-in trace logs: these grow silently and consume log storage. Disable audit logging for non-critical tables: audit logs for high-activity tables (like a table that receives thousands of writes per day) fill up log storage quickly. Compress or externalize file attachments: store large files in SharePoint or Azure Blob and save only the URL in Dataverse instead of the binary content.
Monitoring Flow Health Across the Tenant
Individual flow owners monitor their own flows through the "My Flows" page. Admins need visibility across all flows in an environment — including flows owned by people who have left the organization.
The Power Automate Admin View
In the Admin Center → Environments → select environment → Resources → Flows. This lists every flow in the environment regardless of owner. You see the flow name, owner, state (on/off), and last run date. Filter to show only suspended or failed flows. Flows marked as Suspended have a broken connection or missing license — they need attention. Flows whose owner has left the organization appear with an inactive owner — reassign ownership to keep them running.
Center of Excellence (CoE) Starter Kit
For large organizations, Microsoft provides the Power Platform Center of Excellence (CoE) Starter Kit — a free, open-source collection of apps, flows, and dashboards that give administrators deep visibility into their entire Power Platform tenant. Install it from GitHub (microsoft/coe-starter-kit). It provides an inventory of all apps and flows across all environments, risk scoring for high-business-impact apps, maker activity tracking, unused resource cleanup workflows, and a maker welcome email automation. The CoE Starter Kit is itself built on Power Platform — a compelling demonstration of the platform's own capabilities.
CoE STARTER KIT DASHBOARDS (examples) Power Platform Admin View app shows: ├── 47 environments across tenant ├── 892 active canvas apps ├── 1,247 cloud flows (891 active, 356 suspended) ├── 43 flows with owners who have left the organization ├── 12 apps with no activity in 90+ days └── Top 10 makers by solution count Environment Risk Dashboard: ├── High-use apps without ALM (built in default environment) ├── Apps shared with "everyone in the org" in production └── Flows using deprecated connectors
License Management
Viewing License Assignments
In the Microsoft 365 Admin Center (admin.microsoft.com) → Users → Active users, you see every user and their assigned licenses. Filter by license type to find all Power Apps Per User or Power Automate Premium license holders. This view shows you who has premium licenses and — just as importantly — who has licenses they never use.
Pay-As-You-Go: The Flexible Alternative
Pay-as-you-go (PAYG) connects a Power Platform environment to an Azure subscription and bills for actual usage rather than pre-purchased licenses. Instead of buying 50 Power Apps Per User licenses for occasional users, PAYG charges per app session — roughly a few cents per user per day they use an app. For apps used by a large but infrequent audience (like an annual review form or an emergency procedures app), PAYG is significantly cheaper than per-user licenses. Configure PAYG in the Admin Center → Environments → select environment → Billing policy → Add PAYG policy → select your Azure subscription.
License Usage Reports
In the Admin Center → Analytics → Power Apps, you see active users per day. Cross-reference this with your license count to understand license utilization. If you have 200 Power Apps Per User licenses but only 60 unique users opened an app in the last 30 days, you have 140 licenses that may be reassignable or reducible at renewal. Regular reviews prevent wasted licensing spend.
Tenant Settings: Controlling the Entire Platform
In the Admin Center → Settings (at the tenant level, not environment level), you control platform-wide behaviors.
IMPORTANT TENANT SETTINGS Power Apps: ├── Who can create production environments (Admins only / Everyone) ├── Who can create trial environments ├── Canvas app sharing with external users (on/off) └── Who can create connectors (Everyone / Admins only) Power Automate: ├── Who can create desktop flows ├── Allow sharing flows with external users (on/off) └── Attended RPA session limits Copilot Studio: └── Allow publishing bots to external channels (on/off) AI features: └── Allow AI Builder (on/off), Copilot features (on/off)
Restricting environment creation to admins only is a common governance decision for large organizations — it prevents users from creating dozens of unchecked environments that accumulate over time, consuming storage and spreading solutions across places nobody tracks.
Service Health and Support
In the Admin Center → Help + support → Service health, you see the current status of all Power Platform services — whether each service (Power Apps, Power Automate, Dataverse per region) is healthy, degraded, or experiencing an outage. Check this page first whenever users report that apps or flows are not working — before spending hours debugging what might simply be a Microsoft infrastructure incident. You can also subscribe to email alerts for service health changes so you know about incidents before users report them.
Key Points
- The Power Platform Admin Center (admin.powerplatform.microsoft.com) is the central control point for environments, policies, capacity, analytics, and tenant settings.
- Link Microsoft Entra security groups to production environments to restrict access to named, authorized users only.
- Analytics dashboards show app session counts, flow run pass/fail rates, and Dataverse API call volumes — use these to detect problems after deployments and identify underperforming solutions.
- Power Platform storage has three types: Database, File, and Log. Monitor consumption in Resources → Capacity and take action (archiving, log cleanup, attachment externalization) before reaching the limit.
- Use the Admin view of environments (Resources → Flows) to find suspended flows and flows with inactive owners — reassign before they break business processes.
- The CoE Starter Kit provides a free, comprehensive admin toolkit — app/flow inventory, risk scoring, maker activity, and cleanup workflows — built on Power Platform itself.
- Pay-as-you-go licensing connects an environment to an Azure subscription and bills per session — ideal for large but infrequent user audiences instead of pre-purchased per-user licenses.
- Check Service Health before debugging reported outages — the problem may be a Microsoft infrastructure incident, not a bug in your solution.