> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/entra-eam-beta.md).

# Entra EAM (Beta)

Enable passwordless, biometric login for Microsoft Entra External Authentication Method (EAM) users using 1Kosmos as an OIDC Identity Provider.

***

### Prerequisites

Before starting, make sure you have:

* **AdminX portal** — Admin access to your 1Kosmos AdminX tenant.
* **Microsoft Entra ID** — Admin access to configure an External Authentication Method.
* **1Kosmos mobile app** — Installed and enrolled on iOS or Android. ([Android](https://play.google.com/store) · [iOS](https://apps.apple.com/))
  * Biometrics (Touch ID / Face ID or LiveID) must be enrolled before testing.

***

### Step 1 — Create the OIDC Application in AdminX

1. Sign in to the AdminX portal and go to **Applications → Add Application**.

2. Under **Pre-built integrations**, click **Add Integration** on the **Entra EAM** card.

3. Fill in the following fields:

   | Field                          | Value                                                                      |
   | ------------------------------ | -------------------------------------------------------------------------- |
   | Application Name               | A unique name to identify this application (e.g., `default_EAM`)           |
   | Application Logo               | Upload a `.png`, `.jpg`, or `.gif` file, max 2MB                           |
   | Grant Type                     | `Implicit`                                                                 |
   | Signing Algorithm for ID Token | `RS256`                                                                    |
   | Sign-in Redirect URIs          | `https://login.microsoftonline.com/common/federation/externalauthprovider` |

4. Under **Scopes**, select what's required for your use case:

   | Scope                | Description                       |
   | -------------------- | --------------------------------- |
   | `openid`             | Required for OIDC authentication  |
   | `profile`            | User profile information          |
   | `email`              | User email address                |
   | `identity_assurance` | Identity proofing assurance level |
   | `/assurance/ial/2/`  | IAL2-level identity assurance     |
   | `extension:activate` | Extension activation scope        |

5. Under **Login Screen Customizations**, configure display options as needed:

   | Option                         | Description                                    |
   | ------------------------------ | ---------------------------------------------- |
   | Hide Banner                    | Hides the 1Kosmos banner on the login screen   |
   | Hide Mobile App Download Links | Removes app store links from the login screen  |
   | Change App Name                | Displays a custom app name on the login screen |

6. Toggle **Force Re-authentication** on if users should re-authenticate on every visit.

7. Click **Next** to save the application.

***

### Step 2 — Test the Connection

1. Open a browser and sign in to your Microsoft Entra-protected application.
2. When prompted for additional authentication, select the **1Kosmos** option.
3. You'll be redirected to the 1Kosmos login screen with a QR code.
4. On the 1Kosmos mobile app home screen, tap **Scan QR**.
5. Scan the QR code. When prompted, select **Allow only while using the app**.
6. Tap **Authenticate** and complete biometric verification (Touch ID, Face ID, or LiveID).
7. On success, you'll be signed in to your application.


---

# 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.1kosmos.com/integrations/authentication/pre-built-integrations/entra-eam-beta.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.