> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/security/security-items/azure-active-directory-security.md).

# Azure Active Directory Security

## 👥 What is Azure Active Directory Security ?

Using the Azure  security you can restrict access to your survey to users having a valid Azure Active Directory account. This security item can be setup to either allow single sign on to automatically sign in the respondents if they have already logged into Azure Active Directory or to let the users login manually using their Azure Active Directory credentials. 

## 🔅 Active Directory security properties

* **`Application (client) ID`** ID of the application that you have [setup](/installation-setup/installation/azure-active-directory/azure-active-directory-setup.md) and registered in your Azure Active Directory portal. If you leave it blank it ngSurvey will use the Application ID set globally in your [system settings](/installation-setup/system-settings/azure-active-directory-settings.md). 
* **`Authority`** Azure Active Directory Authority, if you don't have a custom Authority you may leave this value blank.

  **`Allow multiple submissions`** allows a respondent to take part multiple time to the same survey.
* **`Single sign on`** if respondents are already authenticated in Azure Active directory ngSurvey will automatically sign them into the survey.
* **`Authorization token lifetime`**defines in minutes how long ngSurvey will trust the authentication token generated by the user from Azure. Once expired the user will be required to log back in to submit the survey.

{% hint style="success" %}
This security item can be used as a [key provider](/form-management/security/key-provider-concepts.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.ngsurvey.com/form-management/security/security-items/azure-active-directory-security.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.