> 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/email/reports/mailbox-statistics.md). # Mailbox Statistics This report lists every mailbox in the selected tenant with its last activity date, how much space it is using against its quota, how many items it holds, and whether an online archive exists. It is the fastest way to find mailboxes that are close to full, and mailboxes that have not been touched in months. ## Table Details The information displayed comes from the prebuilt Graph report `getMailboxUsageDetail`. For additional details please see the [Graph documentation](https://learn.microsoft.com/en-us/graph/api/reportroot-getmailboxusagedetail?view=graph-rest-beta\&tabs=http). **Storage Used** and **Quota** are reported by Microsoft in bytes and shown here in GB. {% hint style="info" %} The CIPP call to the Graph endpoint is hard coded to 7 days. There is no period selector on this page, because the figures are a snapshot of each mailbox as it stands rather than a count of activity over time. {% endhint %} Selecting All Tenants queues the report as a background job, so the table stays empty with a queued message until every tenant has been collected. ## Anonymised Reports Microsoft 365 has a tenant-wide setting that conceals user names in usage reports, replacing them with hashes rather than user principal names. Where CIPP detects that this report has come back anonymised, it shows a warning above the results. The fix is on the tenant, not in CIPP. Enabling the **Enable Usernames instead of pseudo anonymised names in reports** standard turns the setting off, after which the report needs running again to pick up real names. *** ## 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cipp.app/user-documentation/email/reports/mailbox-statistics.md?ask=&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.