> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/email/reports/sharedmailboxenabledaccount.md).

# Shared Mailbox with Enabled Account

This report lists the shared mailboxes in the selected tenant whose underlying user account can still sign in. A shared mailbox is meant to be reached through delegation rather than signed into directly, so an enabled account behind one is an unnecessary sign-in surface and is flagged by most security baselines.

## Filters

The table opens with a filter on **Account Enabled** set to `Yes`. This matches what the report already returns, since mailboxes whose account is disabled are left out.

## Table Details

The report pairs each of the tenant's shared mailboxes with its user account and returns only those where the account can still sign in.

| Column                   | Description                                                                            |
| ------------------------ | -------------------------------------------------------------------------------------- |
| User Principal Name      | The sign-in address of the account behind the shared mailbox.                          |
| Display Name             | The friendly name of the shared mailbox.                                               |
| Account Enabled          | Whether the account can sign in. Always `Yes` in this report.                          |
| Assigned Licenses        | Any licences assigned to the account. A shared mailbox under 50GB should not need one. |
| On Premises Sync Enabled | Whether the account is synchronised from on-premises Active Directory.                 |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Block Sign In</td><td>Blocks the account behind the shared mailbox from signing in, leaving the mailbox itself and everyone's delegated access to it working normally. Greyed out where <strong>On Premises Sync Enabled</strong> is <code>Yes</code>, because a synchronised account has to be disabled in on-premises Active Directory instead.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/email/reports/sharedmailboxenabledaccount.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.