Analytics is evidence, not authority

The dashboard is doing its job

Microsoft's public tools answer useful questions. The Microsoft AI Decision Framework and Agent Platform Advisor help people choose where work or an agent should start. Analytics Hub collects standalone tools for adoption, readiness, cost, and impact. CreditUsage attributes consumption, while ValueLens turns observed interactions into a modeled value story. These are useful answers. The mistake is asking them to prove a different kind of fact. [1] [2] [4] [3] [11] [12]

Four useful questions Microsoft tools can help answer

A boundary does not make the metric less useful. It makes the metric safe to combine with other evidence. AI-in-One, for example, says that Purview audit logs can illuminate Copilot and agent interactions but are not the sole source of truth for licensing or full-fidelity activity. That is good evidence discipline: name what a source can establish, then stop. [10]

Consumption and billing are separate too. Microsoft's Consumption Dashboard says its credit data is for reference and directs operators to the relevant billing system for official charges. Copilot Studio gives an even simpler example: a proactive greeting can count as a billed Copilot Credit when the user never replies, while analytics classifies that same session as unengaged. A billed event does not establish engagement, and neither fact establishes a successful business outcome. [5] [6]

Seven questions complete the operating loop

An operator needs more than a scorecard. For one important agent, answer these seven questions with named sources and preserve unknown answers as unknown.

Use one path through the review: inventory → ownership → capability → next decision → authority → execution → fresh state.

Microsoft already provides useful pieces of this review in different places. The Microsoft 365 admin center describes a centralized inventory view and identifies ownerless agents. Its role guidance separately says that several roles may view agent information while only selected roles may perform governance actions such as approving requests or assigning ownership. The separation is the point: visibility, ownership evidence, and governance authority are related facts, not one permission. [8] [9]

Cost was real. Success was not established

In one reduced internal example—not Microsoft product documentation—Celest recorded about 602.41 Copilot Credits for an overall task. During a later create phase, no final tool result was tied to that phase. A separate read-only Dataverse query found zero intended lead rows and zero intended opportunity rows. The honest conclusion was narrow: the cost was final, the execution attempt was uncertain, and fresh readback verified no resulting rows at observation time.

The example does not prove that cost data is unreliable. It proves that cost and outcome answer different questions. A useful cost observation should name the task, source, period, attribution, and whether the amount is final or still accruing. A useful outcome claim still needs execution evidence and, for consequential work, fresh state from the system that owns the result.

Use dashboards as sources, not rivals

An agent control plane should not rebuild every adoption chart or ROI model. It should retain the useful result with its source, observation time, scope, method, and limitations, then join that evidence to the same agent record used for ownership, capability, findings, and decisions.

• Collect the smallest useful observation and record where it came from.
• Join it to an agent only when the identifiers and environment match with stated confidence.
• Keep unavailable, unknown, false, and zero as different states.
• Let a reviewed rule produce a finding; do not let a metric produce a mutation.
• Record the authority decision separately from the credential used at runtime.
• After execution, read the intended state again from the system that owns it.

The resulting loop is simple to say even when the estate is complicated: observe, understand, decide, hand off, execute, verify, and retain a receipt. The dashboard remains valuable because its claim stays intact instead of being stretched into authority it never had.

Start with one agent

Choose one agent with meaningful activity, spend, risk, or business importance. Put the seven questions on one page. Link each answer to its source, mark every gap as unknown, and choose one next decision that a named person can make. If work follows, verify the result in the business system before calling it complete.

What Celest proves today

Celest can collect, join, and explain read-only evidence about an agent estate while keeping findings, proposed work, human decisions, execution observations, and receipts distinct. Today, the Microsoft-facing Estate Review does not perform Microsoft lifecycle changes or independently verify their resulting state in production.

That boundary is why the seven questions matter now. They are useful before automated execution exists, and they remain necessary after execution becomes possible. More autonomy increases the value of evidence, authority, and verification; it does not collapse them.

Limitations

• The public repositories cited here do not represent every Microsoft product capability, private preview, commercial service, or future roadmap item.
• An analytics source can be incomplete, delayed, modeled, or joined incorrectly; record its source health and method before using it in a decision.
• Modeled ROI is useful for planning when its assumptions are visible. It is not task-level outcome verification.
• The Customer Zero observation is one source-minimized internal experiment, not customer validation or a statistical claim about Cowork tasks.
• Celest's current Microsoft-facing Estate Review remains read-only; provider execution and fresh-state lifecycle reconciliation are not claimed as current commercial capabilities.

Sources

External claims on this page use the primary sources below. Celest-authored definitions and design criteria are identified as our operating model.

1. 1
   Microsoft AI Decision Framework

   Microsoft · Accessed 2026-07-29. A public methodology for choosing among Microsoft AI technologies using business, experience, technology, lifecycle, and governance considerations.

2. 2
   Agent Platform Advisor

   Microsoft · Accessed 2026-07-29. A static advisor that routes users among Microsoft work surfaces and recommends an agent-building platform from stated needs.

3. 3
   Analytics Hub

   Microsoft · Accessed 2026-07-29. A collection of standalone tools for Copilot adoption, readiness, usage, cost, and business-impact analysis across several source systems.

4. 4
   Copilot Control System measurement and reporting

   Microsoft Learn · Accessed 2026-07-29. Microsoft reporting capabilities for understanding Copilot and agent adoption, usage trends, organizational impact, and value.

5. 5
   Consumption Dashboard

   Microsoft Learn · Accessed 2026-07-29. Credit-consumption monitoring across agents, services, teams, and users; the documentation labels dashboard credit data as reference-only and directs readers to billing systems for official charges.

6. 6
   FAQ for Copilot Studio billing and licensing

   Microsoft Learn · Accessed 2026-07-29. Billing and engagement are distinct: a proactive greeting can be billed even when the user does not reply and analytics marks the conversation unengaged.

7. 7
   Copilot Business Impact report

   Microsoft Learn · Accessed 2026-07-29. A report that relates Copilot usage to customer-supplied business outcome measures and documents omitted variables, statistical limitations, and estimated assisted value.

8. 8
   Agent Registry in Microsoft 365 admin center

   Microsoft Learn · Accessed 2026-07-29. A centralized agent inventory and governance view that includes ownership gaps, platform, channel, source, risk, and management actions.

9. 9
   Agent management roles and permissions in Microsoft 365 admin center

   Microsoft Learn · Accessed 2026-07-29. A role boundary that distinguishes viewing agent information from governance actions such as approving requests, assigning ownership, and changing configuration.

10. 10
    AI-in-One Dashboard

    Microsoft · Accessed 2026-07-29. A Power BI adoption dashboard whose documentation states its preprocessing requirements and warns that Purview audit logs are not the sole source of truth for licensing or full-fidelity activity.

11. 11
    Credit Usage and Chargebacks

    Microsoft · Accessed 2026-07-29. A Power BI report that joins a Copilot credit-consumption export with Entra organization data to analyze utilization, attribution, chargeback, and capacity risk.

12. 12
    ValueLens for Microsoft Copilot

    Microsoft · Accessed 2026-07-29. An experimental analytics template that maps interactions to research-sourced task baselines, hours saved, assisted value, adoption, cost, and governance views while documenting source limitations.