> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/feature-reference/connectors/overview.md).

# Overview

The Overview tab gives you a real-time snapshot of your Connector's configuration, sync health, and mapping status — all in one place.

![The Connector Overview tab for AOH Test AD → CloudSync (Delta), showing status, mode, pipeline diagram, mapping summary, and recent activity](https://2706226485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8BF8xXbTZGWilkpjaGNh%2Fuploads%2Fgit-blob-9a291dab74a04e6e50eb0126562c3e19595a0462%2Fconnector-overview.png?alt=media)

*The Overview tab summarizes your Connector's current state and the data pipeline from source to target.*

## What you can do here

| Action                                                            | What it does                                                                                                                                                                                                                                                                       |
| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| View status badge (IDLE / RUNNING)                                | Shows whether the Connector is currently performing a Sync.                                                                                                                                                                                                                        |
| View unpublished changes badge                                    | Alerts you when field mapping changes have been saved but not yet published to the active Sync.                                                                                                                                                                                    |
| Expand Live Azure State                                           | Shows a live read of the Connector's state in your connected Azure environment.                                                                                                                                                                                                    |
| Navigate tabs (Mappings, MI Rules, Revisions, Schedule, Settings) | Moves to the respective configuration view for this Connector.                                                                                                                                                                                                                     |
| Review Mapping Summary                                            | Shows how many Source Field Mappings and Provisioning Mappings are configured, and which target actions (Create, Update, Delete) are enabled.                                                                                                                                      |
| Review Pipeline diagram                                           | Confirms that your data source, the Mappings layer, and the Target System are all connected and reporting the expected record counts.                                                                                                                                              |
| View Recent Activity                                              | Lists the most recent Sync runs for this Connector.                                                                                                                                                                                                                                |
| Bulk Upload                                                       | Replays every source row through the selected mapping revision against the target — use this after a major mapping change to backfill the target with the new shape. Select a mapping revision and optionally set a batch size, then click **Start Bulk Upload**.                  |
| Source Query Builder                                              | Defines the API query AOH Sync uses to fetch records from your Source System. Set a query name, choose the HTTP method (for example, **GET**), enter the request path, and configure any query parameters. Click **New** to create a query or the refresh icon to reload the list. |

{% hint style="warning" %}
**Bulk Upload writes to your live directory.** It replays every source row against your Active Directory or Entra ID target. Before you start:

* Try a small batch first.
* Plan for Microsoft's limits. Per tenant, Microsoft allows up to 2,000 provisioning API calls in 24 hours on Entra ID P1 or P2 (6,000 with Entra ID Governance), up to 50 records per call, and no more than 40 calls in any 5 seconds. Replaying 5,000 people takes at least 100 calls ([Microsoft](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/inbound-provisioning-api-concepts)).
* If you've turned on Microsoft's **Clear attribute values** preview for an attribute, leaving that attribute out of a record clears it in the target. Microsoft says to include a complete user record in every bulk request ([Microsoft](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/clear-attribute-values)).
  {% endhint %}

## Understanding the status indicators

* **IDLE** — The Connector is not running and is waiting for its next scheduled Sync or a manual trigger.
* **RUNNING** — A Sync is in progress.
* **MODE** — Shows the ingestion mode (for example, **Hybrid AD**).
* **JOIN KEY** — The attribute AOH Sync uses to match incoming records to existing Identities.
* **LAST SYNC** — The timestamp of the most recent completed Sync run.
* **TELEMETRY** — Whether enhanced telemetry collection is turned on or off for this Connector.

The **PIPELINE** diagram shows the three stages of your data flow: the first stage (labeled **Source DB** on screen) connects to your data source, **Mappings** applies your field mapping configuration, and the final stage writes to your connected Target System (shown by its name). A "Connected" badge next to each stage confirms the link is healthy.

{% hint style="info" %}
The **10 unpublished** badge means you have saved mapping changes that are not yet live. Go to the Mappings tab and publish them to apply the changes to future Syncs.
{% endhint %}

## Related

* [Sync Types](https://docs.aohwv.dev/core-concepts/sync-types.md)
* [Identities, Accounts & Users](https://docs.aohwv.dev/core-concepts/identities-accounts-users.md)
* [Field Mappings](https://docs.aohwv.dev/feature-reference/connectors/field-mappings.md)
* [Revisions & History](https://docs.aohwv.dev/feature-reference/connectors/revisions.md)
* [Schedule](https://docs.aohwv.dev/feature-reference/connectors/schedule.md)
* [Connectors](https://docs.aohwv.dev/feature-reference/connectors.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.aohwv.dev/feature-reference/connectors/overview.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.
