Power AppsEvery app, and what it actually touches
The admin centre tells you an app uses a SQL connection. It does not tell you which server, which database, or that eighty-four people were given access one at a time. Power Insights reads the app's own package to answer the first and the permissions resource to answer the second.
- Owner, type, version and last-modified for every app in the tenant
- Sharing split into users and groups — and expanded into the people a group actually reaches
- Connectors and connections resolved per data source, not collapsed to one row
- The SQL server and database each app is really pointed at, read from the .msapp package
One app, and who can open it
Owner, version, environment and dates on the left; everyone who can open or edit it on the right, at what level. Ninety people on this one, which is the number that starts conversations. Where the grants include groups the headline expands them and reports the people a group actually reaches rather than counting it as one — a group of four hundred and a single colleague are both “one share” to the platform, and they are not the same exposure.
What the app is joined to
The app in the middle, what it reaches around it. This one binds four connectors, calls no flows, and — the line under the heading says so plainly — is in no solution, so each of those four is a separate thing to recreate by hand in the target environment. An app that IS in a solution gets the whole picture drawn inside a box carrying the solution's name, because that box is the unit that actually travels.
Connectors
Every connector the app binds, with its licensing tier and whether it was written in this tenant. Premium is the one that carries a cost per user, and custom is the one that does not come with a solution export — so both are marked rather than left to be looked up.
Data sources
The tables, lists and services the app reads or writes, with a Points to column that names the actual server and database — not “a SQL connection”. The note above the table is deliberate: it says how many rows came from the app package and how many from the admin API, because those are different levels of certainty and one merged list would hide it.
Take it with you
A three-page PDF for the steering pack, a six-sheet Excel workbook for the analyst, the untouched Microsoft API response for whoever does not believe either, and the canvas app package itself. The same export menu is on every list in the product.
Every screen here is a live demo tenant
Contoso is sample data, generated rather than scanned — but it renders through exactly the same code as a real tenant, so what you walk around is what you would get.