> 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/macos-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-4-macos-onboard-and-verify-your-test-device.md).

# Step 4 -macOS- Onboard and verify your test device

Complete these checks after the SCA PKG and preference profile are assigned to the test Mac. Record the tested application version, profile revision, device, and test account in your pilot results.

## Install and Start SCA

{% stepper %}
{% step %}

### Synchronize the device

* Use Company Portal on the Mac to synchronize with Intune. <br>
  {% endstep %}

{% step %}

### Verify installation and configuration status

* In Intune, open the SCA application and review its device installation status. <br>
  {% endstep %}

{% step %}

### Verify the installed application

* Confirm that the application exists at `/Applications/SecureContacts.app`.

Open Terminal and inspect its bundle identity:

```bash
/usr/libexec/PlistBuddy -c 'Print:CFBundleIdentifier' /Applications/SecureContacts.app/Contents/Info.plist
/usr/libexec/PlistBuddy -c 'Print:CFBundleShortVersionString' /Applications/SecureContacts.app/Contents/Info.plist
```

The first command must return `de.provectus.SecureContactsDesktop`. The second must match the approved package version and the Intune **Included apps** version.

If the app exists but Intune reports failed detection, compare these values before changing the app package or ignoring its version.
{% endstep %}

{% step %}

### Verify the effective managed preferences

* Read the device-level configuration:

```bash
defaults read "/Library/Managed Preferences/de.provectus.SecureContactsDesktop.plist"
```

* Check the presence of `SecContacts.Licenses` and the values you populated. \
  \
  Empty optional keys are expected when left unused.

{% endstep %}

{% step %}

### Start Secure Contacts App

* Launch **Secure Contacts** from Applications.&#x20;

* Confirm the app opens without an installer or Gatekeeper error.

{% endstep %}

{% step %}

### Sign in

* Sign in with the intended test user. Complete the authentication requirements imposed by your organization.<br>
  {% endstep %}

{% step %}

### Synchronize contact sources

* Allow SCA to load the enabled sources.

{% endstep %}
{% endstepper %}

## Verify SCA

{% stepper %}
{% step %}

### Search for contacts

* Search for a known contact from every contact source enabled for the test user.

{% endstep %}

{% step %}

### Verify contact information

* Open the contact and verify the expected contact information.

{% endstep %}

{% step %}

### Test enabled functions

Test the functions enabled for your deployment, for example:

* Email
* Phone or the configured default dialer
* Microsoft Teams chat, call, or video call
* Microsoft Teams status
* Incoming call detection, if enabled and activated

{% endstep %}

{% step %}

### Enjoy the app

{% hint style="success" %}
SCA is now activated, configured, and verified on your Windows test device. Expand the application and configuration profile assignments only after the pilot results are accepted.
{% endhint %}

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Settings ending in `_InitValue` are set when SCA starts for the first time. When validating a changed initial value, follow the test procedure in [SCA Configuration - SecContacts.Defaults](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults).
{% endhint %}

{% hint style="info" %}
The available functions depend on the assigned license, configured values, accessible contact sources, and applications installed on the Windows device. See [Quick Facts (Desktop)](https://docs.secure-contacts.com/introduction/quick-facts-desktop) for the documented desktop feature set.
{% 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/macos-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-4-macos-onboard-and-verify-your-test-device.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.