> 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/readme/what-is-aohsync.md).

# What is AOH Sync?

Identity visibility for IT teams. Maps HR to Entra. Flags stale accounts and excess group access.

## How it works

AOH Sync connects your upstream Source Systems (HR systems and directories) to a normalized Identity model, then continuously propagates changes to your Microsoft Entra ID target. When an employee joins, changes roles, or leaves, AOH Sync reflects that change in Entra ID — no manual tickets, no scripts, no delays.

The flow has three stages:

1. **Source Systems** — AOH Sync reads Identity data from your connected HR systems and directories via Connectors.
2. **Identity model** — Incoming data is normalized into a unified Identity model that resolves conflicts and tracks relationships across sources.
3. **Entra target** — AOH Sync provisions, updates, or deprovisions Accounts in Microsoft Entra ID to match the current state of your Identity model.

AOH Sync deploys as a single-tenant appliance in your own Azure subscription, so your Identity data never leaves your environment.

![AOH Sync dashboard showing 1,531 total Identities, 106 groups, and 21 departments, with department and role distribution charts, and a Top Groups by Membership list](https://2706226485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8BF8xXbTZGWilkpjaGNh%2Fuploads%2Fgit-blob-0ae7948aff12ee20d598a13d0a06f6661eee78b4%2Fwhat-is-cloudsync.png?alt=media)

*The AOH Sync dashboard gives you an at-a-glance view of your Identity population, group counts, and distribution across departments and roles.*

## Related

* [Key Benefits & Use Cases](/readme/welcome.md)
* [How AOH Sync Works](/core-concepts/how-aohsync-works.md)
* [Source & Target Systems](/core-concepts/source-and-target-systems.md)
* [Getting Started](/getting-started/getting-started.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 dynamically by asking a question.

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

```
GET https://docs.aohwv.dev/readme/what-is-aohsync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.