# Register Epiphany as an Application in Azure

{% hint style="warning" %}
This document is under construction. Please excuse our dust.
{% endhint %}

#### Step 1: 

* Log in to Azure. 
* In the left navigation menu, under **Manage**, select **App** **registrations**. This displays existing applications and also allows you to create a new application. 
* In the command bar, select **+New** **Registration**. 

![App registrations page. Select New registration in the command bar.](/files/SL6jaJoeOnthJNpORApa)

#### Step 2:

* On the **Register an application** page, make the following settings:
  * **Name**: This is the public-facing name of the application and has no bearing on the application’s use within Epiphany. If you have a naming convention used by your organization, follow it, otherwise it is recommended that you use a name with which you can discern that the application is used by Epiphany. For example, **epiphany-azuread**.
  * **Supported account types**: This dictates the boundaries of access *to* the application being created.  The first option, **Accounts in this organizational directory only**, is recommended as it limits the scope of access.
  * **Redirect URI (optional)**. This isn't used. The default setting is fine so don't make any changes.
  * Select the **Register** button.

![Register an application page.](/files/O4Gnb10vtkIWppNNOAZk)

#### Step 3:

* A new page will show the name of the application you just registered (**epiphany-azuread** in this example). It shows the **Application (client) ID** and **Directory (tenant) ID**. Write these down because you'll need them when you add Azure AD credentials to Epiphany.

  <div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p>In Epiphany, these are called the <strong>Application ID</strong> and <strong>Tenant</strong> <strong>ID</strong>.</p></div>

* In the upper-right corner, under **Client credentials**, select **Add a certificate or secret** to create a secret.

![The application you just registered.](/files/3M2MeaiK9mzZ3yS9dL13)

* The **Certificates & secrets** page displays. Under **Client Secrets**, select **New client secret**.&#x20;

![On the Certificates & secrets page, under Client secrets, select New client secret.](/files/O7IOfOpFyf2fHVKSjuxU)

* The **Add a client secret** pane displays on the right. On the **Add a client secret** pane, make the following settings:
  * **Description**: Use a description that can be easily identified as a secret for Epiphany, unless your organization has a naming standard that requires that you use some sort of obfuscation or other method for descriptions.
  * **Expires:** The default expiration date is six months from the time of creation. However, you are encouraged to select an expiration period in alignment with your organization’s standards.

{% hint style="success" %}
It may be worthwhile to include the date in the **Description** to more easily identify the expiration date.
{% endhint %}

*

![The Add a client secret pane is on the right.](/files/dGuLG06xpJqc92BEC7jU)

* A display shows the generated secret. You must copy the **Value** before navigating to another page.&#x20;

{% hint style="danger" %}
If you don't copy the **Value** when it's first visible and before navigating to another page, you won't be able to see it again. You will need to repeat the steps above to create a new secret. &#x20;
{% endhint %}

![On the Client Secrets page, copy the Value.](/files/iavDOjuVoYcjwLPgsWRs)

{% hint style="warning" %}
A common mistake is to accidentally copy the **Secret ID** and not the **Value**.
{% endhint %}

![The value no longer displays once you navigate away from where you set it up.](/files/ekQLNIJvakph7wbaTPOL)


---

# Agent Instructions: 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:

```
GET https://docs.reveald.com/technical-documentation/data-sources/azure-services/register-epiphany-as-an-application-in-azure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.