Zum Inhalt springen
EBF Documentation

EBF product documentation

Find help using and administering EBF applications

EBF Contacts

  • Release Notes
  • 01. What is EBF Contacts
  • 02. Requirements
  • 03. Get EBF Contacts up and running in few steps
  • 04. App usage by end user
  • 05. Contact
View Categories
  • Home
  • Homepage
  • EBF Contacts

03. Get EBF Contacts up and running in few steps

2 min read

03.1. EBF Contacts with Exchange O365/Azure

    • Prepare an AppConfig or similar configuration for the App in your EMM system and provide the current App version from AppStore via EMM system to your user’s device.
    • Mandatory parameters (key/value pairs) are “customerName”, “licenseKey”, “licenseCount” and “endpoint”. Add additional parameters as needed. An example config XML file and a description of all the parameters can be found in chapter 02.3.
    • Fill “customerName”, “licenseKey” and “licenseCount” as provided by your EBF contact person.
    • For filling the parameter “endpoint” register an Application ID in your organization’s Azure instance with the needed permissions described in chapter 02.3.
    • On first start of the App the user needs to activate EBF Contacts in the phone settings (only for iOS/iPadOS) as described to allow identification of callers. Then the user must create an encryption key and may activate Touch-/Face-Id for more comfort. Afterwards he needs to enter his AD credentials to connect to O365/Azure, if not using anonymous authentication.

03.2. EBF Contacts with Exchange On-Premise

  • Prepare an AppConfig or similar configuration for the App in your EMM system and provide the current App version from AppStore via EMM system to your user’s devices.
  • Mandatory parameters (key/value pairs) are “customerName”, “licenseKey”, “licenseCount” and “endpoint”. Add additional parameters as needed. An example config XML file and a description of all the parameters can be found in chapter 02.3.
  • Fill “customerName”, “licenseKey” and “licenseCount” as provided by your EBF contact person.
  • For filling the parameter “endpoint” enter the URL to reach your Exchange On-Premise instance. Make sure a secure connection from the user’s device to your Exchange server is established via VPN.
  • On first start of the App the user needs to activate EBF Contacts in the phone settings (only for iOS/iPadOS) as described to allow identification of callers. Then the user must create an encryption key and may activate Touch-/Face-Id for more comfort. Afterwards he needs to enter his AD credentials to connect to Exchange.

03.3. EBF Contacts with HubSpot

  • Prepare an AppConfig or similar configuration for the App in your EMM system and provide the current App version from AppStore via EMM system to your user’s devices.
  • Mandatory parameters (key/value pairs) are “customerName”, “licenseKey”, “licenseCount” and “hubSpotToken”. Add additional parameters as needed. An example config XML file and a description of all the parameters can be found in chapter 02.3.
  • Fill “customerName”, “licenseKey” and “licenseCount” as provided by your EBF contact person.
  • For filling the parameter “hubSpotToken” create a “private application” in the HubSpot admin portal.
    Go to “Settings” → “Account Setup” → “Integrations” → “Private Apps” and assign read rights for contacts (crm.objects.contacts.read)
  • On first start of the App the user needs to activate EBF Contacts in the phone settings (only for iOS/iPadOS) as described to allow identification of callers. Then the user must create an encryption key and may activate Touch-/Face-Id for more comfort. Synchronization of data should start automatically without user credentials.

03.4. EBF Contacts with ZIP file (CSV/JSON)

  • Prepare an AppConfig or similar configuration for the App in your EMM system and provide the current App version from AppStore via EMM system to your user’s devices.
  • Mandatory parameters (key/value pairs) are “customerName”, “licenseKey”, “licenseCount” and “zipUrl”. Add additional parameters as needed. An example config XML file and a description of all the parameters can be found in chapter 02.3.
  • Fill “customerName”, “licenseKey” and “licenseCount” as provided by your EBF contact person.
  • For filling the parameter “zipUrl” provide a ZIP file according to chapter 02.11. to a publicly available location (use ZIP encryption and the parameter “zipPassword” in this case) or to an intranet location and make sure EBF Contacts can reach this ZIP file via VPN. You can add as many CSV/JSON files to this ZIP as you like to be loaded into EBF Contacts.
  • On first start of the App the user needs to activate EBF Contacts in the phone settings (only for iOS/iPadOS) as described to allow identification of callers. Then the user must create an encryption key and may activate Touch-/Face-Id for more comfort. Synchronization of data should start automatically without user credentials.
Was this article useful?
Still stuck? How can we help?

How can we help?

Updated on 6. Februar 2024
02. Requirements04. App usage by end user
Navigate through page
  • 03.1. EBF Contacts with Exchange O365/Azure
  • 03.2. EBF Contacts with Exchange On-Premise
  • 03.3. EBF Contacts with HubSpot
  • 03.4. EBF Contacts with ZIP file (CSV/JSON)
Subscribe for EBF Newsletter
©2020 EBF-EDV Beratung Föllmer GmbH, All Rights Reserved
Imprint Terms and Conditions Privacy Statement Contact
Facebook-square Twitter-square Linkedin Xing-square Instagram
EBF Status Check