Skip to main content

Enable Copilot and Power BI activity signals

Audit-based usage evidence is optional. It makes the Platform's recommendations for Copilot and Power BI rest on real interaction events instead of last-activity timestamps. This page covers the permission and the tenant-wide audit setting that both share.

The evidence comes from the Office 365 Management APIs. This is a different resource than Microsoft Graph, so you add the permission separately.

Using Dynamics 365?

It needs auditing per environment and per table on top. See How Zation gets Dynamics 365 data.

Before you begin​

  • Complete the Onboarding guide through Step 2, so the Zation Platform Connector App Registration exists.
  • A Global Administrator account.
  • Access to the App Registration to add a permission and grant admin consent.
  • Access to Microsoft Purview to turn on the unified audit log.

Step 1: Grant the activity permission​

  1. In the Zation Platform Connector App Registration, open API permissions → + Add a permission → APIs my organization uses. Search for and select Office 365 Management APIs.

  2. Select Application permissions and add:

    PermissionUsed for
    ActivityFeed.ReadAudit-event metadata (which user used which app or workload, and when) for Copilot interaction-frequency evidence and Power BI usage evidence. Metadata only. No record content, no Copilot prompt or response text.

  3. Select Grant admin consent for <Tenant> → Yes.

The permission is shared by Copilot and Power BI. You can't grant it for only one.

Step 2: Turn on the unified audit log​

Audit events only reach the Platform when the tenant's unified audit log is on. In Microsoft Purview, open Audit and select Start recording user and admin activity.

Without the audit log, signals fall back

If the unified audit log is off, Copilot and Power BI fall back to their proxy and last-activity signals. Turn it on before the first sync.

Next steps​