> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/help-and-support/faqs/my-365-analytics-report-is-empty.md).

# My 365 Analytics report is empty

If your report is empty and you receive the '*There is no data for this chart'* message, there are a few reasons for this, including:

* The data is being filtered in a way that no data is returning. You might need to edit your report and modify the filters.
* The data might require access to the Security and Audit Logs that may not have been configured. Check your 365 Analytics settings.
* The data has not been collected as the data collection needs to be authorized.
* You may need to reauthorize your tenant**.** For information, see [How do I connect the Microsoft tenant for data collection](/help-and-support/faqs/how-do-i-connect-the-microsoft-tenant-for-data-collection.md)?

If you have completed these steps and still have the notification, or the report is empty, [contact support ](/help-and-support/contact-support.md)for assistance.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/help-and-support/faqs/my-365-analytics-report-is-empty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.