> 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.md).

# Windows (Intune-managed) Steps to activate SCA in your Entra Tenant

This guide is intended for Microsoft Intune administrators preparing SCA for Windows.\
\
SCA Desktop uses Microsoft Entra ID for authentication and a device management solution for centralized deployment and configuration.\
\
Latest Releases of SCA Desktop can be downloaded from:

{% embed url="<https://github.com/Provectus-Software-GmbH/SCA_Desktop_Releases/releases/latest>" %}

## Preconditions

You need a Microsoft Entra ID tenant, administrative access for Enterprise Application consent, and Microsoft Intune for the deployment described by this guide.

The Enterprise Application reference describes consent using a Global Administrator account. \
Your Intune administration permissions must be handled separately within your RBAC concept.

You need a valid SCA license and a user with access to the intended contact sources. \
SCA reads contact data in the context of the signed-in user.\
\
You need additionally an Entra-Security Group with your test user as Member.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="https://app.gitbook.com/o/ppfQqpWS3ym5iPtSC6tM/sites/site_KXI4X/s/4v109br9tFl1Rxk2qP0x/~/edit/~/changes/873/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-1-register-enterprise-app">Step 1 -Windows- Register Enterprise App</a></td><td><br>Register Enterprise App with your tenant-ID from our website.</td><td></td><td><a href="/quickstart-guide/android-android-enterprise-steps-to-activate-sca-in-your-azure-tenant-1/step-1-register-enterprise-app.md">Step 1 -AE- Register Enterprise App</a></td></tr><tr><td><a href="https://app.gitbook.com/o/ppfQqpWS3ym5iPtSC6tM/sites/site_KXI4X/s/4v109br9tFl1Rxk2qP0x/~/edit/~/changes/873/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-2-windows-add-app-configuration-policy">Step 2 -Windows- Add App Configuration Policy</a></td><td><p></p><p>Create an App Configuration Policy for licensing.</p></td><td></td><td><a href="/quickstart-guide/android-android-enterprise-steps-to-activate-sca-in-your-azure-tenant-1/step-2-add-app-configuration-policy.md">Step 2 -AE- Add App Configuration Policy</a></td></tr><tr><td><a href="https://app.gitbook.com/o/ppfQqpWS3ym5iPtSC6tM/sites/site_KXI4X/s/4v109br9tFl1Rxk2qP0x/~/edit/~/changes/873/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-3-windows-deploy-sca-with-intune">Step 3 -Windows- Deploy SCA with Intune</a></td><td></td><td>Deploy the App to your Users</td><td></td></tr><tr><td><a href="https://app.gitbook.com/o/ppfQqpWS3ym5iPtSC6tM/sites/site_KXI4X/s/4v109br9tFl1Rxk2qP0x/~/edit/~/changes/873/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-4-windows-onboard-and-verify-your-test-device">Step 4 -Windows- Onboard and verify your Test device</a></td><td></td><td>Verifiy if your configuration applied on the Test device</td><td></td></tr></tbody></table>

{% hint style="info" %}
See [Editions](https://docs.secure-contacts.com/introduction/editions) for license editions and [SCA Configuration - SecContacts.Licenses](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.licenses) for licensing information.
{% endhint %}

{% hint style="success" %}
In case you have further questions, see our [Frequently Asked Questions (FAQ)](https://docs.secure-contacts.com/additional-information/frequently-asked-questions-faq). Contact and trial-license links are available under [Links](https://docs.secure-contacts.com/additional-information/links).
{% 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.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.