> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/settings-and-security/entra-id-scopes.md). # Microsoft Entra ID Scopes Use this page to review the Microsoft Graph permissions Boza requests and the product actions that use them. Compare the list with the Microsoft consent screen and your organization's approved integration scope before granting access. ## How Boza Connects to Microsoft Entra ID During implementation, Boza is connected to your organization's Microsoft Entra ID tenant. Boza accesses information exclusively through **Microsoft Graph APIs**, enabling precise management of users and applications without compromising sensitive data. Boza accesses the following Microsoft Graph APIs in read and/or write mode: | API | Documentation | | -------------------- | ------------------------------------------------------------------------------------------------------------ | | Users | [microsoft.com/graph/api/user-list](https://learn.microsoft.com/en-us/graph/api/user-list) | | Audit Logs / Sign-in | [microsoft.com/graph/api/signin-list](https://learn.microsoft.com/en-us/graph/api/signin-list) | | Groups | [microsoft.com/graph/api/group-list](https://learn.microsoft.com/en-us/graph/api/group-list) | | Licenses | [microsoft.com/graph/api/subscribedsku-list](https://learn.microsoft.com/en-us/graph/api/subscribedsku-list) | ## Required Scopes The following scopes are requested when connecting Boza to your Microsoft tenant: | Scope | Description | | --------------------------- | ---------------------------------------------------------------------------------------------------- | | `User.ReadWrite.All` | Read users, and create, update, or delete them during supported onboarding and offboarding workflows | | `GroupMember.ReadWrite.All` | Read group membership, and update it during onboarding and offboarding | | `Directory.Read.All` | Read directory data: users, groups, and organizational structure | | `AuditLog.Read.All` | Read and query SSO sign-in audit logs | | `Policy.Read.All` | Read directory policies | | `openid`, `offline_access` | Sign in and keep the connection refreshed | The write scopes (`User.ReadWrite.All`, `GroupMember.ReadWrite.All`) support onboarding and offboarding actions. Normal directory, application, license, and sign-in synchronization reads data. Review each lifecycle workflow before approving it because offboarding can delete the Entra ID user. ## Data Collection Summary Boza collects only the data essential to delivering its services: | Data Type | Details | Source API | Purpose | Notes | | ------------------- | ------------------------------------------------------------------- | -------------------- | -------------------------------------------------- | --------------------------------------------------- | | User directory data | Name, email, job title, team/department, assigned licenses, manager | Users | Map company organization | Personal data | | User activity data | Date and time of SSO logins to third-party apps | Audit Logs / Sign-in | Evaluate application usage to optimize resources | Login duration and in-app activity are not recorded | | Group data | List of groups users belong to | Groups | Access control and auditing | — | | Application list | Apps users sign in to | Audit Logs / Sign-in | Build the list of applications in the organization | — | ## Privacy Safeguards * **Purpose-scoped permissions** — normal synchronization reads directory, license, group, policy, and sign-in data; write permissions are used by supported lifecycle workflows. * **No mail or file content** — this integration does not request email-message or OneDrive-file content. * **Tenant context** — synchronized records and workflow actions are associated with the connected Boza organization. * **Transport protection** — Microsoft Graph and Boza API traffic use encrypted HTTPS connections. ## Need Help? If you have questions about the scopes or data collection, contact us at ****. --- # 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://boza.gitbook.io/docs/settings-and-security/entra-id-scopes.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.