> For the complete documentation index, see [llms.txt](https://docs.reveald.com/technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveald.com/technical-documentation/data-sources/azure-services/register-epiphany-as-an-application-in-azure.md).

# Register Epiphany as an Application in Azure

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

#### Step 1:&#x20;

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

![App registrations page. Select New registration in the command bar.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2FNFqbuke2TjnjIiiuZ2Ua%2FPastedGraphic-9.png?alt=media\&token=bd63ac2b-211e-4992-a731-f83bf84c2b65)

#### 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.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2F58fYRQvHNJpBVUeJS3AV%2FPastedGraphic-10.png?alt=media\&token=95e0c2f8-7334-4897-9fbd-52c02f6ef7d8)

#### 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.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2FSqxr5HjD4CCOBXQBMFhu%2FPastedGraphic-11.png?alt=media\&token=08a7cec7-a31d-4bf3-b9de-84ecb238115f)

* 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.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2FiQMfSsuq1EVvC4t3b5oH%2FPastedGraphic-12.png?alt=media\&token=19078f11-6588-4e7d-baf8-142bd04eddc8)

* 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.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2FnwtI3JgM9fB5lEwNsSXr%2FPastedGraphic-13.png?alt=media\&token=19d81a0b-812d-4f1e-ad1d-aa12b2d7e485)

* 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.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2F4dqdapCZuXC7EZZEki03%2Fimage.png?alt=media\&token=e7b84bab-aefd-4ac0-8667-9e75c44d1fa7)

{% 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.](https://4132260347-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftkp3obVDMu3n9ZTUpfEP%2Fuploads%2Fcb19ruTfm4PfGum5AHBm%2FPastedGraphic-14.png?alt=media\&token=b771cbc6-964f-48bc-878e-c5103caa4f32)
