Bug report: 403 forbidden on Flow Export
See original GitHub issueDescription
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
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:19 (12 by maintainers)
Top Results From Across the Web
When a new email arrives - error 403
403 errors are generally caused by unauthorized resource or forbidden resource. Double check that you and the connections you are using in flow ......
Read more >How to Fix a 403 Forbidden Error on Your WordPress Site
The 403 Forbidden error means that your server is working, but you no longer have permission to view all or some of your...
Read more >Re: Export API Error 403 - Microsoft Power BI Community
Export API Error 403 ... The Report does export if we remove the configuration for RLS. The report does not live in the...
Read more >SharePoint Online: Fix "The remote server returned an error
Follow this checklist to resolve Executequery 403 forbidden error in SharePoint Online PowerShell: You may have provided the credentials of another tenant, ...
Read more >How to fix 'Access denied - error 403' in a SharePoint-based flow
In many cases, an error code of 403 appears in a flow fail because of an authentication error. If you have this type...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@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