> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/integrations/calendar/microsoft-365/microsoft-365-permissions.md).

# Microsoft 365 permissions

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2F0U1G9m57W0d8fQjxdhHJ%2Flogo_microsoft365.webp?alt=media&amp;token=efd6e5ec-67ec-4bb7-89ec-19183a1cc0ed" alt=""><figcaption></figcaption></figure>

### Full permissions

This is UMA's preferred method of interacting with Microsoft Graph API as the level of access provides a more feature rich solution for end users.

The full permissions are documented as follows:

<details>

<summary><mark style="color:blue;">Calendars.ReadWrite</mark></summary>

***Read and write calendars in all mailboxes***

***

We need this permission to write to your users and resource calendars.

This is required when booking or editing a booking through UMA.

</details>

<details>

<summary><mark style="color:blue;">Group.Read.All</mark></summary>

***Read all groups***

***

We need this permission to read your Microsoft 365 groups for [user sync](/uma-knowledgebase/integrations/calendar/microsoft-365/user-sync-legacy-search-scim.md).

</details>

<details>

<summary><mark style="color:blue;">GroupMember.Read.All</mark></summary>

***Read all group memberships***

***

We need this permission to read the members of your Microsoft 365 groups for [user sync](/uma-knowledgebase/integrations/calendar/microsoft-365/user-sync-legacy-search-scim.md).

</details>

<details>

<summary><mark style="color:blue;">Place.Read.All</mark></summary>

***Read all company places***

***

Allows UMA to read your company's places (conference rooms and room lists) for calendar events and other applications, on behalf of the signed-in user.

</details>

<details>

<summary><mark style="color:blue;">User.Read.All</mark></summary>

***Read all users full profiles***

***

Allows UMA to read the full set of profile properties including photos, reports, and managers of other users in your organisation, on behalf of the signed-in user.

</details>

### Lite permissions

Lite permissions should only be used for where profile photo and group user sync is not required.

The lite permissions are documented as follows:

<details>

<summary><mark style="color:blue;">Calendars.ReadWrite</mark></summary>

***Read and write calendars in all mailboxes***

***

We need this permission to write to your users and resource calendars.

This is required when booking or editing a booking through UMA.

</details>

<details>

<summary><mark style="color:blue;">Places.Read.All</mark></summary>

***Read all company places***

***

Allows UMA to read your company's places (conference rooms and room lists) for calendar events and other applications, on behalf of the signed-in user.

</details>


---

# 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://support.meetuma.ai/uma-knowledgebase/integrations/calendar/microsoft-365/microsoft-365-permissions.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.