Caveats and Limitations
-----------------------

* When enabled, the local database is not searched, meaning that only LDAP users
  in the global directory are searchable - local CUCM users (temporary workers,
  common area phones, etc.) are not resolved. Add these users to the global
  directory if you want them to be searchable, etc.
* Unlike LDAP Directory configuration, LDAP Search only provides a single integration
  per cluster. Customers with complex AD environments may be forced to deploy
  AD-LDS to make use of this feature.

  |LDAP_search_config_resized|
 
* There is no interaction with the Corporate Directory IP Phone Service in the
  current CUCM LDAP Search feature.
  Corporate Directory still looks to the local CUCM database, which requires
  the local database to maintain a list of all users in all clusters, unless a
  separate Web Server is used to host the global directory. Currently, there is
  no such feature in the HCS solution. You must factor all prominent customer User
  Journeys into deployment model selection. 
* There is an open enhancement to support the LDAP Search model in CUCM.
  Currently, this requires a once-off static configuration on each leaf cluster.
  

.. |LDAP_search_config_resized| image:: /src/images/LDAP_search_config_resized.png