> For the complete documentation index, see [llms.txt](https://docs.licensemeter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensemeter.com/troubleshooting/report-privacy.md). # Report privacy and detection coverage Understand how concealed report names and unavailable signals limit per-user findings. Microsoft usage reports can conceal user identities. When LicenseMeter cannot match a report row to a directory user, it cannot make the same user-level activity assessment from that row. Check **Settings > Detection capabilities** for **Identifiable usage reports**, **Entra ID P1 sign-in activity** and **Copilot usage data**. An unavailable capability explains a limit in the evidence; it is not evidence that the tenant has no unused licenses. ## What remains available Directory state, assigned licenses and purchased seat counts can still support relevant findings when activity reports are incomplete. Imported data supports only the columns and time period in the export. Adobe entitlements do not provide an inactivity signal. ## Before changing report privacy Changing Microsoft's report privacy setting affects reporting across the organization and can expose user-identifiable activity to people authorized to view those reports. It is a tenant-wide privacy decision, not a LicenseMeter-only preference. If your organization approves that change, an authorized administrator can review **Microsoft 365 admin center > Settings > Org settings > Reports**. Record the previous setting and the reason. To reverse the setting, re-enable concealed identities in the same Reports settings. Previously downloaded exports or data already collected by reporting tools are not erased by switching it back. LicenseMeter's connector only reads the report-privacy setting through **ReportSettings.Read.All**; it does not change it. Keeping names concealed is valid when your organization's privacy requirements call for it. Treat the resulting detection limits explicitly in your reviews. See [Microsoft usage report privacy guidance](https://learn.microsoft.com/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide) and your internal privacy policy before deciding. --- # 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.licensemeter.com/troubleshooting/report-privacy.md?ask=&goal= ``` `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.