Zum Inhalt springen
  • Blog
  • Cookie Policy (EU)
  • Datenschutzerklärung
  • EBF Docs
  • Onboarder Source and Target
  • Test
  • EBF product documentation

    Find help using and administering EBF applications

    EBF Contacts

    • Release Notes
    • 01. What is EBF Contacts
    • 02. Requirements and Configuration
    • 03. Get EBF Contacts up and running in few steps
    • 04. App usage by end user
    • 05. Contact
    View Categories
    • Home
    • EBF Docs
    • 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. Requirements and Configuration04. App usage by end user
    Table of Contents
    • 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)
    Linkedin-in Phone
    Workplace Management
    • UEM Solutions
    • Migrations
    • Services
    Modern Work Tools
    • Sync Contacts
    • Hybrid Data Management
    • Secure Mobile Printing
    • eSIM Management
    • App Management
    IT Security
    • IAM
    • Modern Threat Defense
    • Cyber Risk Management
    • Secure Development
    • Zero Trust
    • Security Check
    AI Solutions
    • AI Consulting
    • AI Development
    Company
    • About Us
    • References
    • Partners
    • Sustainability
    • Careers
    • Trends
    © 2026 EBF-EDV Beratung Föllmer GmbH
    • Privacy Policy
    • GTC
    • EULA
    • Imprint
    Manage Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Immer aktiv
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    • Optionen verwalten
    • Dienste verwalten
    • Verwalten von {vendor_count}-Lieferanten
    • Lese mehr über diese Zwecke
    View preferences
    • {title}
    • {title}
    • {title}
    EBF Status Check