> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/cloud-configuration-guide/topics/authentication-with-microsoft-entra-id-ldap-server/setup-secure-ldap-for-microsoft-entra-id-domain-service.md).

# Setup Secure LDAP for Microsoft Entra ID Domain Service

{% hint style="success" %}
By following the steps below, you'll enable secure LDAP on Microsoft Entra ID and configure the required firewall rules and roles, ensuring secure and seamless authentication for your EnGenius Access Points.
{% endhint %}

### **To get started:**

1. Sign in to the Microsoft Azure Admin console.
   * Navigate to [**portal.azure.com**](https://portal.azure.com/) and sign in with your credentials.
2. Enable the Microsoft Entra ID Secure LDAP Server.
   * Follow the instructions provided in the [Microsoft Entra ID documentation](https://learn.microsoft.com/en-us/entra/identity/domain-services/tutorial-configure-ldaps) to enable the secure LDAP server.
3. **(Optional)** Configure an appropriate role for verifying user credentials.
   * Specify a role that can read keys and values for the AP to verify users.
   * For more information on Microsoft Entra built-in roles, see[ ](https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference)<https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference>.
4. Create a Firewall rule for the AP to query your Microsoft Entra ID Secure LDAP Server.
   * Ensure TCP traffic direction is set to outgoing to port 636 of hostname **`ldaps.aaddscontoso.com`** (hostname and port from step 1).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/cloud-configuration-guide/topics/authentication-with-microsoft-entra-id-ldap-server/setup-secure-ldap-for-microsoft-entra-id-domain-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.