One assessment. Every object in the tenant.
Environments, apps, flows, connections, connection references, connectors, solutions, Dataverse tables and columns — each one linked to the things it depends on, and all of it exportable.
Six screens, and what each one tells you
One assessment reads the whole estate and stores it, so every page afterwards loads from storage rather than calling Microsoft again.
Every app in the tenant, and what it actually touches
Canvas and model-driven apps across every environment, with owner, version, sharing reach and the exact connectors and connections each one binds to.
- Owner, version, created and last-modified dates
- Sharing reach — who can open it and at what level
- Connector bindings, with standard/premium/custom tiering
Cloud flow inventory, resolved to its credentials
Trigger type, run state and action count for every Power Automate flow — plus the connection references each one resolves through, followed all the way to the account it runs as.
- Trigger type and run state
- Action count per flow
- Connection references resolved end to end
Tenant-wide environment inventory
Every environment from production to trial, with region, type, Dataverse version and Managed Environment status — the map a CoE works from.
- Region, type and Dataverse version
- Managed Environment status
- Object counts per environment
Which account is really running production
The account a connection runs as, whether it is shared, its status, and everything that depends on it — so a personal connection behind a business process stops being invisible.
- Owning account and shared status
- Connection health
- Every app and flow that depends on it
Connector usage and tiering, so licensing stops being a guess
Standard, premium and custom connectors ranked by real usage across the tenant — the evidence behind a premium licensing conversation.
- Standard, premium and custom tiers
- Ranked by actual usage
- Drill into what uses each one
Excel and PDF, for the people without a licence
The whole assessment or any single object, exported in a shape an auditor, a CFO or a migration partner can read without signing in.
- Whole assessment or single object
- Excel, PDF, CSV and the raw records
- Ready for audit and migration planning
Everything in the tenant, object by object
Every object links to the things it depends on, so a question about one is always one click from the answer about the rest.
Tenant-wide environments
Every environment, production to trial, with region, type, Dataverse version and Managed Environment status.
Canvas & model-driven apps
Owner, version, created and modified dates, sharing reach, and the connectors behind each screen.
Cloud flow inventory
Trigger type, run state, action count and the connection references each flow resolves through.
Connections and their owners
Which account a connection runs as, whether it is shared, its status, and everything that depends on it.
Connector usage and tiering
Standard, premium and custom connectors ranked by real usage, so licence exposure stops being a guess.
Connection references resolved
The indirection between a flow and its credentials, followed all the way through and shown end to end.
Solutions and components
Publisher, version, managed state and a component-type breakdown of what each solution actually carries.
Dataverse tables and columns
Tables with ownership, auditing and change-tracking flags, down to column type and requirement level.
Excel and PDF exports
The whole assessment or any single object, exported in a shape a non-user can read without a licence.
The things Microsoft’s APIs will not tell you
The admin APIs describe what an app is bound to. They say nothing about a URL typed into a Patch() — so these tools read the app source instead.
Search inside app packages
Hardcoded URLs, SharePoint references and arbitrary strings, read from the app source rather than from the admin APIs — which never see them.
Flow action and SQL search
Find flow actions by kind, and the SQL server, database and stored procedure each step reaches. Every answer exports.
Power BI integrations
The connector, the data sources behind it and the embedded tiles — the Power BI surface attached to your Power Platform estate.
Interactive estate map
Objects and their dependencies drawn as a map, so a cross-environment relationship is something you can see rather than reconstruct.
Inventory your own tenant.
The free plan assesses one environment with up to three users — enough to see the shape of the thing before you commit to anything.
Read-only · nothing installed · no card required
More on Power Insights
Every page of the Power Insights sub-site, and the way back to the rest of LogiSam.