Public Beta - Quickstart
Information about the SCA 3.0 public beta test
Welcome to the public beta of SCA 3.0.
Discover what’s new in this release - click here to learn more.
Downloading the Beta Version
The beta version of Secure Contacts 3.0 can be downloaded via Apple’s TestFlight app or the Google Play Store.
iOS link: SCA 3.0 beta @ Apple's TestFlight
Android link: SCA 3.0 beta @ Google's PlayStore
Installation Prerequisite: To install the SCA 3.0 Beta, users must be allowed to install new apps on their device. This must not be restricted by MDM (Mobile Device Management) policies.
Installing the SCA 3.0 Beta
On iOS, the beta version can be installed manually for both management types:
Managed Apps (MAM)
Managed Devices (MDM) with some limitations
On Android, the beta version can only be installed manually for management type:
Managed Apps (MAM)
Note: Pushing or auto-install of beta versions via your MDM system will not work. Most MDM solutions require that apps come from the official app stores. Therefore, beta versions must be manually installed.
Installing SCA 3.0 Beta will overwrite any existing SCA 2.0 installation on the user's device.
App Configuration for SCA 3.0 Beta
Secure Contacts 3.0 uses the same AppConfig settings as version 2.0. Any existing configurations for SCA 2.0 in your policies will still be recognized. As well as your SCA License.
With version 3.0, additional AppConfig settings have been introduced, and some legacy ones have been removed. Please refer to the documentation for details.
When using management type "Managed Apps" (MAM), whether on iOS or Android, SCA 3.0 can access and apply AppConfig policy settings without issue.
When using management type "Managed Devices" (MDM) on IOS, certain limitations may apply - particularly if SCA 2.0 is already defined as the target version in your MDM system configuration.
Some MDM systems (e.g., Microsoft Intune and others) may not apply AppConfig settings if a different app version is installed on the device than the one defined in the MDM system. This can lead to errors such as “no applicable,” meaning the AppConfig will no longer be actively pushed.
What does this mean?
If you install SCA 3.0 over SCA 2.0, the older AppConfig might still be on the device. SCA 3.0 will be able to use this exact configuration since it was transferred before the update, even if the MDM doesn't push it again.
However, if you need to modify or customize the AppConfig for use with SCA 3.0, while SCA 2.0 is still defined as the target version in your MDM system, follow this sequence:
Ensure SCA 2.0 is installed on the device.
Make and save your changes in the AppConfig settings via your MDM system.
Verify that the updated configuration is successfully applied to the device.
Once confirmed, install SCA 3.0 over the existing SCA 2.0.
This ensures that the updated AppConfig is present and will be recognized by SCA 3.0.
This limitation only applies to management type Managed Devices (MDM) for iOS
Why is this important?
Because some of the new features in SCA 3.0 need to be activated or configured before they can be used. Additionally, the app license is delivered via AppConfig policies, and most of the key features in SCA 3.0 require a valid license to function properly.
Note: This AppConfig limitation for Managed Devices (MDM) will no longer apply once SCA 3.0 is officially released to the public app stores and defined as the target version in your MDM system.
Create and Edit personal outlook contacts in SCA 3.0
With SCA version 3.0, users can now create, edit, and delete their personal Outlook contacts directly in the app.
To enable this feature, an administrator must grant consent for the newly added permission Contacts.ReadWrite to the SCA Enterprise App.
Go to https://entra.microsoft.com and sign in with a Global Administrator or Privileged Role Administrator account. In the left menu, select Enterprise Applications, then find and select Secure Contacts App. Open Permissions, click Refresh, and then click on Grant admin consent for …. Wait a few seconds, then verify that the permission with the claim value Contacts.ReadWrite appears in the list and is marked as granted. Done.
Note: This action is only required if the SCA Enterprise App has already been registered and used in your Azure tenant.
If the SCA Enterprise App is being registered for the first time, no further action is required - all current permissions, including Contacts.ReadWrite, will be included automatically.
Last updated
Was this helpful?