> 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/05-first-login.md).

# Step 4 — First Login

With DNS resolving, open the AOH Sync browser setup wizard to complete installation. The wizard takes approximately **10–15 minutes** to run.

{% stepper %}
{% step %}
**Open the setup wizard**

In a browser, navigate to:

```
https://<your-domain>/onboard
```

Replace `<your-domain>` with the domain you configured in [Step 3 — DNS](/getting-started/04-dns.md) — for example, `https://sync.yourcompany.com/onboard`.

The wizard pre-fills your **License Key**, **Domain**, and **Client ID** from the values you entered during the Marketplace deployment. You do not need to re-enter them.
{% endstep %}

{% step %}
**Enter your Azure AD credentials**

The wizard asks for the following:

| Field                                         | Where to find it                                                                                    |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Azure AD Tenant ID**                        | Azure Portal → **Microsoft Entra ID** → **Overview** → *Tenant ID*                                  |
| **Azure AD App Registration — Client Secret** | The secret value you copied in [Step 1 — App Registration](/getting-started/02-app-registration.md) |

{% hint style="info" %}
Your Client Secret is collected here — over TLS in the browser — rather than during the Marketplace deployment. This keeps the secret out of ARM deployment logs.
{% endhint %}
{% endstep %}

{% step %}
**Optionally supply a TLS certificate**

By default, AOH Sync obtains a TLS certificate automatically once DNS resolves. If you prefer to supply your own certificate, you can:

* Upload a `.crt` or `.pem` certificate file and its private key, or
* Paste your PEM-encoded certificate and key directly into the wizard

If you skip this step, AOH Sync will obtain a certificate automatically — no action required.
{% endstep %}

{% step %}
**Accept the terms and start the install**

Review and accept the terms of service, then click **Start install**.

The page shows live installation progress. The process takes approximately **10–15 minutes**. Keep the browser tab open during this time.

Once installation is complete, AOH Sync is live at `https://<your-domain>`.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
If the install fails or the page does not load, confirm that your DNS record has fully propagated and that the VM is in a **Running** state in the Azure Portal. Contact support at **<support@aohwv.dev>** if you need assistance.
{% endhint %}

## How to check it worked

After installation completes, the AOH Sync dashboard loads at `https://<your-domain>` when you open it in a browser.

## Related

* [Step 3 — DNS](/getting-started/04-dns.md)
* [Step 5 — Redirect URI](/getting-started/06-redirect-uri.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/05-first-login.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.