> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/copilot/reports/copilot-trend.md).

# Copilot Usage Trend

The Copilot Usage Trend report shows how Copilot activity in the selected tenant changes over time, with one row per reporting date. Alongside overall enabled and active totals, it breaks active usage out by individual app (Teams, Word, Excel, PowerPoint, Outlook, OneNote, Loop, and Copilot Chat), so you can track adoption trends and see which apps are driving Copilot use day to day.

The figures come from the Microsoft 365 Copilot usage reports in Microsoft Graph and cover the last 30 days, with one row per day in that window.

## Table Details

| Column              | Description                                                                                                                         |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Report Date         | The date this row's usage figures are for, letting you follow Copilot activity as a day-by-day trend.                               |
| Any App Active      | How many people actively used Copilot in at least one app on that date, the headline measure of real usage.                         |
| Any App Enabled     | How many people had Copilot available to them across apps on that date, the potential audience for comparison against active usage. |
| Teams Active        | Number of people who actively used Copilot in Microsoft Teams that day.                                                             |
| Word Active         | Number of people who actively used Copilot in Word that day.                                                                        |
| Excel Active        | Number of people who actively used Copilot in Excel that day.                                                                       |
| PowerPoint Active   | Number of people who actively used Copilot in PowerPoint that day.                                                                  |
| Outlook Active      | Number of people who actively used Copilot in Outlook that day.                                                                     |
| OneNote Active      | Number of people who actively used Copilot in OneNote that day.                                                                     |
| Loop Active         | Number of people who actively used Copilot in Loop that day.                                                                        |
| Copilot Chat Active | Number of people who actively used Copilot Chat that day.                                                                           |

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cipp.app/user-documentation/copilot/reports/copilot-trend.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
