> 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/authentication/passwordless-for-web-apps/use-cases/entra-passkey-for-frontline-workers.md).

# Entra Passkey for Frontline Workers

1Kosmos enables frontline workers to authenticate into Microsoft Entra using a passkey verified through LiveID biometric (selfie).

***

### Overview

Identity is confirmed in real time - ensuring only the verified individual gains access, not just a trusted device or credential.<br>

### What it is

This use case lets frontline workers sign in to Microsoft Entra using a passkey that is verified with a LiveID biometric selfie, rather than a password alone. Because authentication is tied to a live facial biometric, access is confirmed in real time for the verified individual - not just for a trusted device or credential.

### How it works

This integration supports two delivery channels depending on your deployment scenario:

* **Mobile** — for field workers on Intune-managed iOS devices
* **Browser** — for desk-based workers using Chrome

Both channels use the same underlying PassKey + LiveID authentication workflow. Before configuring either channel, ensure the following are in place.

### Prerequisites

* A 1Kosmos tenant with a community configured
* Users provisioned in Microsoft Azure AD
* LiveID enrolled and passkey registered for each user via the Registration workflow
* Access to AdminX&#x20;
* Authentication workflow (`PassKeyWithLiveID`) deployed and active, with a valid access code


---

# 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/authentication/passwordless-for-web-apps/use-cases/entra-passkey-for-frontline-workers.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.