Not every manual process is a good candidate for Power Automate. A frequent, clearly defined task with reliable data is a better fit than a rare case with many exceptions. Start with a pilot whose result you can verify.
Four questions for choosing
| Question | What to look at |
|---|---|
| How often does it happen? | Count cases per week and today's handling time. |
| Are rules and exceptions known? | Map the normal route and the most common deviations. |
| Are data and permissions available? | Check the source system, connector, access and required licence. |
| Who owns the process? | Name the person who handles failures and changes after launch. |
Microsoft's Automation Kit strategy records volume, throughput time and expected value for each process. That is a useful basis for the selection.
Example: document approval
A SharePoint library receives new documents that a specialist must review. First record how often this happens, how rejections are handled and whether a substitute is needed during absences. In the pilot, trigger an approval, log the decision and deliberately test a missing permission. The SharePoint connector documentation shows the supported triggers and limitations.
Measure the result
Compare handling time, failed runs, rework and maintenance effort before and after the pilot. A flow can shift work rather than save it. Microsoft recommends recording value and cost systematically.

