Premium connector exposure: how to find out what your Power Platform licences actually cover
A licence review starts with one question the admin center does not answer directly: which apps and flows use premium connectors, who runs them, and in which environments? Here is how to build the list, and the three exposures that appear in almost every tenant.
LogiSam··6 min read
Connectors come in tiers. *Standard* connectors — SharePoint, Outlook, Teams — are included in most Microsoft 365 licences. *Premium* connectors — SQL Server, Dataverse for canvas apps, HTTP, most third-party services — need a Power Apps or Power Automate licence per user or per app. The cost of getting this wrong is not a fine; it is an unbudgeted true-up when the estate is next reviewed.
What the admin center shows, and what it does not
The Power Platform admin center will tell you which connectors exist in an environment and, with some clicking, which apps use a given connector. It will not give you one list across the tenant, ranked by usage, with the tier on each row and the people who run the apps — which is the shape a licensing conversation needs.
Building the list
- 1For every canvas app, read its connection references — each names a connector id.
- 2For every cloud flow, read the definition and collect the connector of each action and the trigger.
- 3For every connection in each environment, note the connector and the owner.
- 4Tally connector ids across all three, keep the display name and tier from the connector catalogue, and rank by count.
The catalogue is its own trap: the apis endpoint that lists connectors hides many built-ins, so merge what it returns with the connectors you actually observed in use, or your top ten will be missing entries you can see with your own eyes in the maker portal.
The three exposures
- Premium in the default environment. Every user has access to the default environment. A premium connector in an app there, shared with *Everyone*, is a licence requirement for everyone.
- Premium in a trial or developer environment that became production. Nobody planned it, so nobody licensed it. The environment type in the inventory tells you which ones to look at first.
- HTTP and custom connectors. Both premium, both invisible if you only look for named services. A flow that calls an internal API is a premium flow.
Turning it into a position
Group the list by environment and by owner. For each premium connector, count distinct users who can run something that uses it — that is the per-user exposure — and count apps, which is the per-app alternative. Present both; the cheaper of the two is your recommendation, and the list of names is what makes it credible.
Keep reading
How to inventory an entire Microsoft 365 tenant's Power Platform estate in an afternoon
Every environment, every Power App, every Power Automate flow, every connection — the estate is all there, spread across four admin APIs that each refuse to describe the whole. Here is how to bring it into one list, and what to do about the parts Microsoft will not tell you.
Environment sprawl in Microsoft 365: default, developer, Teams and trial environments explained for governance leads
Thirty-seven environments. Nobody created most of them on purpose. This is what each type is, how it came to exist, and what a governance lead should ask about it — with the one policy change that stops the count growing.
The Power Platform Center of Excellence Starter Kit and Power Insights: what each does best
Microsoft's CoE Starter Kit is the reference toolkit for a Power Platform Center of Excellence, and many tenants run it well. Power Insights covers some of the same ground and none of some of it. This is a plain account of which does what, written for the administrator who has to decide whether they need one, the other, or both.