True Adoption: "Audit Log Data Is Not Available" When Setting Up the Copilot Persona

Purpose

When you create the Copilot persona in True Adoption, setup can stop with a message that audit log data is not available for the organization. The cause is almost always a missing tenant consent for one Microsoft Graph permission. This article covers which permission, which application to consent it on — that part is easy to get wrong — and how long to wait before concluding it has not worked.

The permission

True Adoption needs AiEnterpriseInteraction.Read.All.

It is worth knowing what this grants before you take it to whoever approves permissions in your organisation, because the name sounds broader than it is:

AiEnterpriseInteraction.Read.All — This permission provides visibility into usage patterns only, enabling organizations to understand AI adoption while maintaining user privacy and data isolation. This is read only access and does NOT provide access to AI prompts, responses, or user content.

Granting it requires a Global Administrator. A user with a lesser role will not be able to complete the consent.

Consent it on the right application

This is the step that costs people the most time.

Your tenant will contain several ENow enterprise applications, and more than one of them has a similar name — there are separate Report Gatherer applications for Office 365, for SharePoint Online and for Microsoft Teams, alongside the Tester applications used for monitoring. Consenting the permission on the wrong one produces no error. It simply does not fix the problem.

For True Adoption, the consent belongs on the ENow Report Gatherer application — the one used for reporting and adoption data, not one of the monitoring Tester apps. Check the exact display name in your own tenant before consenting, since it varies slightly by deployment.

If you have already consented something and the message persists, check which application you consented before assuming the consent itself failed. In practice this is the single most common reason the error survives a consent.

Verify the consent registered

Back in the Adoption Center, the permission should show a green check box. That confirms the product can see the consent. It does not yet mean data has been collected.

Then wait — longer than you would expect

Data collection for the True Adoption Center runs on a 24-hour collection cycle. On a large tenant, the initial collection can take 48 hours or more to complete and display results. This is expected on the first full ingestion; after that the Center updates daily.

Three things affect when data first appears:

• The time of day the consent was completed, relative to a collection cycle that may already have been in progress.
• The overall size of the tenant and the associated data set.
• The thresholds and measurements being evaluated during the initial collection, across every persona defined in the application.

A blank Copilot persona a few hours after consent is normal and not worth raising a case for. A blank one after three days is not.

If data still does not appear

Before opening a case, confirm all three of these, because each has been the actual cause at least once:

1. The consent is on the reporting Report Gatherer application, not another ENow application.
2. The permission shows the green check in the Adoption Center, not just in the Entra portal.
3. More than 48 hours have passed since the consent, and at least one full collection cycle has run since.

When you raise the case, say which application you consented and when, and whether the green check is showing. That skips a round trip.