> 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/es/automatizacion/runbooks/runbook-references/org/mail/hide-mailboxes_scheduled.md).

# Ocultar buzones programado

Ocultar o mostrar todos los calendarios de Bookings en la libreta de direcciones

{% hint style="info" %}
Este es un runbook programado. Está diseñado para ejecutarse según una programación recurrente en lugar de activarse para un único objeto. Véase [Programación](/es/automatizacion/runbooks/scheduling.md) para obtener detalles sobre cómo configurar las programaciones del runbook.
{% endhint %}

### Descripción

Oculta cada buzón de calendario de Microsoft Bookings de la lista global de direcciones, o los vuelve a mostrar, en cada ejecución. Los nuevos calendarios de Bookings se cubren automáticamente la próxima vez que se ejecute el runbook.

### Ubicación

Organización → Correo → Ocultar buzones (programado)

**Nombre completo del runbook**

rjgit-org\_mail\_hide-mailboxes\_scheduled

### Detalles

| Propiedad          | Valor                                                                             |
| ------------------ | --------------------------------------------------------------------------------- |
| Versión            | 1.0.3                                                                             |
| Módulos requeridos | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>ExchangeOnlineManagement (>= 3.9.2)</p> |
| Programable        | sí                                                                                |

### Permisos

#### Permisos de aplicación

* **Tipo**: Office 365 Exchange Online
  * Exchange.ManageAsApp
    * *Ejecuta Get-/Set-Mailbox en la sesión de Exchange Online solo de aplicación*

#### roles de RBAC

* Administrador de Exchange
  * *Ejecuta Get-/Set-Mailbox para ocultar todos los buzones de programación de Bookings de la lista de direcciones*

### Parámetros

#### HideBookingCalendars

Los calendarios ocultos no se pueden encontrar en Outlook ni en la libreta de direcciones; desactívelo para volver a mostrarlos.

| Propiedad                      | Valor                             |
| ------------------------------ | --------------------------------- |
| Requerido                      | verdadero                         |
| Valor predeterminado           | Verdadero                         |
| Tipo                           | Booleano                          |
| Nombre para mostrar del portal | ¿Ocultar calendarios de Bookings? |

[Volver al resumen de referencia de Runbook](/es/automatizacion/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/es/automatizacion/runbooks/runbook-references/org/mail/hide-mailboxes_scheduled.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.