There was an error while loading. Please reload this page.
Copilot adoption: document the App Insights telemetry and monitoring queries New section 9 covering the CopilotAdoptionAnalysis event: its dimensions and measurements, why per-step durations are measurements rather than dimensions, and why one event is emitted per analysis rather than per request. Includes ready-made Kusto queries for the three questions an operator has - is any report degrading, how slow is it and which step owns it, is it approaching the timeout - and two suggested alert rules. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 87347b97-407c-4dbe-bae5-e8880d0fc77d
Copilot adoption: record the measured scale finding and re-scope rollups Benchmarked on a synthetic 200k-user / 12M-interaction tenant. The dominant cost was not the fact scan the earlier audit assumed - it was asking for three COUNT(DISTINCT) in one GROUP BY, which forces SQL Server to spool the input and process each distinct separately, and which pushed the query past the 90s command timeout so the report degraded to a warning on a large tenant. 28-day window went from 114.7M logical reads and 281s to 772k and 73s; 365-day from 115.2M and 303s to 819k and 135s. Correctness gated first: 33,999 rows each side, zero differing. Rollups are re-scoped rather than dropped: still the answer for the widest windows and the prerequisite for credit analytics, but no longer the first fix. No customer data was used or recorded. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 87347b97-407c-4dbe-bae5-e8880d0fc77d
Copilot adoption: say licence rather than seat throughout the docs Matches the product change: seat is licensing shorthand that does not travel, and licence is the word already on the customer invoice and in the admin centre. 44 lines across the spec and the user guide, including the Reclaimable licences tile name and the FAQ. Two headings reworded rather than swapped, because a straight substitution made them contradict themselves - a Copilot-branded SKU is what is not counted as a Copilot licence. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 87347b97-407c-4dbe-bae5-e8880d0fc77d
Copilot adoption: record why the last funnel step is not a loss Section 5 now states that the funnel's final step reads 'N not yet Champions' in neutral grey rather than red 'lost here', and why: everyone who reaches Habitual has formed a habit by the tool's own definition (section 3.2), and the action catalogue marks Established as needing no action. Flagging them as lost would contradict our own advice and aim enablement budget at the people already succeeding. Written down so a future change does not quietly revert it. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 87347b97-407c-4dbe-bae5-e8880d0fc77d
Copilot adoption: document the window definition and the demo-data scenario Records two things that were previously only true in code. Section 3.1 now states that 'last N days' means exactly N distinct calendar dates and explains why the window starts N-1 days back: starting N days back spans N+1 dates, so the numerator could exceed the window the frequency target divides by. New section 8 documents the FakeDataGen adoption scenario - what it plants, why random scatter makes the tool look broken, and the fact that persona targets are re-scored through the real scoring code on every run so the demo data cannot silently stop matching this page. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 87347b97-407c-4dbe-bae5-e8880d0fc77d
Copilot adoption: correct PAX name and note AI-in-One's own licensing caveat Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b
Copilot adoption: overview sections, renamed actions, three new design principles Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b
Add a Copilot Adoption user guide The existing page is a specification - design principles, metric definitions and a review checklist for people changing the tool. It does not tell an admin how to actually use it. Adds a task-oriented guide: prerequisites and what each missing import costs you, a first-fifteen-minutes walkthrough, a tour of the six tabs, and three worked scenarios (a reclaim review before renewal, planning an enablement programme, and proving a programme worked with before/after snapshots). Plus a table of how to read each chart with its common misreading, a glossary of every term the tool uses, what each warning means and what to do about it, and an FAQ covering the questions the numbers actually provoke - why adoption can be 100% while habit is near zero, why figures differ from the M365 admin centre, and why a Copilot-branded SKU may not count as a seat. Cross-linked from the specification and the sidebar. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b
Copilot Adoption spec: replace the backlog with a researched gap analysis Assessed against Microsoft's 2026 tooling (admin-centre Copilot dashboard, Copilot Control System measurement pillar, Viva Business Impact Report, the free Analytics Hub templates) and the commercial tools in this space. Records the strategic shift - 'who is using Copilot' is now a solved native capability, and the frontier is credit/consumption cost, defensible value, and readiness grounded in real data exposure - then tiers the gaps by whether the data is already imported. Most of Tier 1 is surfacing signal we already store (per-interaction credit estimates, AI model, sensitivity labels on accessed resources) rather than new imports. Also records what we deliberately reject and why: AI-generated narrative summaries and named-user fluency leaderboards both breach stated principles, and saying so here stops them being re-proposed each time Microsoft ships one. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b
Copilot Adoption spec: Excel export and the visual vocabulary Documents the twelve-sheet Excel export and its point-in-time snapshot purpose, why it is written with no third-party dependency, and why the Report sheet has to carry the thresholds for two snapshots to be comparable. Records the visual vocabulary against AI-in-One (gauges and the radar profile have no equivalent there), and adds review-checklist items for chart-type choice and for keeping the page and the workbook in step. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b
Copilot Adoption spec: record capability coverage against AI-in-One Adds a per-page comparison table against microsoft/AI-in-One-Dashboard so a future change cannot silently regress a capability, documents the agents and unlicensed-usage screens, and states the two things deliberately not copied (the AI-generated narrative page, and a per-user leaderboard naming individuals). Refreshes the known-gaps list. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b
Add the Copilot Adoption Tool specification page Describes what the Copilot Adoption area is for, its design principles (every assertion explains itself; say a thing once; never show a percentage without its counts; never claim a metric the data cannot support), every metric definition and formula, the data sources with their caveats, and a feature-review checklist to run against any future change to the tool. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 492674d8-e6a9-4e73-a224-c598ee04110b