canonical: https://jentic.com/apis/flow.microsoft.com/flow-microsoft

# Microsoft Azure Power Automate Management API

The Power Automate Management API manages the automated flows in a Microsoft Power Automate environment and their execution. It lists, creates, reads, updates, and deletes flows, turns them on and off, and cancels or resubmits individual flow runs. It also manages flow owners and run-only users, lists the connectors and connections an environment exposes, and offers admin operations to read and restore flows across environments.

## For AI agents

List, create, update, and delete Power Automate flows, turn them on or off, cancel or resubmit runs, and manage owners, connectors, and connections across environments.

## Scope

Does not author the steps inside a flow, run Power Apps, or build Power BI reports. Use for managing Power Automate flows, their runs, owners, and connections only.

## Capabilities

- Create and update automated flows in a Power Automate environment
- Turn a flow on or off, and cancel or resubmit a flow run
- List the flows in an environment and read a single flow's definition
- Modify flow owners and run-only users
- List the connectors and connections available in an environment
- Restore a deleted flow as an admin

## Use cases

### Agent-Managed Flow Lifecycle

An AI agent connected through Jentic creates a flow in the right environment, reads its definition back to confirm, and turns it on when it is ready to run. Because the management operations are exposed over the API, the agent handles the full create-review-enable loop without a human clicking through the Power Automate portal.

Example prompt: Create a flow in a named environment, read its definition to confirm, and turn the flow on

### Run Control and Recovery

An operations workflow cancels a flow run that is stuck and resubmits a run that failed, keeping automations moving without manual intervention. The run-control operations act on a specific run id, so the workflow targets exactly the execution that needs attention.

Example prompt: Cancel an in-progress run of a flow and resubmit a run that previously failed

### Flow Governance

An admin workflow lists the flows in an environment, modifies their owners and run-only users, and restores a flow that was deleted in error. The admin-scoped operations let governance tooling audit and correct flow ownership across an environment from one integration.

Example prompt: List flows in an environment, modify the owners of one flow, and restore a flow that was deleted

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows` | List flows in an environment |
| POST | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows` | Create a flow |
| GET | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}` | Get a flow |
| PATCH | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}` | Update a flow |
| DELETE | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}` | Delete a flow |
| POST | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}/start` | Turn on a flow |
| POST | `/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}/stop` | Turn off a flow |

## Key resources

- **Flows** — List, create, read, update, delete, and turn flows on or off
- **Runs** — Cancel and resubmit flow runs
- **Connectors and Connections** — List connectors and connections and create a connection
- **Environments** — List the environments your flows belong to
- **Admin** — Read and restore flows and modify their owners as an admin

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/flow.microsoft.com/flow-microsoft/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Power Automate Management API by hand means running the Microsoft OAuth2 authorization-code flow, carrying the token across the long Microsoft.ProcessSimple resource paths, and scoping each call to the right environment. Through Jentic you install once, import Power Automate from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Power Automate puts the environment and flow name in the URL path (`/environments/{environmentName}/flows/{flowName}`), so a rule can pin your agent to one environment or flow and the operations you pick, such as listing and reading flows. You choose the operations it may call, so deleting a flow or turning it off is not included unless you add it.
- **Credential handling:** Your Power Automate OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a flow' or 'turn off a flow', and Jentic returns the matching Power Automate operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **n8n API** — A workflow automation platform whose API manages workflows and executions, like Power Automate manages flows and runs.
- **Pipedream API** — Another automation and integration platform with programmatic control over workflows and runs.
- **Activepieces API** — An open-source automation platform that manages flows and runs in a comparable way to Power Automate.

## FAQ

### What authentication does the Power Automate Management API use?

The Power Automate Management API authenticates with OAuth2 using the authorization-code flow against Microsoft's identity platform per its OpenAPI spec. Through Jentic the OAuth2 credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never reach the agent's context.

### Can I turn a flow on or off with the Power Automate Management API?

Yes. There are dedicated operations to turn a flow on and off, and separate operations to cancel an in-progress run or resubmit a run that failed. Each acts on a specific flow, and the run operations target an individual run id.

### Can I limit what my agent is allowed to do with the Power Automate Management API?

Yes. The environment and flow names sit in the URL path, so write a rule that allows only the read operations for one environment, such as listing flows and reading a flow's definition, so your agent cannot delete flows or turn them off, and every call it makes is logged. Add the create, update, and run-control operations when you want the agent to manage flows too.

### What are the rate limits for the Power Automate Management API?

The OpenAPI spec does not state rate limits for the Power Automate Management API. Check the Microsoft Learn documentation for the Power Platform request limits that apply to your tenant.

### How do I create a flow with the Power Automate Management API through Jentic?

Search Jentic for 'create a Power Automate flow' and it returns the create-flow operation with its input schema; your agent supplies the environment and flow definition and reads the flow back to confirm. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Power Automate MCP server?

You don't need an MCP server to give your agent the Power Automate Management API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the flow, run, and admin operations with scoping and credential isolation applied.