Platform, Security & Integrations / Integrations

Directory Sync (LDAP / Active Directory)

Your phone system can sync directly with your company’s existing directory — Active Directory or Azure AD (Microsoft’s system for centrally managing employee accounts, also known as Entra ID — see Glossary) — so employee accounts, groups, and contact information stay accurate automatically, instead of being entered twice.

What problem does this actually solve?

Without it, someone has to manually create, update, and delete phone-system user accounts every time an employee joins, changes department, or leaves — a common source of stale accounts and admin busywork. With directory sync, your existing employee directory becomes the single source of truth, and the phone system follows it.

What happens when someone joins or leaves the company?

When a new employee is added to your directory, their phone-system account and extension can be provisioned automatically. When someone leaves and is removed or disabled in the directory, their access follows suit — reducing the risk of an ex-employee retaining phone system access.

Does this work with directory systems other than Microsoft’s?

Yes — LDAP (Lightweight Directory Access Protocol — a standard method for looking up directory/contact information — see Glossary) support means this works with LDAP-compliant directory systems generally, not just Active Directory or Azure AD specifically.

Does group structure carry over too?

Yes — department and group structure from your directory can sync through as well, which is useful for keeping ring groups, permissions, and internal directories organized without maintaining them separately in two places.

Is this the same as Single Sign-On?

They’re related but different. Directory sync keeps user accounts and data aligned with your directory. Single Sign-On lets employees log in using their existing company credentials rather than a separate phone-system password. Most businesses use both together.