True Adoption: Copilot Prompt Counts Show Zero, or Admin Consent Is Requested

Purpose

In True Adoption, two Copilot measurements can sit stubbornly at zero while everything else reports normally, and the Adoption Center may ask for admin consent before it will finish configuring. Both come back to one Microsoft Graph permission that has to be granted in your tenant.

This article covers which permission, which application it belongs to, what is and is not affected while it is missing, and the step after consent that most people miss.

What you will see

Either or both of:

A consent banner in the Adoption Center, along the lines of Admin consent required to complete configuration — Copilot measurement items selected require the AiEnterpriseInteraction.Read.All permission to report on interactions. Selecting a Copilot measurement that depends on the permission is what triggers it.

Two metrics reading zero in Copilot Adoption and Copilot ROI:

• Prompts submitted for Copilot Chat (work)
• Prompts submitted for Copilot Chat (web)

What is actually affected — and what is not

This is worth knowing before you escalate, because the scope is narrower than it looks.

Without the permission, all other information is still collected from the audit log as normal. Your personas, scores and other adoption metrics are unaffected. It is specifically the two Copilot Chat prompt counts above that cannot be populated, because they come from a Graph call that the permission gates.

So a persona that is entirely blank is probably not this problem. Two fields at zero, with everything around them working, is.

The permission, and which application it belongs to

The permission is AiEnterpriseInteraction.Read.All.

It must be consented on the CloudScape application. This is the part that costs people the most time, because your tenant contains several ENow applications and the name does not obviously connect to True Adoption.

It is not the Report Gatherer application. That application previously carried this permission and it was deliberately removed. Consenting there will not resolve the problem and will not produce an error to tell you so — it simply will not work. If you have already consented something and nothing changed, check which application you consented before assuming the consent itself failed.

Granting the permission requires an account authorised to consent on behalf of the organisation — in practice a Global Administrator.

Granting it

The Adoption Center has its own consent page and will redirect you to it when a required permission is missing. Use the Consent control in the banner rather than hunting for the application in the Entra portal — it takes you to the right place and grants the right permission against the right application, which removes the main opportunity for error.

The step most people miss: historical data does not backfill

This is the important one.

Once consent is granted, collection starts working from that point forward. The days that were collected without the permission keep their zeros. Those values are not recalculated on the next cycle, and waiting will not fill them in — the underlying Graph calls for those days already failed and are not retried on their own.

If you need the historical figures, raise a case and ask for a re-import of the affected period. Support can force the collection job to re-run for a number of days back. Say how far back you need, because that determines the work.

If you only care about going forward, no action is needed — just expect a gap in the two prompt-count metrics covering the period before consent.

Confirming it worked

1. The consent banner no longer appears when you select the Copilot measurements.
2. Allow a full collection cycle — collection runs daily — before judging the result.
3. Check the two prompt-count fields for the day after consent was granted, not for historical dates. Historical dates will still read zero until a re-import is run.

If it still does not populate

Before opening a case, confirm all three:

1. The consent was granted on CloudScape, not on a Report Gatherer or Tester application.
2. It was granted by an account authorised to consent for the organisation.
3. You are looking at a date after the consent, and at least one full daily collection has run since.

When you raise the case, say which application you consented, when, and whether you need historical data re-imported. That turns two or three exchanges into one.