cli-microsoft365: Bug report: 403 forbidden on Flow Export
Description
When running m365 flow export --environment [env] --id [id] I get the error “Error: Request failed with status code 403”
Running the command with --format json does work however.
If I grab the access token and run the command in postman I get same error but with more information:
{“error”:{“code”:“AuthorizationFailed”,“message”:“The client certificate ‘DF4D2C02B7F733BB44849D827A5BC6AFA11B316C’ is not allowed.”}}
Steps to reproduce
Export a flow with
m365 flow export --environment [env] --id [id]
Expected result
Success with a zip exported
Actual result
403
Environment
windows 10 m365 version: v3.4.0 node.js v14.15.4
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 19 (12 by maintainers)
Commits related to this issue
- Fixes bug in exporting flows. Closes #2091 — committed to waldekmastykarz/cli-microsoft365 by waldekmastykarz 3 years ago
@waldekmastykarz We’re seeing the same issues in PnP PowerShell, which is calling exactly the same end points.
thanks @waldekmastykarz I’ve updated and it now works as expected
@m-carter1 we’ve just released a new preview version where this issue should be fixed. Could you please give it a try by running
npm i -g @pnp/cli-microsoft365@next?Once again thank you for reporting the issue! 👏
@waldekmastykarz I am still able to export flows as a zip from the UI
I have the same issue on all flows on my dev tenant 😦