> 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/installation-setup/system-settings/azure-active-directory-settings.md).

# Azure Entra Settings

The Azure Entra settings allows you to setup a link between ngSurvey and your Entra tenant that will be used globally by ngSurvey to let Entra Directory users log into ngSurvey using their existing Entra credentials.

## 🔅Entra 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 Entra portal. 
* **`Authority`** Azure Entra Authority, if you don't have a custom Authority you may leave this value blank.
* **`Single signon`** Tries to login using existing Entra credentials if the user has previously logged in using its Entra credentials.    
* **`Automatic access to new users`** If you are dealing with a lot of users you may want to avoid having to add manually each [Entra user](/installation-setup/installation/azure-active-directory/untitled.md) from the [user management](/multi-user-management/users.md) interface. If automatic access is enabled ngSurvey will automatically let any successfully authorized Entra users access the administration section. Note that you may use the auto link option of the [Roles](/multi-user-management/roles.md) to automatically add a role to each new Azure Active Directory user.


---

# 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/installation-setup/system-settings/azure-active-directory-settings.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.