> 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/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-3-windows-add-app-configuration-policy.md).

# Step 3 -Windows- Add App Configuration Policy

You need a valid license to onboard SCA with the features required by your organization.

{% hint style="success" %}
See [SCA Configuration - SecContacts.Licenses](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.licenses) to request a trial license key.
{% endhint %}

The license key and features for SCA are applied to Windows through an Intune configuration profile using a supplied Administrative Templates for SCA.

<br>

{% stepper %}
{% step %}

## Download files from github

* Download `secure-contacts.admx` and `secure-contacts.adml` from Github:

{% embed url="<https://github.com/Provectus-Software-GmbH/SCA_Desktop_Releases/tree/main/config/Windows/ADMX>" %}

{% endstep %}

{% step %}

### Import the SCA Administrative Templates

* In the Microsoft Intune admin center, go to **Devices → Windows → Configuration → Import ADMX**.

* Import `secure-contacts.admx` and its matching language file `secure-contacts.adml`.

{% hint style="warning" %}
Always use the ADMX and ADML files from the same SCA Desktop release.
{% endhint %}

* Wait until Intune reports the import status as **Available**.

{% endstep %}

{% step %}

## Create the Configuration Profile

* Go to **Devices → Windows → Configuration → Policies → Create → New policy**.

* Select:

| Platform      | Windows 10 and later              |
| ------------- | --------------------------------- |
| Profile type  | Templates                         |
| Template name | Imported Administrative templates |

{% endstep %}

{% step %}

### Create Profile

* Enter a name, for example **Secure Contacts App Configuration - Windows**.

* Switch to Configuration settings

* Open the imported Secure Contacts settings and configure the values required by your organization.

{% hint style="success" %}
Path to imported Settings:

Computer Configuration/Secure Contacts/Secure Contacts Settings
{% endhint %}

| Settings name | Value                                            |
| ------------- | ------------------------------------------------ |
| `Licenses`    | `[{"name":"license name", "key":"license key"}]` |

* Replace `<license name>` and `<license key>` with your license information.

{% hint style="warning" %}

### Use [App Configuration Policy - Name/Values for SCA](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca) as the reference for all configuration keys. Start with [SecContacts.Defaults](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults) and apply [SecContacts.Licenses](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.licenses) early.

{% endhint %}

{% endstep %}

{% step %}

### Finalize profile configuration

* Assign the configuration profile to your Windows test device group.

* Review the profile and select **Create**.
  {% endstep %}
  {% endstepper %}

{% hint style="success" %}
Configuration for Secure Contacts Desktop is finalized - Deployment of the App is the next step.
{% 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/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-3-windows-add-app-configuration-policy.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.