Data Sources

The Secure Contacts App (SCA) can retrieve contacts from multiple sources. Some are available by default (“primary”), and others are optional.

All data sources can be enabled, disabled, or customized through App Configuration Policies in your MDM system. SCA always retrieves contact information exclusively from your organization’s own tenant and connected services.

SCA synchronizes on first launch and whenever a user pulls to refresh. During sync, it queries all enabled sources the user has permission to access.

Primary Data Sources

These are included by default but can be managed via app configuration:

Source	Acronym	Description	Typical Use Case
Microsoft Entra ID (formerly Azure AD)	AAD	Retrieves organizational user profiles from your tenant directory.	Core source for company user contacts.
Global Address List (OrgContacts / GAL)	GAL	Retrieves organization-wide shared contacts from Azure AD.	To access shared or widely used org contacts.
Personal Outlook Contacts	APC	Contacts stored in the user’s personal Exchange Online mailbox.	For including personal work-related contacts.

Optional Data Sources

These can be additionally enabled via app configuration policies:

Source	Acronym	Description	When to Enable
Dynamics 365	D365	Contacts stored in Microsoft Dynamics 365.	If your org uses Dynamics to manage customer or partner contacts.
Microsoft Dataverse	DVRS	Contacts stored by apps built on Microsoft Dataverse.	For custom or business apps using the Dataverse platform (e.g. custom CRM, Power Platform).
Azure Blob Storage	ABS	Contacts exported from any app (including on-premises) via CSV/JSON using the SCA Blob Storage connector.	If you want to integrate external contact data exported from any app (e.g. Lotus Notes, SAP, Excel-file, etc.)
Shared Mailbox Contacts	SMC	Contacts in Exchange Online shared mailboxes.	If teams use shared mailboxes and need those contacts in SCA.

Splitting Data Sources

SCA allows you to split data sources into multiple, separate sources for better organization and easier navigation. This can be useful, for example, to separate contacts by business unit, region, team, format, or origin system.

Ways to achieve this:

• AADGroups → make each Azure AD group appear as its own contact source.

• OData filters → use Microsoft Dynamics 365 or Dataverse API filters to split contacts (e.g. by region or data ownership).

• Azure Blob Storage (ABS) → use multiple CSV/JSON files within the same container, each representing a distinct contact dataset.

Where possible, use CustomDatasourceNames to give friendly display names to your data sources so end users clearly understand what they are seeing.