LogoLogo
Provectus Technologies GmbH
  • Introduction
    • Secure Contacts App (SCA) - Safe & GDPR Compliant
    • Technical / Security Overview
    • Editions
    • Requirements
  • Quickstart Guide
    • iOS (MAM) - Steps to activate SCA in your Entra Tenant
      • Step 1 -MAM- Register Enterprise App
      • Step 2 -MAM- Add App Protection Policy
      • Step 3 -MAM- Add Conditional Access Policy
      • Step 4 -MAM- Add App Configuration Policy
    • iOS (Intune Managed Device) - Steps to activate SCA in your Entra Tenant
      • Step 1 -MDM- Register Enterprise App
      • Step 2 -MDM- Add App Protection Policy
      • Step 3 -MDM- Add Conditional Access Policy
      • Step 4 -MDM- Add App Configuration Policy
    • Android (Android Enterprise) - Steps to activate SCA in your Entra Tenant
      • Step 1 -AE- Register Enterprise App
      • Step 2 -AE- Add App Configuration Policy
    • Android (aMAM) - Steps to activate SCA in your Entra Tenant
      • Step 1 -aMAM- Register Enterprise App
      • Step 2 -aMAM- Add App Configuration Policy
      • Step 3 -aMAM- Add App Protection Policy
      • Step 4 -aMAM- Add Conditional Access Policy
    • Additional Datasource for SCA
    • Best-Practice Guide for SCA
  • Enduser guide
    • iOS - Onboarding SCA
    • iOS - activate Caller Identification
    • iOS - Userguide
    • iOS - App Manual
      • Contacts page
      • Contacts Sync
      • Contact information
      • Contact settings menu
      • Side menu
      • Logviewer
      • Help menu
      • vCard
    • Android Enterprise - Userguide
  • Documentation
    • Authentication
      • Enterprise Application
      • Conditional Access
        • CA with SCA - Require Complaint Device
        • SCA with CA - Require App Protection Policy
    • Deployment SCA
      • iOS - App Installation
      • Android - App Installation
      • App Configuration
        • iOS - MobileDeviceManagement (MDM) protocol
        • Android - App Restrictions
        • AppConfigurationPolicies
          • iOS - App Configuration Policies - MAM Integration in Microsoft Intune
          • Android - App Configuration Policies - MDM Integration in Microsoft Intune
      • App Protection Policy - Integration in Microsoft Intune
        • APP - unmanaged Devices
        • APP - managed Devices
        • Requirement - Open phone-settings
        • Requirement - Open Maps app
        • Requirement - Open GoogleMaps app
        • Requirement - Open WebExTeams
        • Requirement - Open WhatsApp
        • Requirement - Open Facetime
        • Requirement - Open email-link from SCA in Outlook
      • Deployment for your Devices in Intune
        • Deployment iOS - MAM-WE - APP only
        • Deployment iOS MDM - Managed & Complaint Device
        • Deployment iOS MDM - Managed Device & APP
        • Deployment Android MDM - Managed Device
    • App Configuration Policy -Name/Values for SCA
      • SCA Configuration - SecContacts.Defaults
      • SCA Configuration - SecContacts.Licenses
      • SCA Configuration - AAD filters
      • SCA Configuration - AAD groups
      • SCA Configuration - Connect additional Datasource
      • SCA Configuration - Custom Datasource Names
      • SCA Configuration - CI Customization
    • Data Sources
      • AAD - Azure Active Directory
      • GAL - Global Address List
      • APC - Personal Outlook Contacts
      • D365 - Dynamics 365
      • DVRS - Dataverse
      • ABS - Azure Blob Storage
      • SMC - Shared Mailbox Contacts
    • Valid phone numbers for SCA
    • iOS and Android version of SCA in comparison
  • Additional Information
    • Troubleshooting
    • Frequently Asked Questions (FAQ)
    • Phone number handling defaults changed in release v2.0.19
    • Links
    • Product Page - Secure Contacts App
Powered by GitBook
On this page
  • SecContacts.ServiceUrls
  • SecContacts.AzureBlobStorage
  • SecContacts.SharedMailboxContacts

Was this helpful?

  1. Documentation
  2. App Configuration Policy -Name/Values for SCA

SCA Configuration - Connect additional Datasource

SecContacts.ServiceUrls

This setting is for adding service urls of custom dataverse datasources e.g. Dynamics 365.

  • Name: SecContacts.ServiceUrls

  • Value: [{"name":"<service ID>", "value":"<service URL>"}]

The Value property is a JSON Array of name value pairs. You can add one or multiple service urls here.

Replace <service ID> with the service ID of a customs datasource

  • e.g. D365 or DVRS

Replace <service URL> with the url of a customs datasource

  • e.g. https://provectus-lab.crm.dynamics.com

Currently "Dynamics 365" (D365) as well as "Dataverse" (DVRS) 'SCA default Table 'sca_contact_tables' is supported.

SecContacts.AzureBlobStorage

This setting is for defining an AZURE Blob Storage as optional datasource for contacts.

With Azure Blob Storage in combination with the Provectus Azure Blob Storage Connector (link here) you can easily get contacts from any onPrem Application into the Secure Contacts App as long as the onPrem Application can export it's contacts into an *.csv or *.json file.

  • Name: SecContacts.AzureBlobStorage

  • Value: [{"name":"<abs name>", "value":"<abs access key>"}]

The Value property is a JSON Array of name value pairs. You can add one or multiple azure blob storages here.

Replace <abs name> with the unique name to identify the Azure Blob Storage

  • e.g. ABS1

Replace <abs access key> with the access key for a particular Azure Blob Storage. The access key needs to be generate for each Azure Blob Storage individually via the Provectus Azure Blob Storage Connector.

  • e.g. Xt8TVki4+ndWtqSVTAXTNr(...)0UFWNuDo2du3wZ5w92a7w==

SecContacts.SharedMailboxContacts

This setting is for defining exchange online shared mailboxes as optional datasource for contacts.

  • Name: SecContacts.SharedMailboxContacts

  • Value: ["name":"<smc_name>", "value":"<smc_emailaddress>"}]

The Value property is a JSON Array of name value pairs. You can add one or multiple shared mailbox email addresses here.

Replace <smc_name> with the unique name to identify the shared mailbox

  • e.g. SCM1

Replace <smc_emailaddress> with the email address of a shared mailbox.

  • e.g. marketing@provectus-lab.de

If the SCA user is member of the shared mailbox configured here, then contacts stored in that shared mailbox will become available in SCA.

If the SCA user is NOT member of the shared mailbox configured here, then this setting is ignored by SCA and the user will not see any contacts stored in that shared mailbox.

Last updated 9 months ago

Was this helpful?