> 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/activesync-devices.md).

# ActiveSync Devices

This report lists every mobile device partnership registered against a mailbox in the selected tenant, one row per device. It shows what each device is, when it last synchronised, and whether Exchange Online currently allows or blocks it, so you can find stale partnerships and quarantined devices without opening Exchange Online PowerShell.

## Table Details

The properties returned are for the Exchange Online PowerShell command `Get-MobileDevice`. For more information on the command please see the [Microsoft documentation](https://learn.microsoft.com/powershell/module/exchangepowershell/get-mobiledevice).

**Device Access State** is the column the row actions work from, and is normally `Allowed`, `Blocked`, or `Quarantined`. CIPP adds one column of its own, **Sync Info Note**: where the row is Outlook for iOS or Android, it explains that those apps use modern authentication and do not report ActiveSync sync times, which is why their sync columns can look empty or out of date.

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Allow Device</td><td>Allows the device to synchronise with the mailbox. Greyed out where <strong>Device Access State</strong> is already <code>Allowed</code>.</td><td>true</td></tr><tr><td>Block Device</td><td>Stops the device synchronising with the mailbox. Greyed out where <strong>Device Access State</strong> is already <code>Blocked</code>.</td><td>true</td></tr><tr><td>Delete Device</td><td>Removes the device partnership from the mailbox entirely. This cannot be undone.</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>

Each action confirms first, naming the device and the mailbox it belongs to. Allowing and blocking are settings on the mailbox rather than on the device, so a device that synchronises several mailboxes needs the action running against each of its rows.

***

## 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/activesync-devices.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.