# App Configuration Policy -Name/Values for SCA

### Overview

The **Secure Contacts App (SCA)** supports configuration through **App Configuration Policies** provided by any Mobile Device Management (MDM) solution.\
With these policies, administrators can **customize app features, apply licenses, and specify which data sources SCA uses for contact synchronization**.

> Microsoft Intune is one common example of an MDM system that can deliver these policies, but SCA works with **any MDM platform** that supports standard key–value configuration.

By assigning the appropriate key–value pairs, you can centrally manage how SCA behaves across your organization.

### Main Configuration Keys

Below is an overview of the most commonly used configuration keys in SCA. Each key controls a specific feature or integration.

<table><thead><tr><th width="282.1429443359375">Configuration Key</th><th>Purpose</th></tr></thead><tbody><tr><td><a href="/pages/doZ8G3P50c1ykuVo5iO8"><strong>SecContacts.Defaults</strong></a></td><td>Customize app features and change default behavior.</td></tr><tr><td><a href="/pages/MdzEvXLRrfsBlBmAy6cU"><strong>SecContacts.Licenses</strong></a></td><td>Apply the app license.</td></tr><tr><td><a href="/pages/8D2OlTOatgYtgjl4JVp3"><strong>SecContacts.AADGroups</strong></a></td><td>Use Azure AD groups as separate contact sources within SCA.</td></tr><tr><td><a href="/pages/bf6qlzjqFL3ODEf6GONt#seccontacts.serviceurls"><strong>SecContacts.ServiceUrls</strong></a></td><td>Connect Microsoft Dataverse (DVRS) to use contacts stored by apps built on the Dataverse platform (e.g. Dynamics 365, Power Apps, etc.).</td></tr><tr><td><a href="/pages/l3ku470gJjjS1ucIS7wz"><strong>SecContacts.AzureBlobStorage</strong></a></td><td>Connect Azure Blob Storage (ABS) to use contacts exported from any app (including on-premises) via CSV/JSON using the SCA Blob Storage connector.</td></tr><tr><td><a href="/pages/d4Z004r5FHTPNK745aEK"><strong>SecContacts.SharedMailboxContacts</strong></a></td><td>Use Exchange Online shared mailboxes as an optional data source for contacts.</td></tr><tr><td><a href="/pages/MapUYDr96Lka6BOTA5uO"><strong>SecContacts.CustomDatasourceNames</strong></a></td><td>Rename any data source or ID in SCA to a more descriptive, user-friendly name.</td></tr></tbody></table>

A sample configuration for your App Configuration Policy could look like this:

<figure><img src="/files/AoSR08OLkcch1lZ8vybd" alt=""><figcaption><p>Note: This is just an example for illustration</p></figcaption></figure>

### Best Practice

* Start with [**SecContacts.Defaults**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults.md) to configure the basic app behavior that fits your organization.
* Apply [**SecContacts.Licenses**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.licenses.md) early so users are properly licensed from the start.
* Use [**SecContacts.AADGroups**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-aad-filters-and-groups-1.md) if you want to organize your Azure AD groups as **separate contact sources** within SCA.
* Apply [**CustomDatasourceNames**](/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.customdatasourcenames.md) to give your data sources clear and user-friendly names.
* Add [**ServiceUrls**](https://docs.secure-contacts.com/documentation/pages/bf6qlzjqFL3ODEf6GONt#seccontacts.serviceurls), [**AzureBlobStorage**](https://docs.secure-contacts.com/documentation/pages/bf6qlzjqFL3ODEf6GONt#seccontacts.azureblobstorage), or [**SharedMailboxContacts**](https://docs.secure-contacts.com/documentation/pages/bf6qlzjqFL3ODEf6GONt#seccontacts.sharedmailboxcontacts) only if you need extra contact sources beyond Azure AD.

{% hint style="success" %}
When you make changes to your app configuration, it may take some time for the updates to be applied to the device.

For apps protected by **Intune App Protection Policies (MAM without device enrollment)**, app configuration and protection policy updates are **typically applied within about an hour**. To force immediate application, the user must **log out and log back in** or **manually sync via the Company Portal**.
{% endhint %}

{% hint style="info" %}
**Note:** This delay applies only to **MAM (app protection) scenarios**. For fully enrolled **MDM devices**, app configuration and compliance policies are delivered through the device management channel and usually apply much faster. The delay with MAM is expected behavior and not an error.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
