> 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/what-data-do-you-collect-for-365-analytics.md).

# What data do you collect for 365 Analytics

### How does 365 Analytics connect to my data?

365 Analytics uses the Microsoft Graph service to access your customer tenant. 

This is managed through the use of an Enterprise Application provisioned in your Microsoft Entra directory and controlled through the use of security roles associated with the Enterprise Application. This enterprise application is called 'SoftwareOne Cloud Insider - Read Only' and is configured as part of the onboarding process.

### Encryption <a href="#encryption" id="encryption"></a>

365 Analytics makes extensive use of data encryption for data in transit and at rest:

* Traffic from 365 Analytics users is encrypted using HTTPS in their web browsers.
* API traffic between the 365 Analytics application and Microsoft’s services is all encrypted. Graph traffic is natively encrypted since it’s just HTTP requests; other protocols, such as remote PowerShell, are tunneled over HTTPS.
* All 365 Analytics data is encrypted at rest.


---

# 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/what-data-do-you-collect-for-365-analytics.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.