# About Integrated Directory Services

Integrated Directory Services are supported for the following integrations:

- MiCollab with MiVoice Business

- MiCollab with MiVoice 5000 or MiVoice MX-ONE

- MiCollab with MiVoice Office 250 or Non-Mitel PBX

- Active Directory Authentication

- External Directory Access

## MiCollab with MiVoice Business

You can integrate the user database of a corporate directory service with the MiCollab database to minimize data entry and administration. The user data and MiCollab Client contacts on the corporate directory server are synchronized with the MiCollab database using Lightweight Directory Access Protocol (LDAP). If Flow Through Provisioning is enabled, then MiCollab distributes the user data to the MiVoice Business platforms. Synchronization occurs in one direction only—from the directory server to MiCollab.

On the directory server, you can assign an attribute ("employeeType" by default) to each user data record. The "employeeType" attribute maps to a "role" in the MiCollab database which corresponds to a MiCollab user template. The user template allows you to apply additional personal data, telephone services, and application services to the user entry.

MiCollab detects updates that are made on the directory server via polling. MiCollab polls the directory server on a pre-specified interval or on-demand. Figure 1 illustrates how the directory service data is synchronized with the MiCollab and MiVoice Business.

Figure 1: Directory Service Data Synchronization with MiCollab

If IDS fails to process a directory service update, the operation is sent to the detained queue. Operations in the detained queue can have two states: detained or failed. Detained operations are operation that the system has not yet processed. These only occur if the detain-all option is enabled. Failed operations are operations that the system has been unable to process. You manage failed and detained operations from the Bulk User Provisioning Tool in the Users and Services application.

## MiCollab with MiVoice 5000 or MiVoice MX-ONE

For integrations with these communications platforms, Integrated Directory Services supports the provisioning of contacts within the MiCollab Client application so that the contacts appear as entries in the MiCollab Client corporate directory. The contacts from the directory server are provisioned in the MiCollab Client corporate directory so that MiCollab Client users are able to "click-to-call" them. These contacts can be corporate or non-corporate numbers.

- On a site with MiVoice 5000 only, contacts are only synchronized from the directory service in the MiVoice 5000 server.

- On a site with MiVoice 5000 Manager, contacts can be synchronized either from the MiVoice 5000 Manager or from an Active Directory server, but not both.

- On a site with a MiVoice MX-ONE contacts are only synchronized via an Active Directory server.

The contacts are synchronized in one direction only, from the directory service to the MiCollab database. Flow Through Provisioning is not supported.

## MiCollab with MiVoice Office 250 or Non-Mitel PBX

For integrations with MiVoice Office 250, or Non-Mitel PBX communications platforms, Integrated Directory Services provisions the MiCollab database with user data and MiCollab Client contacts from the corporate directory server using Lightweight Directory Access Protocol (LDAP).

Data is synchronized in one direction only, from the directory server to the MiCollab database. Flow Through Provisioning is not supported.

## Active Directory Authentication

Y ou can configure the integrations described above with Active Directory Authentication. This feature allows users to log into their MiCollab applications interfaces (for example: MiCollab End User Portal) using their Active Directory server credentials (login name and password). See Configure Active Directory Authentication for details.