> 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/introduction/editions.md).

# Editions

Overview: Standard vs. Enterprise Editions of Secure Contacts App (SCA)

### Standard Edition

* **GDPR-compliant** handling of business contacts
* Integration with:
  * **Exchange Online** (EXO) - Personal Contacts
  * **Azure Active Directory -** Company Address Book
  * **Organizational contacts** - GAL
* **Central configuration** via Microsoft Intune or other MDM-System
* **Telephony and messenger integration** with:
  * Telephony, SMS, iMessage
  * Microsoft Teams
  * Microsoft Outlook
* **Optional integrations**:
  * WhatsApp
  * Signal
  * Telegram
  * WebEx

### Enterprise Edition

Includes **all features of the Standard Edition**, plus:

* **Integration of additional data sources**:
  * Shared Mailbox Contacts (EXO)
  * Microsoft Dynamics 365 - Contacts stored in Microsoft Dynamics 365
  * Microsoft Dataverse - Contacts stored by apps built on Microsoft Dataverse
  * Azure Blob Storage - Contacts exported from any app (incl. on-premises) via CSV/JSON
* **Contact enhancements**:
  * Display Microsoft Teams presence/status
  * Display Out-of-Office messages
  * Show organizational chart (reporting relationships)
  * Address fields with direct link to Maps app
* **Advanced functionality**:
  * Create, edit, and delete personal contacts within SCA
  * Safe contact export/sharing
  * Vacation Mode
  * Anonymized calling
* **Customization options**:
  * App CI (corporate identity/branding)
  * Additional messenger/telephony apps available on request
* **Extended platform support**:
  * Secure iOS / Siri / CarPlay integration via CPE (Contact Provider Extension)


---

# 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/introduction/editions.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.