Govern an estate you did not build and cannot see.
Power Platform estates are built by makers, not by projects. None of it is hidden — it is spread across four Microsoft admin APIs, each paginated, each throttled, none of which will hand you a single sentence about the whole tenant.
You cannot govern what nobody has ever listed
Apps appear in default environments, flows run on a leaver’s personal connection, premium connectors turn up in trials, and the only copy of something important is a solution somebody exported once.
Ownership
Owner and last-modified on every object, with leavers flagged where the directory no longer resolves them.
Exposure
Everyone an app is shared with and at what level, including anything shared with the entire tenant — with groups expanded into the people they really reach.
Credentials
The account each connection authenticates as, whether it is shared, and everything downstream that depends on it.
Licensing
Premium and custom connector reach, ranked by real usage — a licensing answer and a security answer from one list.
Sprawl
Every environment including default, trial and Teams, with Managed Environment status and what each one holds.
Reporting
Six standing reports over the stored assessment, exportable to Excel, PDF, CSV and JSON.
Six of the questions, answered on a screen
Every screen on this page is the Contoso demo tenant — sample data, rendered through exactly the same code as a real assessment.
Who owns this, and are they still here
Every app and flow carries its owner, and the estate carries the ones whose owner has left. An app running a finance process owned by somebody who went in March is not a governance abstraction — it is an outage with a date on it.
- Owner and last-modified on every object
- Objects whose owner no longer resolves in the directory
- Ownership concentrated in one or two people, made visible
Who can open what
Everyone an app is shared with and at what level, including anything shared with the entire tenant. Where the grants include groups, the headline expands them and reports the people a group actually reaches — a group of four hundred and a single colleague are both “one share” to the platform, and they are not the same exposure.
- Users and groups per app, with their permission level
- Tenant-wide sharing called out rather than counted
- Sharing read live rather than from the stored assessment, because it is the figure most likely to have moved
The connections nobody remembers making
A connection is an identity. Knowing which account a production process authenticates as — and whether that account belongs to a person — is the question that decides how much of the estate is one leaver away from stopping.
- The account each connection runs as, where the API discloses it
- Health status and whether it is shared beyond its owner
- Everything downstream that would break if it went away
Premium reach, without the guesswork
Standard, premium and custom connectors ranked by real usage across the tenant. Premium reach is a licensing question and a security one, and the same list answers both.
- Usage merged from apps, flows and connections
- Licence tier per connector
- Custom connectors with the backend host they call
Every environment, including the ones you forgot
Production, sandbox, developer, trial, Teams and default. The default environment is usually the largest and the least governed, and it is the one nobody has a list of.
- Type, region and state for every environment
- Managed Environment status, so governance gaps are a column rather than a conversation
- What each one holds, object by object
Answers before the audit asks
Prepared views over the stored assessment — governance, security, connectors, environments and pre-migration — and the whole thing exportable in a shape somebody without a licence can read.
- Six standing reports, all derived from the current assessment
- Excel, PDF, JSON and CSV exports of any of it
- Refresh whenever you need the picture brought up to date
Where each one is strongest
Microsoft’s Center of Excellence Starter Kit is a free, open-source toolkit many tenants rely on, and it does things Power Insights deliberately does not. This is a plain account of which tool covers what — many teams run both.
| Capability | CoE Starter Kit | Power Insights |
|---|---|---|
| Where it runs | ||
| Deployment model | Solutions installed into a Dataverse environment in your tenant, with flows, tables and Power BI reports | Hosted service outside your tenant; reads through Microsoft’s admin APIs with your sign-in |
| Writes to your tenant | By design — its processes act on apps, flows and makers | Read-only by default; a few labelled actions (share with me, create a solution) run only when you start them |
| Several tenants from one place | One installation per tenant | Enterprise plan: connect several tenants to one account (MSPs, partners) |
| Inventory and visibility | ||
| Environments, apps, flows, connectors, connections | Core components sync flows, on a schedule | Assessment in minutes, refreshed on demand |
| Solutions, Dataverse tables and connection references | Solutions are inventoried; table and column schema is not the focus | Solution membership per object, tables with columns, connection references resolved |
| Ownership, sharing reach and orphaned objects | Owner and shared-with data, orphaned-object handling | Owner, shared-with count and list per app, leavers flagged, users-per-app export |
| Premium connector and licensing exposure | Power BI dashboards on connector usage | Connectors ranked by real usage with tier, per environment |
| Search inside app packages and flow definitions | Not covered | Hard-coded URLs, SQL statements and stored procedures, SharePoint and Power BI references, action counts |
| Estate map and cross-environment reports | Power BI dashboards per area | Interactive map, governance and pre-migration reports, Excel and PDF export |
| Governance processes | ||
| DLP policy impact analysis and editor | A strength of the kit | Shows connector reach; does not model or edit DLP policies |
| Compliance requests, app archival, inactivity clean-up | Governance components with maker-facing flows | Read-only — reports what is stale, does not archive it |
| Maker onboarding, welcome emails, nurture | Nurture components | Not covered |
| Migration | ||
| Dependency detection and migration plan | Not covered | Per-app dependencies, kanban with notes and stages, plan refreshed from the current assessment |
| Collections across environments and solution creation | Not covered | Pick apps and flows from any environment; preflight and create a Dataverse solution from them |
| Read-only sharing with stakeholders | Power BI sharing, with Power BI licences | Expiring share links, no sign-in needed for the reader |
Effort to get there, and to stay there
Typical figures, not promises — yours depend on the size of the tenant and how much of the kit you deploy.
| Aspect | CoE Starter Kit | Power Insights |
|---|---|---|
| Prerequisites | A dedicated environment with Dataverse, a service account with an admin role, Power Automate premium licensing for that account, Power BI Pro for the dashboards | An administrator account and a browser. A Dataverse security role is needed only for solution, table and connection-reference detail |
| Initial set-up | Typically 1–3 working days for an experienced administrator; 1–2 weeks elapsed once licensing and service-account approvals are included | About ten minutes: sign in, run the assessment |
| Time to a first complete picture | After the first full sync — several hours to a day on a large tenant | Minutes for most tenants; under an hour for the largest |
| Ongoing maintenance | Monthly releases to import and test; sync flows to monitor and repair. Typically 2–4 hours a month, more after a breaking change | None on your side — refresh is one click and the product is maintained for you |
| Skills needed | Solution import, Power Automate, Dataverse, Power BI | Using a web application |
| Cost model | The kit itself is free; the cost is licences for the service account and Power BI, plus people time | Subscription, with a free plan for a single environment. No licences to buy in your tenant |
Estimates are drawn from LogiSam’s own deployments and Microsoft’s published set-up guidance for the CoE Starter Kit, as at 2026. The CoE Starter Kit is a Microsoft project; Power Insights is an independent product by LogiSam and is not affiliated with or endorsed by Microsoft.
The inventory, and what you do with it
Power Insights
The standing picture: what exists, who owns it, what it connects to and what it would break. Read-only, refreshable, available the day you sign in.
- Tenant-wide inventory in minutes
- Ownership, exposure and credential visibility
- Premium connector reach
- Governance reports and exports
Power Platform governance service
The decisions: environment strategy, DLP policy, licensing position, an ALM pipeline and the maker standards that stop the estate drifting back.
- Environment strategy and DLP
- Center of Excellence set-up
- Licensing and premium connector review
- ALM pipelines and maker enablement
Start with the list.
Run a read-only assessment on your own tenant and see the ownership, exposure and premium reach you are actually governing.
Read-only · nothing installed · free plan, no card required
More on Power Insights
Every page of the Power Insights sub-site, and the way back to the rest of LogiSam.