Skip to content

Updates documentation of flow export command. Closes #6418#7244

Open
nanddeepn wants to merge 1 commit intopnp:mainfrom
nanddeepn:issue-6418
Open

Updates documentation of flow export command. Closes #6418#7244
nanddeepn wants to merge 1 commit intopnp:mainfrom
nanddeepn:issue-6418

Conversation

@nanddeepn
Copy link
Copy Markdown
Contributor

Closes #6418

Updated the documentation for the flow export command to clarify the output format when exporting as JSON. The description now specifies that the command exports the ARM template of the specified Power Automate flow as a JSON file, rather than just a generic JSON export.

Copilot AI review requested due to automatic review settings May 7, 2026 09:59
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the CLI documentation for m365 flow export to more precisely describe what the --format json output represents (an ARM template JSON), aligning user expectations with the actual exported artifact.

Changes:

  • Refined the JSON export example description to state that it exports the flow’s ARM template as JSON.

```

Export the specified Power Automate flow as a JSON file
Export the ARM template of the specified Power Automate flow as a JSON file
@milanholemans
Copy link
Copy Markdown
Contributor

Thanks, we'll try to review it soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug report: flow export -f json includes sensitive connector web token (JWT)

3 participants