Power Automate

Every flow, its trigger, and where it writes

A flow’s connector list tells you it talks to SQL. The flow definition tells you it runs a native query against a named production database. Power Insights reads the definition, so the second answer is the one you get.

  • Trigger type and run state for every cloud flow — stopped and suspended flows surface immediately
  • Connectors and connection references, resolved per flow
  • Data targets: the concrete server, database, site or list each step reads from or writes to
  • Action counts, as a usable proxy for how much work re-building a flow would be

Where each step actually writes

The connection carries an identity; the flow definition decides the destination. This table pulls the destination out step by step — here a native SQL query against contoso-sql-prod, database Claims. That is the row that turns “we think it is read-only” into a question somebody has to answer.

Data targets tab of a flow listing each step, its connector, operation and the server and database it points to
Data targets tab of a flow listing each step, its connector, operation and the server and database it points to

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.

Run it on your tenant
In the user manualFinding your way around(opens the Power Insights app in a new tab)

See it on your own tenant.

The free plan assesses a single environment for real — no trial countdown, no sample data.

Read-only · nothing installed · no card required

LogiSam Assistant Guided help & instant answers

Answers come from this website. Privacy policy

↑↓ to navigate ↵ to open