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

# Key Benefits & Use Cases

Detect stale accounts, orphan identities and excess or outdated security group memberships.

### See discrepancies and risk across the identity stack

Surface stale accounts, orphaned identities, and security group memberships that are excessive or out of date. Drill down into accounts using a detailed lifecycle audit trail and access graph.

### One unified identity pipeline

Mapping and reconciliation bring siloed HR and IT systems into a single view.

### Establish clear ownership for service accounts

Identify the service accounts across your estate and assign a clear owner to each one.

### Azure Marketplace Deployment

AOHSync runs in the customer's Azure tenant, so your identity data never leaves your trusted zone. Deployment is straightforward, allowing risk insights to arrive quickly.

## Who benefits

| Team            | What AOH Sync changes for them                                      |
| --------------- | ------------------------------------------------------------------- |
| IT Operations   | Visibility into HR (FT and Contractor) data                         |
| Security        | Risk hides in relationships                                         |
| HR / People Ops | Search new employee has a provisioned account and in correct groups |
| Compliance      | One view across employees and external guests                       |

## Common use cases

### External guest/contractor cleanup

Surfaces guest accounts that were invited for a specific project and never removed.

### Visibility of orphaned accounts

Finds orphaned accounts across different directories and systems.

### Role change/privilege creep cleanup

Flags outdated group access left over from role changes. Identify users with excess privileges compared to peers.

## Related

* [What is AOH Sync?](/readme/what-is-aohsync.md)
* [How AOH Sync Works](/core-concepts/how-aohsync-works.md)
* [Provisioning & Deprovisioning Lifecycle](/core-concepts/provisioning-lifecycle.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 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/readme/welcome.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.