> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/v1/technical-description/permissions-required.md).
# Permissions Required
by the Bsure Insights Data Collector Managed Application
When you run the [permissions script](/v1/installation/installation-instructions.md#step-2-start-the-permissions-script)[ ](https://docs.bsure.no/install/installation-instructions#step-2-give-permissions)during the installation process, you give the Microsoft Graph permissions below to a Managed Identity used by the Azure Functions in the Managed Resource Group.
* Directory.Read.All, used to read user and license information​
* AuditLog.Read.All, used to get user last signin information​
* Domain.Read.All, used to get friendly names for tenantid​
* Reports.Read.All, used to read user MFA registration information
* Policy.Read.All, used to read signin logs and conditional access policies
* MailboxSettings.Read, used to read user purpose of the user's mailbox
#### The Managed Identity holds these permissions:
### Permissions Bsure have in your environment:
To monitor jobs and provide updates and new features the solution provider Bsure will be given contributor access during setup to the Managed Resource Group inside the managed application.
Bsure can't consume customer data, ref
---
# 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.bsure.io/v1/technical-description/permissions-required.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.
