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

# Overview

This guide walks you through deploying AOH Sync in your Azure subscription and completing the initial configuration. Follow the steps in order — each step builds on the last. The full path from prerequisites to your first sync takes approximately **45–60 minutes**.

## What you'll need

| Requirement          | Details                                                                                             |
| -------------------- | --------------------------------------------------------------------------------------------------- |
| Azure subscription   | With the ability to deploy a VM from the Azure Marketplace and create resources in a resource group |
| A domain you control | For example, `sync.yourcompany.com`. You need the ability to add an A record with your DNS provider |
| AOH Sync license key | Provided when you purchase AOH Sync. Format: `CS-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX`                     |

{% stepper %}
{% step %}
[**Prerequisites**](/getting-started/01-prerequisites.md)

Confirm you have an active Azure subscription, an AOH Sync license key, and a domain you control before you begin.
{% endstep %}

{% step %}
[**Step 1 — App Registration**](/getting-started/02-app-registration.md)

Create an Azure App Registration, grant the required Microsoft Graph permissions, and generate a client secret. AOH Sync uses this registration to authenticate your users via Entra ID. (\~5 minutes)
{% endstep %}

{% step %}
[**Step 2 — Azure Marketplace**](/getting-started/03-deploy.md)

Find AOH Sync in the Azure Marketplace, configure your deployment, and provision your VM. (\~2–3 minutes provisioning)
{% endstep %}

{% step %}
[**Step 3 — DNS**](/getting-started/04-dns.md)

Add an A record pointing your chosen domain to the VM's public IP address. AOH Sync configures TLS automatically once the domain resolves. (A few minutes to propagate)
{% endstep %}

{% step %}
[**Step 4 — First Login**](/getting-started/05-first-login.md)

Open the browser setup wizard at `https://<your-domain>/onboard`, enter your Azure AD credentials, and start the install. (\~10–15 minutes)
{% endstep %}

{% step %}
[**Step 5 — Redirect URI**](/getting-started/06-redirect-uri.md)

Return to your App Registration and add the OAuth redirect URI for your domain. This is the final configuration step before AOH Sync is live.
{% endstep %}

{% step %}
[**Step 6 — Connect a Source System**](/getting-started/07-connect-source-system.md)

Connect the HR or identity system AOH Sync reads people from. Adding it automatically creates an Account Import connector. (\~5 minutes)
{% endstep %}

{% step %}
[**Step 7 — Connect a Target System**](/getting-started/08-connect-target-system.md)

Connect your Microsoft Entra ID or Active Directory tenant. Adding it automatically creates an Identity Ingestion connector. (\~10 minutes)
{% endstep %}

{% step %}
[**Step 8 — Set Up Provisioning**](/getting-started/09-set-up-provisioning.md)

Create the Outbound Provisioning connector that writes identities out to your target directory. (\~5 minutes)
{% endstep %}

{% step %}
[**Step 9 — Run Your First Sync**](/getting-started/10-first-sync.md)

Confirm field mappings, trigger a sync, and verify the results in Sync History and the Dashboard.
{% endstep %}
{% endstepper %}

## Managing your instance

Once AOH Sync is deployed, see [Managing Your Instance](/getting-started/11-managing-your-instance.md) for information on checking status, viewing logs, applying updates, and monitoring your instance.

## Need help?

Contact support at **<support@aohwv.dev>** or visit the [AOH Sync support page](/help-and-support/contact.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/getting-started/getting-started.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.