Audit a Flow's Connector Dependencies
A 4-step recipe with Microsoft Power Automate. We can help you get access.
Recipe · 4 steps
Audit a Flow's Connector Dependencies
Resolve a flow's connector and connection dependencies for migration or licensing review.
- Read the flow to surface the connection references it declares and the definition summary listing the connector each action calls.
- List the connectors registered in the environment so the flow's declared dependencies can be checked against what the environment actually offers.
- Resolve the connector in detail to establish its display name, tier, and whether it is a custom API. Tier is what determines premium licensing, and custom APIs are what break an environment-to-environment migration.
- List the environment's connections so each connection reference the flow declares can be matched to a real, authenticated connection.
What you'll need to have ready
- environmentName: The name of the environment holding the flow.
- flowName: The name or ID of the flow to audit.
- apiName: The name of the connector to resolve in detail (e.g. shared_commondataserviceforapps).
For your developer
Arazzo workflow microsoft-power-automate:connector-dependency-audit, 4 operations: getFlow → listConnectors → getConnector → listConnections. Specs on APIs.io.