PA is great within the Microsoft 365 ecosystem. I see little value in it outside of that scope. PA has a lot of bugs, and I’ll call them ‘quirks’ because calling them design flaws and/or bad design is mean. 😏 A lot of times, I think it’d be faster for someone to learn JS or Python than it would be to learn PA. In addition to these issues, the issues I have with PA are: The New Designer is absolute hot garbage The team doesn’t fix bugs (It’s MS. So, no surprise there!) Far too many connectors are just plain bad and a nightmare to work with—even for MS apps such as OneDrive or MS Forms. All inputs are converted to strings—even data entered as input on a button press in Instant Flows e.g. if input type is integer, PA automatically converts the input (integer) to text. Incredibly slow development the team makes changes that affect how PA operates at a fundamental level but don’t feel the need to announce the changes or document them in any way e.g. whether string literals need to be in quotations or not. Documentation is poor. Error messages are vague/obtuse and oftentimes not helpful in any way whatsoever. Actions and fields are tied to literal/display names rather than to a GUID/identifier. So, if you change the name of an action (e.g. ‘Compose 4’ to ‘Compose String’), it will break every action that uses dynamic content tied to that action. Working with datetime is a nightmare. Licensing and pricing is ridiculous. Too few basic connectors and too many premium connectors. MS has locked far too many connectors behind premium licenses. Inconsistencies e.g. sometimes strings must be in quotations, other times they don’t need to be in quotations (as PA handles it for the user on the backend). Data type coercion is far too complicated—and considering, as mentioned above, that all data is pulled into PA as text, it makes an already complicated task really fun to deal with. 🙄 No native way to store global/environment variables (can use a SP list as a workaround). No ability to group flows in folders. This makes the My Flows UI a PITA to navigate through. If you have actions contained within a control (Apply to Each, Do Until, Switch, etc) and the flow fails, you cannot see the output of any of the actions contained within the control. The way PA handles And/Or logic with the Condition action is unintuitive and just plain bad design Native/Built-in Approval process is awful No ability to enter data/receive input once a flow has started (other than Yes/No or using adaptive cards which come with a whole list of issues themselves). Also, input options for Instant Flows are extremely limited. Anything more than maybe 10-20 actions and working in the designer/UI becomes a chore. It’s slow, unresponsive, and glitches far too often. For very basic/quick automations e.g. ‘When a new list item is created, send email’ or ‘When a file is added to a document library, copy file, and move copy to a different document library’ PA is fine. There is an inverse relationship between complexity and PA’s effectiveness and utility whereas complexity increases, PA’s effectiveness and utility decreases. More on reddit.com

Automating Microsoft SSO account change programmatically. (self.rpa) ... Post a comment! ... Use of this site constitutes acceptance of our User Agreement and Privacy Policy. © 2024 reddit inc. More on old.reddit.com

I would use any other vendor other than PowerAutomate for starters. More on reddit.com

You will need a power plan that can handle hosting virtual machines if you want to do RPA on it at least. More on reddit.com