> 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/windows-workstation-mfa/deployment-scenarios/entra-joined-workstations.md).

# Entra Joined Workstations

Support for Microsoft Entra ID joined machines (formerly Azure AD joined) is on 1Kosmos product roadmap. This page will be updated when the feature is available.

***

### What to Expect

Entra ID joined machines are Windows devices that are joined directly to Microsoft Entra ID rather than to an on-premises Active Directory domain. This model is increasingly common in cloud-first and hybrid organisations where traditional domain infrastructure is being reduced or eliminated.

{% hint style="warning" %}
**Beta** This feature is currently in Beta and available for testing. The information below reflects planned scope and is subject to change. No configuration steps or user guidance are provided on this page until the feature reaches general availability.
{% endhint %}

### In the Meantime

For organisations that require MFA on Windows devices managed through Entra ID today, the following interim options may be applicable:

| Option                                     | Description                                                                                                                                                                                                                                                                                                                                                           |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hybrid Entra ID Join                       | Join machines to both on-premises AD and Entra ID; deploy the 1Kosmos Credential Provider using the standard domain-joined model                                                                                                                                                                                                                                      |
| Microsoft Entra ID external authentication | 1Kosmos integrates with Microsoft Entra ID as an external authentication provider for app and web access; see [1Kosmos + Microsoft Entra ID Integration](https://www.1kosmos.com/platform/resources/integrations/microsoft-entra-verified-id?utm_campaign=46345118-Developer%20Center\&utm_source=docsite\&utm_medium=website\&utm_content=entra-id-link) for details |


---

# 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/windows-workstation-mfa/deployment-scenarios/entra-joined-workstations.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.