> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/org/mail/add-equipment-mailbox.md).

# Add Equipment Mailbox

Create an equipment mailbox with optional booking delegates

### Description

Creates an equipment mailbox in Exchange Online, for example for a projector or a pool car, so it can be booked in meeting requests. Without booking delegates the equipment accepts requests automatically when it is free. With booking delegates every request waits for their approval; they get no access to the mailbox itself. The user account behind the mailbox can be disabled.

### Location

Organization → Mail → Add Equipment Mailbox

**Full Runbook name**

rjgit-org\_mail\_add-equipment-mailbox

### Details

| Property         | Value                                                                                                                           |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Version          | 2.0.0                                                                                                                           |
| Required modules | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>Microsoft.Graph.Authentication (>= 2.41.2)<br>ExchangeOnlineManagement (>= 3.9.2)</p> |
| Schedulable      | no                                                                                                                              |

### Permissions

#### Application permissions

* **Type**: Office 365 Exchange Online
  * Exchange.ManageAsApp
    * *Creates the equipment mailbox and sets its calendar processing and booking delegates in the app-only Exchange Online session*
* **Type**: Microsoft Graph
  * User.ReadWrite.All *(optional — feature: Disable user account)*
    * *Reads the mailbox's user account and blocks its sign-in via PATCH /users/{id} when DisableUser is on (default)*

#### RBAC roles

* Exchange Administrator
  * *Required for the app-only Exchange Online session creating the equipment mailbox*

### Parameters

#### MailboxName

Alias of the mailbox, which becomes the part of the email address in front of the @ sign.

| Property            | Value  |
| ------------------- | ------ |
| Required            | true   |
| Default Value       |        |
| Type                | String |
| Portal display name | Alias  |

#### DisplayName

Name shown in the address book. Leave empty to use the alias.

| Property            | Value        |
| ------------------- | ------------ |
| Required            | false        |
| Default Value       |              |
| Type                | String       |
| Portal display name | Display name |

#### DelegateTo

Users who approve or decline every booking request for the equipment. Leave empty to accept requests automatically when the equipment is free.

| Property      | Value     |
| ------------- | --------- |
| Required      | false     |
| Default Value |           |
| Type          | String\[] |

#### DisableUser

Blocks sign-in for the user account behind the mailbox. Booking keeps working.

| Property            | Value                                  |
| ------------------- | -------------------------------------- |
| Required            | false                                  |
| Default Value       | True                                   |
| Type                | Boolean                                |
| Portal display name | Block sign-in for the mailbox account? |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# 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.realmjoin.com/automation/runbooks/runbook-references/org/mail/add-equipment-mailbox.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.