Features
Everything one assessment gives you
One read of the tenant, stored, then every page below opens instantly from it. Nothing here needs an agent, an installed solution or a change to your environments.
The whole tenant on one screen
Every total, the spread across environments, connector usage and the things worth attention — rolled up the moment a sync finishes. It is the page you open after an assessment and the one you screenshot for the steering group.
- Totals for apps, flows, solutions, connections and tables
- Environment spread by type, region and Dataverse status
- Attention signals: premium reach, orphaned owners, sprawl
- Live step log while a sync runs, with what each phase found
EnvironmentsEvery environment, including the ones you forgot
Production, sandbox, developer, trial, Teams and default, with region, Dataverse version and Managed Environment status. Open one for a tabbed view of everything inside it.
- Type, region and state for every environment in the tenant
- Dataverse URL and version where a database exists
- Managed Environment flag, so governance gaps are visible
- Per-environment apps, flows, solutions, tables and connections
AppsEvery app, and what it actually touches
Canvas and model-driven apps across every environment, with the owner, the sharing reach, the connectors behind each screen and the SQL databases underneath them. Filter, sort, search and export any slice of it.
- Owner, version, created and modified dates
- Sharing reach — how many people can open or edit it
- Connector and connection bindings, resolved per data source
- SQL databases in use, one per line, per app
App detailOne app, all the way down
Identifiers, owner, sharing, connectors, data sources, the flows it calls and the solution it belongs to. Where the admin API cannot say which server and database a data source points at, the app's own package can be opened to find out.
- Everyone the app is shared with, and at what level
- Each data source with the connector and address behind it
- Flows the app calls, linked where they resolve
- Raw API response panel — exactly what Microsoft returned
FlowsEvery flow, its trigger, and its blast radius
Cloud flows with run state, trigger type and action count, resolved through the connection references they depend on — so you can see what stops working before you switch anything off.
- Run state and trigger type for every flow
- Action count from the flow definition, not an estimate
- Connection references followed through to the connection
- Which apps call the flow, resolved by name across the environment
ConnectionsThe connections nobody remembers making
Who created them, which account they run as, whether they still work, and everything downstream that would break if they went away. A production process running as a named individual is the thing to look for.
- The account each connection authenticates as
- Health status and whether it is shared beyond its owner
- Everything that resolves through it, app by app and flow by flow
- Direct connections told apart from connection references
ConnectorsWhich connectors are in play, and where
Standard, premium and custom connectors ranked by real usage across the tenant. Premium reach is a licensing question and a security one; the same list answers both.
- Usage counts merged from apps, flows and connections
- Licence tier per connector, so exposure stops being a guess
- Custom connectors with their backend host
- Per-connector page listing every object that uses it
SolutionsWhat is packaged, and what is loose
Publisher, prefix, version, managed state and a component-type breakdown of what each solution actually carries. Objects sitting in the default solution are treated as unpackaged, because that is what they are.
- Component counts by type — canvas apps, model-driven apps, flows
- Managed and unmanaged state, publisher and prefix
- Solution membership resolved per object, not guessed from names
- Unsolutioned objects listed as the migration risk they are
DataverseTables, columns and how they are configured
Tables with ownership, auditing and change-tracking flags, down to column type and requirement level. System tables are hidden by default, because a stock environment carries several hundred of them.
- Ownership model, auditing and change tracking per table
- Full column list with type, requirement level and max length
- Row counts where the environment reports them
- Connection references and environment variables alongside
MapThe estate as a graph, not a list
Environments down to apps and flows, then to the connectors and connections beneath them — drilled in place. It answers the question a table cannot, however many columns it grows: what is joined to what.
- Drill from environment to object to dependency without leaving the page
- Shared connections visible as the joins they are
- Users and connections shown per app and per flow
- Derived entirely from the stored assessment — no new calls
MigrationsWhat actually moves, not what somebody listed
Upload the apps you intend to migrate and the plan grows it to the truth: the flows those apps call, the objects sharing their solutions, and the risks in between. Everything it offers is listed before it is added.
- Import by app id and environment name, not display name
- Dependency detection from each app's own data sources
- Broken flow calls told apart from flows merely missing from the project
- Ignore a suggestion and restore it later — the decision is reversible
Solution planningOne solution per thing that has to travel together
Existing solutions on one side, the ones that still have to be built on the other, with the objects each must carry. Default and system solutions are excluded — they already exist on the far side.
- Proposals grouped so objects that must move together do
- Create, update and already-packaged counted in solutions, not objects
- Collapsible rows with filters for each state
- A dry run that reports exactly what creating them would do
Prepared answers for the questions that repeat
Overview, environments, connectors, pre-migration readiness, governance and security. The pre-migration report is tenant-wide: what has to be true before anything moves at all.
- Governance — ownership, sprawl and what nobody is watching
- Security — sharing, privilege and exposure
- Pre-migration — readiness across environments and licensing
- Every report reads the stored assessment, so it opens instantly
ExportsA report you can hand to the board on Friday
The whole assessment or any single object as Excel, PowerPoint or PDF — formatted to be read by people who will never log in. Bulk exports assemble in your browser, so hundreds of files are not a problem.
- Excel workbook and PowerPoint deck of a migration plan
- Solutions worklist: one tab per solution, with a status column
- One file per app and flow, zipped, for a whole selection
- JSON and CSV of the entire assessment for your own tooling
See it on your own tenant
The free plan assesses a single environment for real. No trial countdown, no sample data.