> 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/06-redirect-uri.md).

# Step 5 — Redirect URI

The final configuration step is to add the OAuth redirect URI to your App Registration. This tells Entra ID where to send users after they authenticate.

{% stepper %}
{% step %}
**Open your App Registration**

In the [Azure Portal](https://portal.azure.com), navigate to **Microsoft Entra ID** → **App registrations** and select the registration you created in [Step 1](/getting-started/02-app-registration.md).
{% endstep %}

{% step %}
**Add the redirect URI**

1. Go to **Authentication** → **Add a platform** → **Web**.
2. Set the redirect URI to:

```
https://<your-domain>/auth/callback
```

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

3. Click **Save**.
   {% endstep %}
   {% endstepper %}

{% hint style="success" %}
AOH Sync is now fully configured. Open `https://<your-domain>` in your browser to sign in for the first time.
{% endhint %}

## How to check it worked

The redirect URI appears in your App Registration's **Authentication** page under **Web** → **Redirect URIs**, and you can sign in to AOH Sync at `https://<your-domain>` without an authentication error.

## Related

* [Step 4 — First Login](/getting-started/05-first-login.md)
* [Step 9 — Run Your First Sync](/getting-started/10-first-sync.md)
* [Managing Your Instance](/getting-started/11-managing-your-instance.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/getting-started/06-redirect-uri.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.