# MDE Onboarding

This page will reflect the state of the connector between Microsoft Defender for Endpoint and Mobile Threat Defense. This page will have different views depending on if being accessed via All Tenants or a single tenant. All Tenants displays an informational table. Single tenant will also show a link to "Start Onboarding" that will send you to the MDE onboarding page within the Microsoft Defender portal if the state is not enabled or available.

## Page Actions

<details>

<summary>Live/Cached</summary>

This button will toggle the table between live data and cached data. The live data will pull directly from Microsoft while the cached data is from the most recent CIPP cache database update.

When toggled to cached, the Sync button will appear allowing you to queue a task to run a fresh database sync.

</details>

## Partner State

* `enabled` — MDE connector is set up and active
* `available` — connector exists and is reachable but not fully configured/enrolled
* `unavailable` — connector can't be reached or isn't responding
* `unresponsive` — connector was set up but has stopped communicating
* `notSetUp` — no connector configured at all
* `error` — something went wrong retrieving the state

{% hint style="warning" %}
The connector being configured is a prerequisite, not a confirmation of full deployment. See [Defender Deployment](/user-documentation/security/defender/deployment.md) for how to complete a full deployment.
{% endhint %}

***

## Feature Requests / Ideas

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cipp.app/user-documentation/security/reports/mde-onboarding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.