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

# AAD - Azure Active Directory

\[AAD]

Azure AD is the **primary data source** in SCA and integrates your organization’s user profiles to provide access to company-wide contacts. Contacts are queried via the **Microsoft Graph API**, and accounts are managed in your [**Microsoft Entra ID (Azure AD) tenant**](https://entra.microsoft.com/).

#### App Configuration Parameters

**Defaults (**[**`SecContacts.Defaults`**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults.md)**):**

* [**AAD\_Enabled**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults.md#enable-or-disable-features) → Enables or disables the Azure AD data source.
* [**AAD\_InitValue**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults.md#initial-value-set-by-default) → Sets the default position of the user’s switch for this data source (on = shown, off = hidden) when SCA is first launched.
* [**AADuseUPNasEmail\_Option**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults.md#appearance-and-functions) → Determines whether to use User Principal Name (UPN) as the email address.
* [**AADonlyEnabledAccounts\_Option**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults.md#appearance-and-functions) → 🆕Filters contacts to include only enabled accounts.

**Customization / Organization:**

* [**SecContacts.AADGroups**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-aad-filters-and-groups-1.md) → Organize contacts into separate data sources based on Azure AD groups.
* [**SecContacts.CustomDatasourceNames**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.customdatasourcenames.md) → Assign friendly display names for the data source.

#### Requirements for Contacts

Any AAD contact to be shown in SCA **must have the following three fields populated**:

1. **First name**
2. **Last name**
3. **Valid phone number**

**Note:** Every AAD account in your tenant that meets these requirements will appear as a contact in SCA. Only **Member accounts** are included; **Guest accounts** are ignored.

{% hint style="success" %}

* Each data source, including AAD, can be **hidden by the user** if they do not want to see or use it.
* Hiding a data source does **not affect Caller Identification** — contacts from hidden sources will still resolve incoming calls.
* Use **AADGroups** to split contacts into multiple separate data sources (e.g., by department, region, or team).
  {% 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.secure-contacts.com/documentation/data-sources/aad-azure-active-directory.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.