🔎 ValueLens

Both play here in the page — no download.

Demo — what the dashboard measures, page by page (1m 49s)

A tour of the pages and how the value model fits together.

Setup guide — getting your own data in, every source, start to finish (7m 07s)

Every data source (Purview audit, Entra, M365 usage), the permissions each needs, the parameters you fill in, and the Fabric path in full: PySpark notebooks instead of scripts, the Graph permissions per notebook, the ingester-then-processor run order, and the same notebooks and template running on Databricks, Synapse or Azure SQL.

👉 New here? Start with 4. Local CSV

It ships with a fabricated sample dataset that fills the whole dashboard. Open the template, point it at the sample CSVs, done — no tenant, no exports, no setup. Roughly two minutes, and it tells you whether the numbers are worth wiring up before you wire anything up.

Same dashboard, a choice of data pathways. Path 1, Fabric, is the recommended route. It includes an installer that sets the whole path up for you, and the Fabric App: a preview that runs the dashboard as a web app in your Fabric workspace, on top of the model you publish from any of paths 1–4. Path 2 is a preview for Power Automate and Dataverse, exercised end-to-end on a bounded demo interval. Paths 3 and 4 need no Fabric capacity.

Quick decision: Fabric capacity → 1 · Dataverse-centric → 2 · Power BI Pro only → 3 · no tenant access → 4 · want a web app on top of any of them → 1. Fabric/Fabric App.

Not sure? Start with path 4. It takes minutes and tells you whether the numbers are worth automating — before you set up any automation. Move to 3 or 1 when you want it hands-off.

The former Copilot Studio agent / topic / CSAT add-on is retained as archived reference, not a recommended active deployment. For agent transcripts in Dataverse, use the Dataverse companion repo ↗, which reads them natively — no Fabric or SharePoint needed.

💳 Want credit consumption and cost too? Paths 1–4 each have an optional Add Credit Consumption/ add-on: the separate Consumption Central report for Cowork / Work IQ, Copilot Studio, GitHub Copilot and Azure AI Foundry spend. Start with the Local CSV add-on and its sample data. Once it's published, the Fabric App's Consumption page reads it too.

Each path folder has its own README with the exact, step‑by‑step setup. This page is just the map.

README.md  ·  CHANGELOG.md  ·  LICENSE  ·  Images/
CONTRIBUTING.md  ·  CODE_OF_CONDUCT.md  ·  SECURITY.md  ·  SUPPORT.md

docs/              DATA-DICTIONARY.md  ·  PERMISSIONS.md   ← cross-path reference
1. Fabric/         Fabric.pbit  ·  docs/  ·  flows/  ·  notebooks/  ·  pipelines/
     installer/         `npx valuelens-install` — sets up the whole Fabric path for you
     Fabric App/        web app (React + Vite) over a published model  ·  deployed with `npx rayfin up`
     docs/              Fabric-only notes: ingestion, storage modes, troubleshooting, checker pack
     archive/extended/  archived Copilot Studio add-on reference (core notebook mirrors still synchronized)
     archive/flows/     archived cost-consumption flows and guides, not active setup
2. Power Automate + Dataverse/  Power Automate + Dataverse.pbit  ·  scripts/  ·  source-map.json
3. SharePoint/     SharePoint.pbit  ·  scripts/  ·  azure-container/
4. Local CSV/      Local CSV.pbit  ·  sample-data/   ← start here, fabricated demo dataset
*/Add Credit Consumption/  optional Consumption Central cost report, one per path
archive/            superseded versions — kept for reference, not maintained
tests/             offline pytest regressions, run in CI by .github/workflows/tests.yml

Dataverse path → companion repo: microsoft/AgentEvaluator-for-Copilot-Studio

• Quantified value — hours saved and dollar‑equivalent assisted value, grounded in research‑sourced time baselines.
• Value by function — Sales, HR, IT, Legal, Finance, Marketing, Customer Service, with task‑level attribution.
• Habit formation — Beginner → Developing → Habitual → Power, from each person's active days in the last complete month.
• Business case — projected annual value, ROI multiple, and licence investment net.

How: every interaction → classified into an AI Task → mapped to a research‑sourced time baseline → summed to Hours Saved → × hourly rate = Assisted Value. The methodology explains every step, page by page.

Availability varies by deployment path. Use the path README for the maintained source list and exact setup.

Optional sources can be left out — the dashboard works fine without them. On Fabric, the Enable_* toggles default to Include and a table that hasn't been landed loads empty; on the other paths, leave the Agent 365 or Feedback File parameter blank. The exact export + connect steps live in the path README you choose above.

Maintained page lists live in the path READMEs:

• 1. Fabric/README.md
• 1. Fabric/Fabric App/README.md
• 2. Power Automate + Dataverse/README.md
• 3. SharePoint/README.md
• 4. Local CSV/README.md

Archived Studio page reference (not an active deployment): 1. Fabric/archive/extended/Fabric + Copilot Studio/README.md.

Every path ships the same 15-page report (activation, adoption, habit formation, agent registry, task breakdown, estimated value, model fit, Cowork fit, Cowork and licence readiness, user feedback, leaderboard, trend heatmap and two appendices); only the data connection differs. Studio detail is archived.

Built by the Microsoft Copilot Growth & ROI practice, building on the structure of the community AI‑in‑One Dashboard. Licensed MIT — see LICENSE.

Running the tests. The offline regression suite needs only Python 3.12 and pytest:

python -m pip install pytest
python -m pytest tests -q

It runs on every pull request via .github/workflows/tests.yml. No tenant, credentials or Spark cluster required — the suite is deliberately offline.