Update SCA 2.0 to 3.0

After the Release of SCA 3.0

With the public release of Secure Contacts App (SCA) 3.0, here’s what administrators and end users need to know.

Updates & Compatibility

• Automatic Update: Devices running SCA 2.0 are upgraded to 3.0 through the App Store/Google Play. No manual uninstall is required.

• Seamless Transition: After the update, users only need to sign in again. A full re-enrollment is not required.

• Contacts & Settings: Contacts and configurations remain unaffected during the update. Favorites need to be reconfigured.

• Configuration Compatibility: All settings from SCA 2.0 continue to work in 3.0, including the license key. New options are available, and some new features require updated configuration.

• Managed Apps: On iOS and Android, auto-updates apply as with any managed app, though timing may depend on MDM/MAM policies.

New Features

• Most new capabilities in 3.0 are opt-in and must be explicitly enabled by administrators via App Configuration.

• Personal Outlook Contacts (special case): To allow users to create, edit, and delete personal Outlook contacts directly in SCA, admins must grant the Contacts.ReadWrite permission in the Secure Contacts App - Azure AD enterprise app. ⚠️

If you do not want users to edit their own personal Outlook contacts in SCA, disable the feature by setting: APCeditor_Enabled = false

For a complete overview of all new features and improvements, see What’s New in SCA 3.0.

What This Means

For Administrators

• Verify that the SCA enterprise app is registered and consented.

• Review App Configuration and enable new features as needed.

• Grant Contacts.ReadWrite if Outlook contact editing should be allowed.

• Check MDM/MAM policies to ensure app updates flow correctly.

For End Users

• SCA will update automatically to 3.0 when store updates are allowed.

• Existing settings remain in place, favorites need to be reconfigured.

• New features become available only if enabled by your administrator.