What is a Directory Import? #
A directory import is used to import information from a 3rd-party source into the ISI Analytics directory. Directory Imports are useful for automatic directory management and updates.
Recommended Directory Imports per Data Source #
A list of our most common Data Sources and our recommended automated directory import sources can be found below.
| Common Data Source Types | Entra ID | UCM** | UCM + LDAP** | LDAP** | Webex | File Import |
| Avaya | N | N | N | Y | N | Y* |
| Cisco UCM | N | Y | Y | N | N | Y* |
| Webex DI | N | Y | Y | N | N | Y* |
| Webex MT | N | N | N | N | Y | Y* |
| Microsoft Teams | Y | N | N | N | N | Y* |
Important Notes:
- Y*: Can be used if the recommended Directory Import sources are not maintained.
- **: Requires Cloud Connect.
Supported Automated Directory Imports #
While we do have our recommendations, we support various directory import sources per data source. Listed below is a list of supported directory import sources per data source.
| Common Data Source Types | Entra ID | UCM** | UCM + LDAP** | LDAP** | Webex | File Import |
| Avaya | Y | N | N | Y | N | Y |
| Cisco UCM | Y | Y | Y | Y | N | Y |
| Webex DI | Y | Y | Y | Y | N | Y |
| Webex MT | Y* | N | N | Y* | Y | Y |
| Microsoft Teams | Y | N | N | Y | N | Y |
Important Notes:
- Y*: Extensions within Webex MT data are sent in an E.164 format. Choosing either directory import source will require configurations to be made to the user’s extension to match the E.164 format in the data.
- **: Requires Cloud Connect.
If you have questions regarding a supported data source not listed here, please reach out to our Support Team for more information.