> 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/group/mail/show-or-hide-in-address-book.md).

# Show Or Hide In Address Book

Show or hide this group in the address book

### Description

Shows this Microsoft 365 or distribution group in the address lists or hides it from them. A hidden group still receives email at its address; it just does not appear in the address book. Query only shows the current state without changing anything.

### Location

Group → Mail → Show Or Hide In Address Book

**Full Runbook name**

rjgit-group\_mail\_show-or-hide-in-address-book

### Details

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

### Permissions

#### Application permissions

* **Type**: Office 365 Exchange Online
  * Exchange.ManageAsApp
    * *Runs Set-UnifiedGroup or Set-DistributionGroup with -HiddenFromAddressListsEnabled in the app-only session*

#### RBAC roles

* Exchange Administrator
  * *Required for the app-only Exchange Online session hiding or showing the group*

### Parameters

#### GroupName

Identity of the group in Exchange Online, such as its name or alias. Set by the portal from the selected group.

| Property         | Value                                  |
| ---------------- | -------------------------------------- |
| Required         | true                                   |
| Default Value    |                                        |
| Type             | String                                 |
| Hidden in portal | yes (preset via runbook customization) |

#### Action

Show lists the group in the address book, Hide removes it from the lists, Query only shows the current state.

| Property            | Value  |
| ------------------- | ------ |
| Required            | false  |
| Default Value       | 1      |
| Type                | Int32  |
| Portal display name | Action |

**Portal options**

| Portal option                | Value |
| ---------------------------- | ----- |
| Show group in address book   | 0     |
| Hide group from address book | 1     |
| Query current state only     | 2     |

[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/group/mail/show-or-hide-in-address-book.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.