> 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/multi-factor-authentication-support.md).

# Multi-Factor Authentication Support

<code class="expression">space.vars.PRODUCT\_NAME</code> supports Microsoft 365 modern authentication and multi-factor authentication through the online sign-in form. When a user is prompted by <code class="expression">space.vars.PRODUCT\_NAME</code> to authorise with Microsoft 365, they should click the link 'authenticate with Office 365 via the online form'.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FxVNjF3tItbwBgP9TZfTu%2Fimage.png?alt=media&amp;token=f785bc1d-e638-48b0-8ac3-ebe65cdab4fb" alt=""><figcaption></figcaption></figure>

After clicking the link, the online sign-in form will pop up for the user to authenticate online. The manner of authentication is dependent upon how your organisation and the user has configured their authentication in Microsoft 365/Microsoft Entra.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FX3lxmgHetNJmUEXmNMrq%2Fimage.png?alt=media&amp;token=4082bf54-cdb8-47c8-8ed6-9c6abb1755dc" alt=""><figcaption></figcaption></figure>

After signing in, if the user has multi-factor authentication enabled they will be prompted for their second factor of authentication.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FRWZA9863rsc2i81sDILu%2Fimage.png?alt=media&amp;token=a78bfbbb-5954-4bf8-b2b8-b3df5a1189d2" alt=""><figcaption></figcaption></figure>

The online form will close and <code class="expression">space.vars.PRODUCT\_NAME</code> will complete the authentication.

<figure><img src="https://4182749601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBkDVFDwNmEHlZv1KwwiY%2Fuploads%2FnOpSDnQF6Pil7pRsoTXL%2Fimage.png?alt=media&amp;token=6956900f-c98e-44c3-a250-64427573f509" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If your organisation has single sign-on with ADFS or Entra joining, then users will not be prompted to authenticate, authentication will be automatic. See [Single Sign-On and Entra ID Token Protection](/feature-guide/single-sign-on-and-entra-id-token-protection.md)
{% endhint %}


---

# 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.zeedrive.com/feature-guide/multi-factor-authentication-support.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.