Power Automate

M365-native integration: Connectors for SharePoint, Teams, Outlook and Dataverse make common automations trivial and keep users in the tools they already use Speed to value for cloud flows: Templates, triggers, and approvals (incl. adaptive cards in Teams) to shrink the cycle time from idea to first run. Low-code pro escape hatches: Makers can start visually, then step up to custom connectors, Graph API, and solution ALM when needed Process insights: Process mining/Advisor is helpful for spotting what to automate next.

connectors and flows security and compliance DIY low code no code easy trouble shooting

1. Both cloud and desktop flows have a large number of actions available that can do almost anything required. 2. There is a wealth of information, tutorials, and documentation. Many other services do not have the same level of answers available if a problem presents itself. 3. Easy integration with Microsoft suite. You can connect your email, teams, and many other Microsoft services very easily, and then use them in process flows. 4. If you have any software development knowledge, it's easy to pick up. 5. Flows can be shared easily. 6. It's not expensive for the potential it gives. 7. Support does exist. I contacted Microsoft support, and they did resolve my issue, although it took a few days for them to respond.

Licensing complexity Environment sprawl vs. agility Desktop bot operations

No connectors for legacy systems like OAS application we cannot build big apps using it only simpler to medium apps, we often end up in loading issue and performance failure. cost is also a , when increasing the flows it also comes with cost

1. Licensing is very confusing to set up. Figuring out exactly what is required to support your business case can be confusing with all the different packages and capabilities. Once set up however, it doesn't change unless your needs do. 2. Very quickly you will need more than one unattended machine (if you are using unattended processes). If a process is running on a machine and another process attempts to use it, Power Automate will throw an error immediately. It would be nice if there was a process queue where it would wait for the first to finish, then run the next process in the queue. 3. Every variable is a global variable. This can make large flows difficult to decipher, especially if you did not write it yourself. 4. Co-pilot AI at this time does not work well. It doesn't implement prompts as expected and most of the time it doesn't make a usable product. Scripting actions do have AI that works well. 5. Compared to other platforms, error handling could be improved. 6. Same with UI automation, UI path does a better job in that area.