> 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-or-remove-teams-mailcontact.md).

# Add Or Remove Teams Mailcontact

Give a Teams channel a friendly email address or remove it

### Description

Creates a mail contact that forwards a friendly email address to the long address Teams generates for a channel. People can then email the channel with an address they can remember. The same runbook removes the friendly address again.

### Location

Organization → Mail → Add Or Remove Teams Mailcontact

**Full Runbook name**

rjgit-org\_mail\_add-or-remove-teams-mailContact

### Details

| Property         | Value                                                                             |
| ---------------- | --------------------------------------------------------------------------------- |
| Version          | 1.0.1                                                                             |
| Required modules | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>ExchangeOnlineManagement (>= 3.9.2)</p> |
| Schedulable      | no                                                                                |

### Permissions

#### Application permissions

* **Type**: Office 365 Exchange Online
  * Exchange.ManageAsApp
    * *Runs New-/Set-MailContact and Get-EXORecipient in the app-only Exchange Online session*

#### RBAC roles

* Exchange Administrator
  * *Required for the app-only Exchange Online session creating the relay mail contact*

### Parameters

#### RealAddress

Email address that Teams generated for the channel.

| Property            | Value                 |
| ------------------- | --------------------- |
| Required            | true                  |
| Default Value       |                       |
| Type                | String                |
| Portal display name | Channel email address |

#### DesiredAddress

Friendly address that should forward to the channel.

| Property            | Value                  |
| ------------------- | ---------------------- |
| Required            | true                   |
| Default Value       |                        |
| Type                | String                 |
| Portal display name | Friendly email address |

#### DisplayName

Name shown for the contact in the address book. Leave empty to use the part of the friendly address before the @ sign.

| Property            | Value                    |
| ------------------- | ------------------------ |
| Required            | false                    |
| Default Value       |                          |
| Type                | String                   |
| Portal display name | Name in the address book |

#### Remove

Set up the friendly address creates the mail contact; Remove the friendly address deletes it again.

| Property            | Value   |
| ------------------- | ------- |
| Required            | false   |
| Default Value       | False   |
| Type                | Boolean |
| Portal display name | Action  |

**Portal options**

| Portal option               | Value |
| --------------------------- | ----- |
| Set up the friendly address | false |
| Remove the friendly address | true  |

[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-or-remove-teams-mailcontact.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.