> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/for-admins/classic-microsoft-integrations.md).

# Classic Microsoft Integrations

## Available Integrations

1. [**Entra ID**](/for-admins/classic-microsoft-integrations/entra-id-integration.md) *(preliminary)*
2. [**Azure Groups**](/for-admins/classic-microsoft-integrations/azure-groups-integration.md)
3. [**Sharepoint**](/for-admins/classic-microsoft-integrations/create-a-sharepoint-connection.md) 
4. [**Onedrive**](/for-admins/classic-microsoft-integrations/onedrive-admin-consent.md)

### Recommended App Registration per Azure App

For most customers, we recommend creating a **separate Azure App Registration for each Blockbrain agent or capability** (e.g. one for SharePoint, one for Outlook, one for OneDrive).

This approach gives you:

* **Least privilege:** Each App Registration only holds the Microsoft Graph scopes it actually needs, so no agent is over-permissioned.
* **Separation of concerns:** A misconfigured or unused agent cannot accidentally affect another agent's access.
* **Easy secret rotation and revocation:** You can rotate or revoke the client secret for a single capability without disrupting the others.
* **Cleaner audit trail:** Entra ID sign-in and audit logs are scoped per App Registration, which makes incident review and access reviews simpler.

{% hint style="warning" %}
While this documentation provides detailed steps we recommend a brief setup call with our expert team to ensure a smooth implementation.

Though not mandatory, experience has shown that a 15-20 minute setup call can significantly accelerate your integration and help avoid potential configuration issues.

To schedule a setup call please contact your Key Account Manager.
{% endhint %}


---

# 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.blockbrain.ai/for-admins/classic-microsoft-integrations.md?ask=<question>&goal=<endgoal>
```

`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.