Microsoft Power Automate · Arazzo Workflow

Microsoft Power Automate Manage Flow Owners

Version 1.0.0

Read a flow's current owners, add or remove owners, and verify the new roster.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AutomationBusiness ProcessIntegrationLow-CodeMicrosoftPower PlatformRPAWorkflowsArazzoWorkflows

Provider

microsoft-power-automate

Workflows

manage-flow-owners
Modify the owner list of a flow and verify the resulting roster.
Reads the flow and its existing owners, submits the requested owner additions and removals, then re-reads the owners so the effective roster is confirmed rather than assumed.
4 steps inputs: environmentName, flowName, ownersToAdd, ownersToRemove outputs: flowDisplayName, ownersAfter, ownersBefore
1
confirmFlow
Read the flow to confirm it exists and to capture its display name and creator for the ownership audit record.
2
readCurrentOwners
List the flow's current owners so the roster before the change is captured and the requested modification can be reconciled against it.
3
modifyOwners
Apply the owner additions and removals in a single request so the roster never passes through an intermediate state with no owner.
4
verifyOwners
Re-read the owner list and assert at least one owner remains, catching the dangerous case where a removal leaves the flow orphaned.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Microsoft Power Automate Manage Flow Owners
  summary: Read a flow's current owners, add or remove owners, and verify the new roster.
  description: >-
    Flow ownership is the access-control surface of Power Automate, and the most
    common cause of an orphaned business-critical flow is a sole owner who has
    left. This workflow confirms the flow exists, reads the current owner roster,
    applies an add and remove set, and reads the roster back to prove the change
    landed. Every step spells out its request inline so the flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: flowPermissionsApi
  url: ../openapi/microsoft-power-automate-flow-permissions-api-openapi.yml
  type: openapi
- name: flowsApi
  url: ../openapi/microsoft-power-automate-flows-api-openapi.yml
  type: openapi
workflows:
- workflowId: manage-flow-owners
  summary: Modify the owner list of a flow and verify the resulting roster.
  description: >-
    Reads the flow and its existing owners, submits the requested owner
    additions and removals, then re-reads the owners so the effective roster is
    confirmed rather than assumed.
  inputs:
    type: object
    required:
    - environmentName
    - flowName
    properties:
      environmentName:
        type: string
        description: The name of the environment holding the flow.
      flowName:
        type: string
        description: The name or ID of the flow whose owners are being managed.
      ownersToAdd:
        type: array
        description: >-
          Principals to add as owners, each an object with an id (the principal
          object ID) and a type.
        items:
          type: object
      ownersToRemove:
        type: array
        description: >-
          Principals to remove as owners, each an object with an id (the
          principal object ID) and a type.
        items:
          type: object
  steps:
  - stepId: confirmFlow
    description: >-
      Read the flow to confirm it exists and to capture its display name and
      creator for the ownership audit record.
    operationId: getFlow
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    - name: flowName
      in: path
      value: $inputs.flowName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      displayName: $response.body#/properties/displayName
      creator: $response.body#/properties/creator
  - stepId: readCurrentOwners
    description: >-
      List the flow's current owners so the roster before the change is captured
      and the requested modification can be reconciled against it.
    operationId: listFlowOwners
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    - name: flowName
      in: path
      value: $inputs.flowName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      ownersBefore: $response.body#/value
      firstOwnerRole: $response.body#/value/0/properties/roleName
  - stepId: modifyOwners
    description: >-
      Apply the owner additions and removals in a single request so the roster
      never passes through an intermediate state with no owner.
    operationId: modifyFlowOwners
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    - name: flowName
      in: path
      value: $inputs.flowName
    requestBody:
      contentType: application/json
      payload:
        add: $inputs.ownersToAdd
        remove: $inputs.ownersToRemove
    successCriteria:
    - condition: $statusCode == 200
  - stepId: verifyOwners
    description: >-
      Re-read the owner list and assert at least one owner remains, catching the
      dangerous case where a removal leaves the flow orphaned.
    operationId: listFlowOwners
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    - name: flowName
      in: path
      value: $inputs.flowName
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.value.length > 0
      type: jsonpath
    outputs:
      ownersAfter: $response.body#/value
  outputs:
    flowDisplayName: $steps.confirmFlow.outputs.displayName
    ownersBefore: $steps.readCurrentOwners.outputs.ownersBefore
    ownersAfter: $steps.verifyOwners.outputs.ownersAfter

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/microsoft-power-automate-manage-flow-owners-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.