- 01
/plugin marketplace add microsoft/power-platform-skills - 02
/plugin install process-intelligence@power-platform-skills
Compares two groups in Power Automate Process Mining under the same definitions, such as two departments or two periods, and reports their case counts, average duration and waiting time, and the difference between them.
WHEN TO USE
USE FOR
- Compare two departments, regions or other groups.
- Check results before and after a change.
- Compare two time periods.
NOT FOR
- Object-centric processes: analyze-objects handles those.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
Matched cohort comparisons
Use the shared contract and filters/units. Fix the outcome definition/provenance, metric, aggregation, units, timezone and one selector S. Freeze the user's agreed baseline F, separately from current exploratory filters. Reuse metadata versions and exact typed cohort values. Use the investigation method for findings/status.
Ordered trace
- Copy baseline F twice. For attribute cohorts append
{attributeName:A,dataType:T,attributeValues:[X],isInclusive:true}toattributeValueFiltersfor A's cohort value, and the same shape with Y for B. Preserve other agreed baseline conditions; retain rework restrictions only if part of that baseline. Do not leak an exploratory/outcome-only subset into a full-population comparison. Change only the intended cohort condition. If values are unknown, requestget_attribute_values_v2 {S,attributeName:A,itemsPerPage:20,itemsToSkip:0,filterOptions:F}; it returns values, not frequencies. get_process_overall_metrics_v2 {S,filterOptions:F_A}->get_process_overall_metrics_v2 {S,filterOptions:F_B}. Nometrics,groupByor aggregation parameter exists. Use the same returned metric definitions; nativeCaseDuration/CaseWaitingTimeare means.- Only if a grouped explanation is needed and statistics is advertised, make a matched pair:
get_attribute_statistics {S,attributeName:A,filterOptions:F_A,itemsPerPage:5,itemsToSkip:0,metricToSortBy:"TotalDuration",sortOrder:"Descending"}, then exactly the same call with F_B. Do not treat independent top-five pages as a complete aligned population.
Continue relevant value/group pages or matched follow-ups when needed, without fixed call quotas. Stop at sufficient evidence, no new information or a capability/error boundary; no blind sweeps. Do not create views or use two inclusive timeframes in one query as an A/B comparison.
Time and reproducibility
For periods, change only one explicit timeframeFilters start/end pair in each copied F.
Case windows mean Contained, not cases Started/Completed/Intersecting or all events during the period.
If completed-only membership including earlier starts is essential, stop/reframe or route
to derive-metric/a user-confirmed existing matching view. Never invent a date-mode field
or promise unknown end-boundary behavior.
If refresh is reported or reproducibility is at risk, recheck details. Changed PV/PMV invalidates the pair: mark inconclusive, stop or deliberately rerun both, not just the second. Process selection resolves latest; no direct version selector or atomic comparison snapshot exists. Views pin version context but their configuration is mutable/cached.
Report A/B counts, mean metrics, absolute delta and relative change only for a nonzero baseline. Empty cohorts mean insufficient evidence, not zero duration/infinite improvement. State scope/version and unmatched-group coverage; at most five headline rows. Recorded means do not establish closure, equal maturity or complete lifecycles. Report those as unknown unless supported; qualify the comparison, not an assumed causal improvement. Retain baseline/cohort filters, evidence references, status and alternatives. Overlapping groups cannot be added as unique-case totals. Object-centric comparisons belong in analyze-objects, not case-filter fallbacks.
Account or credentials required
3 FOR YOUItems without a tag are required.
- 01Install with the process-intelligence plugin, then run setup
Install it with Microsoft's process-intelligence plugin. It works through the plugin's Process Mining MCP server and shared analysis guides, which come only with the plugin.
- 02Node.js 22 or 24, Azure CLI 2.54+, Process Mining access
Node.js 22 or 24, the Azure CLI 2.54 or later, and an authorised Power Automate Process Mining account and environment. GCC, GCC High, DoD and Mooncake clouds aren't supported yet.
- 03Note Results reach your AI assistant unredacted
Analysis results, which can include personal and business data, are passed unredacted to the AI assistant you use. Check your organisation's rules for that assistant before you connect.
This skill ships inside the Power Platform Skills plugin. Listed package contents include 25 agents, hooks and an MCP server. Installed components and skill versions may vary by AI tool.
Install as a Claude Code plugin
Typed inside the agent's own prompt, not in a terminal. This skill uses files kept elsewhere in its plugin, so install the whole plugin — on its own the skill would be missing them.
The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →