> For the complete documentation index, see [llms.txt](https://docs.zeedrive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeedrive.com/feature-guide/single-sign-on-and-entra-id-token-protection.md).

# Single Sign-On and Entra ID Token Protection

<code class="expression">space.vars.PRODUCT\_NAME</code> supports SSO (single sign-on) experience for both Entra ID joined devices and ADFS joined devices, and Entra ID token protection (token binding).

<code class="expression">space.vars.PRODUCT\_NAME</code> subscription users on an Entra ID joined device or ADFS joined device will experience a seamless mapping of their <code class="expression">space.vars.PRODUCT\_NAME</code> network drives. When a user signs in to their Windows desktop, <code class="expression">space.vars.PRODUCT\_NAME</code> will start-up automatically, identify the user and sign the user in automatically to Entra ID. End user interaction is not required. Access tokens will subsequently be refreshed automatically to keep the network drives *always on*.

For organisations requiring additional security, <code class="expression">space.vars.PRODUCT\_NAME</code> is compatible with Microsoft Entra ID [conditional access token protection](https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-token-protection) (or token binding) on Entra ID joined devices. if your organisation enables token protection, then <code class="expression">space.vars.PRODUCT\_NAME</code> will continue to authenticate and issue tokens successfully from Entra ID on an Entra ID joined device.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zeedrive.com/feature-guide/single-sign-on-and-entra-id-token-protection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.