How CHAOS decides
CHAOS turns raw Microsoft 365 and Entra ID data into explicit license picks per persona. Multiple compliant SKU paths stay in scope; the chosen route is justified and rejected alternatives are documented—that is the Why layer.
Decision logic
Rules describe which signals apply to which personas (desktop Office need, elevated security features, specialist apps such as Project/Visio, and more). Models translate those signals into candidate SKUs—conflicts between lowest price and minimum capability surface before recommendations harden.
- Persona- and group-based modelling instead of blanket “one bundle everywhere” logic
- Add-ons compared against stepping up bundles when that is genuinely cheaper
- Clear precedence when overlapping rules activate at the same time
Why layer
Every emitted decision reads in plain language: which connector, which rule revision, which alternatives were screened out and why that matters for finance versus engineering versus audit. Fewer clarification loops during annual reconciliation and smoother internal scrutiny—without forcing licensing SMEs to rebuild documentation manually each quarter.
- Finance- and auditor-friendly exports grounded in factual metadata
- Less interpretive ambiguity in Microsoft-facing or joint audits
- Change-adverse functions can mandate approvals anchored in the documented graph
Simulation
Before automation snaps into production you can replay scenarios—what shifts if Frontline adopts F3 more aggressively? What breaks if Project is gated behind a dynamic Azure AD group instead of manual assignment? The simulator reuses identical logic to live operations so numbers stay coherent.
- Sensitivity to assumptions surfaced early
- Business alignment anchored in concrete deltas, not anecdotes
- Rollout sequencing in phased waves backed by reproducible KPIs
CHAOS — signals, rules, decision: traceable in one graph.
From the field
Scenario
IT wants to stop “gut-feel” licensing: usage signals, group memberships, and role profiles should converge into a clear SKU recommendation, including documented exclusions.
Why (evidence layer)
The rule engine and decision graph show which rule fired and which options were deliberately discarded. That transparency shortens billing and audit Q&A—fed automatically from tenant signals.
Before/after in EUR per month (run-rate). Annual savings = difference × 12. Figures reflect typical mid-market profiles consolidated from completed optimisation programmes (anonymised, rounded); your organisation will differ by inventory and governance.
Total before (monthly)
€ 128,000
Total after (monthly)
€ 99,840
Savings / year
€ 337,920
Savings
22%
Run-rate cost: before vs. after
License mix by SKU (after)
Split by Microsoft 365 / online SKUs (after — readable)
Microsoft 365 E3
€ 37,939 · 38.0%
Microsoft 365 F3
€ 21,965 · 22.0%
Microsoft 365 E5
€ 11,981 · 12.0%
Project Plan 3
€ 9,984 · 10.0%
Visio Plan 2
€ 7,987 · 8.0%
Microsoft Defender for Office 365 (Plan 1)
€ 9,984 · 10.0%
Consolidated metrics from comparable customer programmes (anonymised under GDPR, rounded). This is how finance and IT teams usually read run-rate before a live tenant connect. Your authoritative view is built in the demo with your tenant.
| Total before (monthly) | 128000 |
|---|---|
| Total after (monthly) | 99840 |
| Savings / year | 337920 |