Closed mix1981 closed 1 year ago
Ok, I've solved it - the problem was with EnvironmentId on configuration tab - when MS Flow changed to Power Automate, EnvorinmentID starts with "Default-XXX" and whole this string is the EnvirnmentID, including "Default-" word.
I got error when I click Connect on Connect to API flow - no flows are getting listed, just "Firbidden" error appears. I think I've added all necessary permissions to the application - even more than necessary and listed in your blog (https://linked365.blog/2020/10/14/flow-to-visio-xrmtoolbox-addon/#connect-to-power-automate-api). The only difference is that currently permission group is called PowerAutomate instead FlowService, but necessary permission (Flows.Read.All) is granted.