100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
Programming

Process Mining

Use Process Advisor to record real user activity, reconstruct the as-is version of a business process, and identify the best candidates for automation.

RPA & AIAdvanced9 min readJul 10, 2026
Analogies

Process Mining and Process Advisor in Power Automate

Process mining flips the usual automation approach around: instead of interviewing stakeholders to guess how a process works and then automating that guess, Process Advisor (Power Automate's built-in process mining tool) records the actual clicks, application switches, and timestamps real users generate while doing their job, and reconstructs the true, as-is process from that raw activity data. Each recorded action becomes an event in an event log with three essential fields, a case ID identifying which process instance it belongs to (such as a specific purchase order number), an activity name, and a timestamp, and Process Advisor stitches these events together per case to build a process graph showing every path the work actually took, including the exceptions and rework loops that a whiteboard diagram from a stakeholder interview would never capture. Because the data comes from an unattended background recorder rather than self-reported descriptions, process mining routinely surfaces process variants nobody in the organization was consciously aware of, including workarounds staff invented to cope with a broken step.

🏏

Cricket analogy: Like Hawk-Eye reconstructing a ball's actual trajectory from raw tracking data rather than an umpire's memory of where it pitched, Process Advisor reconstructs the real process from recorded events rather than a stakeholder's recollection.

Analyzing Bottlenecks and Process Variants

Once the event log is built, Process Advisor's process graph shows every distinct path (variant) the case data followed between activities, with the thickness of each connecting line proportional to how many cases took that path, so the single most common variant is visually obvious, and rare, expensive detours stand out immediately. Clicking any activity or connection surfaces statistics like average and median duration, case count, and a distribution histogram, which is how you distinguish a genuine bottleneck (an activity that's slow for almost every case) from an outlier skew (an activity that's fast for most cases but occasionally stalls for days on a handful of them, often due to a specific exception condition worth investigating separately). Process Advisor also supports root-cause style filtering, letting you isolate cases by an attribute like requester department or order value to check whether the bottleneck is universal or concentrated in one segment of the business, which changes whether the fix should be a broad automation or a targeted policy change for that segment.

🏏

Cricket analogy: Like a bowling heatmap showing which line and length gets hit for boundaries most often, the process graph's line thickness shows which path through a process the most cases actually follow.

From Process Insights to Automation

Process Advisor's value isn't the analysis alone; it's meant to feed directly into deciding what to automate next, and the tool's built-in Automation Opportunities panel scores activities by a combination of frequency, duration, and how repetitive/rule-based the recorded steps looked, ranking candidates so teams don't have to guess which process to attack first. A high-frequency, high-duration, low-variability activity (say, copying data from an email attachment into an ERP system) is typically the strongest RPA candidate because the volume justifies the build effort and the low variability means a desktop flow can reliably replicate it, whereas a low-frequency, highly variable activity is usually a poor automation candidate no matter how painful it feels anecdotally. Once a target activity is chosen, the underlying recorded task capture (the literal sequence of clicks captured during process mining recording) can often be exported directly into the Power Automate Desktop designer as a starting point for the desktop flow, shortcutting the build phase since the automation team isn't starting from a blank recording.

🏏

Cricket analogy: Like a franchise's data team ranking which fielding drill improvement yields the biggest run-saving impact per hour of practice, the Automation Opportunities panel ranks which process activity yields the biggest ROI per automation effort.

text
// Simplified event log record structure used by Process Advisor
// (one row per recorded activity instance)
{
  "caseId": "PO-104822",
  "activity": "Approve Purchase Order",
  "timestamp": "2026-06-14T09:12:33Z",
  "resource": "finance.approver@contoso.com",
  "attributes": {
    "department": "Marketing",
    "orderValue": 4200.00
  }
}

// Case: all rows sharing caseId 'PO-104822' form one process instance
// stitched in timestamp order to build that case's path through the graph

Process Advisor recorders run locally during a data collection period, capturing UI events without needing an API into the target application, which is why it's commonly used as the discovery step before building a desktop flow: it tells you exactly which clicks a future RPA flow would need to replicate.

Recording real employee activity for process mining raises privacy and change-management concerns; scope recorders to specific business processes and machines rather than blanket-recording everything, communicate clearly what is and isn't captured, and review recordings with employee representatives or HR/legal before rolling out an organization-wide process mining initiative.

  • Process Advisor records real user activity to reconstruct the actual as-is process, rather than relying on stakeholder interviews.
  • An event log has a case ID, activity name, and timestamp per event; events sharing a case ID are stitched into one process instance.
  • The process graph's line thickness shows how many cases followed each path, surfacing the most common route and rare detours.
  • Duration histograms distinguish a universal bottleneck from an outlier skew affecting only a handful of cases.
  • Filtering cases by attribute (department, order value) reveals whether a bottleneck is systemic or concentrated in one segment.
  • The Automation Opportunities panel ranks candidates by frequency, duration, and variability to prioritize what to automate first.
  • High-frequency, low-variability activities are the strongest RPA candidates; low-frequency, highly variable ones usually aren't worth automating.

Practice what you learned

Was this page helpful?

Topics covered

#Programming#PowerAutomateStudyNotes#ProcessMining#Process#Mining#Advisor#Power#StudyNotes#SkillVeris#ExamPrep