> 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/add-ins/outlook.md).

# Outlook

This tutorial outlines the steps to integrate the Blockbrain Add-in into Outlook.

## Deploying the Blockbrain Outlook add-in to Microsoft 365

The Blockbrain add-in for **Outlook** is deployed centrally from the Microsoft 365 admin center. No local installation and no file downloads are required. It is published as a manifest URL that Microsoft 365 reads directly.

### Before you start

| Requirement  | Detail                                                                                                                                           |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Admin role   | **Global Administrator.** An Exchange Administrator can view Integrated apps, but only a Global Admin can consent to and deploy a custom add-in. |
| Manifest URL | Publicly reachable HTTPS URL                                                                                                                     |

**Manifest URL**

* Outlook — `https://ms-outlook-addin.theblockbrain.ai/manifest.xml`

### Deployment steps

#### 1. Open Integrated apps

Go to [admin.cloud.microsoft](https://admin.cloud.microsoft/?#/Settings/IntegratedApps) → **Settings** → **Integrated apps**.

#### 2. Select "Upload custom apps"

The button sits above the app list and opens the upload wizard.

#### 3. Set the app type to "Office Add-in"

Do **not** choose **Teams app** — that option expects a zipped unified manifest, which is not the format the Blockbrain add-ins use.

#### 4. Choose the URL option, not the file upload

Under **Choose how to upload app**, select **Provide URL for manifest** instead of **Upload manifest file**.

Paste the Outlook manifest URL, then select **Validate**. \
The add-in name and icon appear once the manifest has been read successfully.

#### 5. Assign users

Select **Add users**, then pick one of:

* **Entire organization** — the usual choice for a full rollout.
* A specific Microsoft 365, security, or distribution group.
* **Just me** — useful for a pilot before widening the scope.

#### 6. Accept the permission request

Review the capabilities and permissions the add-in requests, then select **Accept permissions**. This is the step that requires the Global Administrator role.

#### 7. Finish the deployment

Select **Next**, check the summary, then **Finish deployment**. The add-in now appears on the Integrated apps **Overview** tab, where its assigned users can be edited or the deployment removed later.

{% hint style="warning" %}
Rollout can take **up to 24 hours** to reach every user and every client. To check, restart Outlook and look under **Home → Add-ins**
{% endhint %}

### Troubleshooting

**Validation fails after pasting the URL**

Open the manifest URL in a browser first. It must return XML over HTTPS with no sign-in prompt.

If the manifest loads in the browser but is still rejected, the add-in ID most likely already exists in the tenant. Remove the earlier deployment on the **Overview** tab and upload again.

**The add-in does not appear for users**

Confirm the assigned users on the **Overview** tab, then allow the full 24-hour propagation window before investigating further. Users on Office for the web may need to reload the browser tab; desktop users need to restart the app.


---

# 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/add-ins/outlook.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.