Microsoft Azure Power Automate Management API
65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsCi Cdoauth222 EndpointsREST
For 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.
Use for: I need to create a new flow in an environment, Turn off a running flow, List all flows in my Power Automate environment, Get the definition of a specific flow
Not supported: 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.
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.
Install Jentic One Beta
Connect the Power Automate Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Power Automate Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflow.microsoft.com%2Fflow-microsoft" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflow.microsoft.com%2Fflow-microsoft" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Power Automate Management API.
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
Patterns agents use Power Automate Management API for, with concrete tasks.
★ 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.
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.
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.
List flows in an environment, modify the owners of one flow, and restore a flow that was deleted
Key Endpoints
22 endpoints — the power automate management api manages the automated flows in a microsoft power automate environment and their execution.
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
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
Jentic AI Readiness Score
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.
P
Power Automate Management API
- AI-Aware (B)65/100
82
Foundational Compliance56
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability90
Security74
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
26%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
95%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
90
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
90%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
74
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
74%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Power Automate Management API through Jentic.
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.
GET STARTED