What it does

The Usage tab under Licensing > Power Automate in the Power Platform admin centre lists the users whose Power Automate action or request consumption is over their daily limit, with a usage trend and the top consumers called out. Select a user and you see the licence context they're consuming under and which flows are driving it.

Key facts

• Sits at Licensing > Products > Power Automate > Usage in the admin centre.
• Per-user detail shows the licence context (Power Automate, Power Apps, Dynamics 365, or Microsoft 365/free) and a breakdown of the flows behind that user's consumption.
• Attribution follows the owner for automated and scheduled flows, and the person who ran it for on-demand flows.
• It only shows consumption attributed to users. Service principals, and flows covered by Process or legacy Per-flow licences, don't appear.
• There's no export option yet. For a tenant-wide download of per-user and per-flow request consumption, use the Power Platform request report instead.

When to use / skip

Use it as the first look when someone says flows are being throttled, or before you decide a client needs more capacity. Skip it for anything involving service principals or Process-licensed flows, because they aren't in it.

Configuration decisions

• Whether a single high-volume flow gets its own Process licence, which gives it 250,000 requests per 24 hours independent of the people who use it.
• Whether several related flows supporting one business process go into a flow group so they can share one Process licence.
• Who in the client's admin team owns checking this page, since nothing alerts you when a user goes over.

Gotchas

• A flow that's already on a Process licence won't show up, so an empty-looking page can mean the problem has been licensed away rather than solved.
• Attribution to the owner means a departed maker's flows can keep landing on one person's line long after they've stopped caring.
• No export means screenshots for the governance pack unless you go the request report route.

Consultant notes

• Use this page to pick flow group candidates before anyone raises a purchase order for extra Process licences. It's usually cheaper to group related flows than license each one.
• Clients tend to read "over their daily limit" as "flows are failing". While the transition limits apply, that isn't necessarily so, so check for actual throttling before escalating.
• Pair it with the licence consumption view for flows with no owner or standalone premium flows on a standard licence. They're different problems and easy to conflate in a steering group.
• Preview-era admin reports change shape without much warning, so screenshot dates matter if you're putting one into a deliverable.

---

Worth revisiting once the page gains export or covers service principals.