How to - Verify Configuation for SCA

How to Verify Config | Secure Contacts App (SCA)

Verifying the application configuration is a critical step after deployment or any policy change to ensure that the Secure Contacts App (SCA) is receiving and correctly interpreting the intended settings from the Unified Endpoint Management (UEM) solution (e.g., Microsoft Intune/Entra ID).

1. Using the Configuration Viewer

The most reliable method for verifying the applied configuration is through the hidden Service Menu in the SCA application. This menu includes a dedicated Configuration Viewer that displays the raw and parsed settings.

• Access Service Menu: Follow the procedure to enter the Service Menu.

• Navigate: In the Service Menu, locate and select the Configuration Viewer or App Config Status option.

• Review Policy: The viewer will display the active App Configuration Policy assigned to the user, including all key-value pairs.

Tip: Pay close attention to the Source of the configuration (e.g., "Intune Policy," "Default Settings"). This confirms that the UEM policy has successfully reached the device.

1. Key Configuration Parameters to Check

While the Configuration Viewer shows all parameters, certain keys are fundamental to SCA's operation and should be prioritized during verification.

Parameter Category Key Parameter Example Verification Check Data Sources DataSource_AAD_Enabled Must be set to True if Azure AD contacts are expected. Phone Formatting PhoneNumberParseCountryCode_Option Verify the country code is correct (e.g., DE for Germany) to ensure proper caller ID matching. Features Feature_CallerID_Enabled Must be set to True for iOS Caller Identification to function. Branding App_Title_Custom Check if the custom title is correctly displayed, confirming the policy is applied.

Hint: If a parameter is missing or shows an unexpected value, it indicates an issue with the UEM policy assignment or the parameter key name. Ensure the key name in the UEM console exactly matches the required SCA parameter name (case-sensitive).

1. Verifying End-User Experience

The final verification step is to confirm that the applied configuration translates into the correct end-user experience.

• Contact Count: Check the number of contacts displayed in the SCA. Does it match the expected count based on the enabled data sources and the user's group membership?

• Feature Availability: If a feature like Shared Mailbox Contacts was enabled, verify that the option to view or search these contacts is now visible to the user.

• Functionality Test: Perform a simple test, such as calling the device from a synced contact number, to verify that the Caller Identification feature is working as configured.

Caution: UEM policy propagation can take time (up to several hours). If the configuration is not immediately visible in the Configuration Viewer, force a device check-in via the UEM client or wait for the next scheduled sync interval before concluding there is an error. If the issue persists, check the UEM console for any policy deployment errors.