Administration

Active Directory integration

Provision users and extensions straight from your Active Directory.

Managing user accounts across two separate systems creates work that adds up quietly: a new hire joins and someone has to remember to add them to the phone system, a person leaves and their extension stays active longer than it should. Voxbi's directory integration connects your Microsoft 365 tenant to your phone system so that the people, groups, and sign-in rules you already maintain in one place flow through to the other.

The integration covers user and contact synchronisation and single sign-on. Once it is configured, your Microsoft 365 administrator grants the required permissions once, and Voxbi keeps things aligned. Staff log into the Voxbi Cockpit and the Voxbi app with the same credentials they use everywhere else, and provisioning a new user no longer means a separate round trip to the phone system.

When you'd use Active Directory

  • A company running Microsoft 365 that wants to provision phone extensions from the same directory it uses for email and Teams, without maintaining a separate user list in the phone admin panel.

  • An IT team that needs single sign-on across all business tools so staff aren't managing a separate Voxbi password, and so leavers lose phone access the moment their Microsoft account is disabled.

  • An organisation where contacts and presence information from the Microsoft directory should be visible in the phone system, so agents see a caller's details without switching apps.

How Active Directory works in Voxbi

  1. Create the Microsoft 365 integration

    In the Voxbi Cockpit, add a new integration of type Microsoft 365. An administrator from your Microsoft 365 tenant then grants the required admin consent, which authorises Voxbi to read the directory data it needs.

  2. Choose what to synchronise

    Turn on users sync to pull Microsoft 365 accounts across to the phone system, contacts sync to bring in directory contacts for call tracking, and user contact sync to create a phone-system contact for each provisioned user.

  3. Enable single sign-on

    In PBX Settings under the Authentication tab, activate single sign-on and point it at your identity provider. Staff then log in with their existing Microsoft credentials rather than a separate Voxbi password.

  4. Monitor the connection status

    The Integrations screen in the Voxbi Cockpit shows whether the link is connected, pending, or flagged with an error, so your IT team can spot a broken sync before it causes a support call.

Frequently asked questions

What permissions does the Microsoft 365 integration require?

The integration requires an admin consent grant from a Microsoft 365 administrator in your tenant. This is a one-time step that authorises Voxbi to read user and contact data from your directory. Once granted, the sync runs automatically.

Does single sign-on work for both the Voxbi Cockpit and the Voxbi app?

Single sign-on is configured at the PBX level in the Voxbi Cockpit and applies to administrator and user logins. The authentication tab in PBX Settings lets you map identity provider attributes to Voxbi user fields, so the right account is matched on first login.

What happens to a user's phone extension when their Microsoft account is disabled?

Because Voxbi reads from your Microsoft 365 directory, disabling or removing a user in Microsoft 365 means they are no longer synchronised as an active user in Voxbi. Administrators retain full control over the enabled or disabled state of each user from the Voxbi Cockpit as well.

Can we use the directory integration without enabling single sign-on?

Yes. User sync and contacts sync operate independently of single sign-on. You can synchronise directory data to keep your phone system's user list accurate while still allowing staff to log in with separate Voxbi credentials, or you can enable both together.

See Voxbi in your business.

Talk to us or to a certified Voxbi partner.