Syncing Entra ID contacts

Connect the Entra ID directory connector to sync your organisation's people into emu.chat as contacts.

Written By EmuChat

Last updated About 16 hours ago

The Entra ID connector keeps a contact list in emu.chat in step with your organisation's Microsoft Entra ID (Azure AD) directory. Once an administrator connects it, emu.chat syncs your directory's people into a shared contact list every hour, so your team always has up-to-date contacts to message. This is a workspace-level integration: only a workspace administrator can set it up, and there is one Entra ID sync per workspace.

Before you start

You need to be a workspace administrator. If you are not, the Entra Id card on the Integrations page is disabled, with a tooltip asking you to Ask your admin to configure it.

Connecting the directory also requires admin consent in Microsoft, so it helps to have permission to grant your organisation's Microsoft access (or to know who can).

Connect Entra ID

  1. Go to Integrations and select the Entra Id card.

  2. If emu.chat does not yet have access to your directory, you are prompted that Microsoft permissions required. Click Grant permissions.

  3. You are redirected to Microsoft to authorise emu.chat. Sign in as an administrator and approve the request. emu.chat asks only for read access to your directory's users (the Microsoft Graph User.Read.All permission).

  4. After you approve, Microsoft returns you to the Integrations page, where the configuration options are now available.

Note: Granting access needs an administrator to consent on behalf of your organisation. If you do not have that authority in Microsoft, ask whoever manages your tenant to complete this step.

Choose what syncs

Before saving, you decide how directory fields map to contact fields and how emu.chat should handle changes over time.

  • Field Mappings: match each directory field to a contact field in your workspace. By default, first name, last name, email, mobile phone, and company are mapped from the matching directory fields. Other directory details such as job title, department, and office location are also available to map.

  • Conflict Resolution: choose what happens when a contact exists in both systems. Always update from source overwrites local edits with the directory's values on each sync. Keep local changes preserves edits made in emu.chat and only fills in fields that are empty.

  • Deletion Behavior: choose what happens when a person is removed from the directory. Unlink keeps the contact but removes its link to the directory. Hard Delete permanently deletes the contact.

When you are happy with the settings, click Save Configuration. Syncing starts automatically and then runs every hour. There are no further approval or verification steps.

Where synced contacts live

Synced people are added to a contact list named <Org Name> Users (your organisation's name followed by Users), with the description Synced contacts. This list is shared across your workspace, so every member can see and message the contacts in it.

To understand how this shared list behaves alongside your other lists, see Personal vs shared contacts.

Keep contacts up to date

emu.chat syncs automatically every hour, picking up only what has changed since the last run. You can also sync on demand from the Sync Status area:

  • Sync Now runs an immediate update of recent changes.

  • Full Resync re-reads your whole directory from scratch, which is useful if something looks out of step.

The same area shows the current state of your sync, including totals and when it last started and completed.

Related