> 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/archiv/update-sca-2.0-to-3.0.md).

# 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**](/sca-3.0-public-beta/whats-new-in-sca-3.0.md), 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](/sca-3.0-public-beta/app-config-policy-name-values-for-sca-3.0.md), 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](/sca-3.0-public-beta/whats-new-in-sca-3.0.md) are **opt-in** and must be explicitly enabled by administrators via App Configuration.
* [**Personal Outlook Contacts**](https://docs.secure-contacts.com/archiv/pages/6SFaCpH5zzgdT7Q8fct1#create-and-edit-personal-outlook-contacts-in-sca-3.0) **(special case)**: To allow users to create, edit, and delete personal Outlook contacts directly in SCA, admins **must grant the** [`Contacts.ReadWrite`](https://docs.secure-contacts.com/archiv/pages/6SFaCpH5zzgdT7Q8fct1#create-and-edit-personal-outlook-contacts-in-sca-3.0) **permission** in the Secure Contacts App - Azure AD enterprise app. ⚠️

{% hint style="success" %}
If you do not want users to edit their own personal Outlook contacts in SCA, disable the feature by setting:\
`APCeditor_Enabled = false`
{% endhint %}

For a complete overview of all new features and improvements, see [What’s New in SCA 3.0](/sca-3.0-public-beta/whats-new-in-sca-3.0.md).

### 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.


---

# 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/archiv/update-sca-2.0-to-3.0.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.