> For the complete documentation index, see [llms.txt](https://developer.ultimo.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ultimo.net/connectors/ldap/cloud-vs-on-premises.md).

# Cloud vs On Premises

Implementation of the LDAP integration depends on how Ultimo is hosted. Ultimo in the cloud requires a different approach than Ultimo on premises.

## On Premises

When Ultimo is hosted on premises, Ultimo will try to make a direct connection with the directory service. The directory service is supposed to run in the same network, so Ultimo is able to make a connection. To setup a successful connection, configure the needed [connection settings](/connectors/ldap/ldap-connector.md#connection-properties) on the LDAP connector.

## Cloud

When Ultimo is hosted in the Cloud, it is usually not possible to make a direct connection with the directory service, as the directory service is unreachable from outside a customers network. To make the integration work in a cloud environment, a webservice and powershell script have to be used.

### Powershell

When hosted on Azure, it is possible to download a Powershell script in the LDAP connector manager. This script contains all information necessary (taken from the settings on the LDAP connector) to retrieve data from the directory service and sending the results back to an Ultimo webservice. The Powershell script can be put on the server where the directory service runs or a location from where the directory service can be reached. To periodically send results to Ultimo, make sure the script is scheduled and ran with authorised credentials to connect to the directory service.

### Webservices

To receive data from the directory service in Ultimo, a webservice (import connector) is available. The webservice request is send automatically from the Powershell script. The webservice will pass the input to the LDAP connector and execute the standard business logic to create and maintain users and employees.

### LDAP connector differences

As setting up a connection with the directory service is not initiated from Ultimo when hosted in the Cloud, not all [connection properties](/connectors/ldap/ldap-connector.md#connection-properties) apply on the LDAP connector.

| Parameter           | Applies to Cloud |
| ------------------- | ---------------- |
| Server              | ✅                |
| User name           | 🚫               |
| Password            | 🚫               |
| Distinguished names | ✅                |
| Filter              | ✅                |
| Page size           | ✅                |
| Use fast bind       | 🚫               |
| Use server bind     | 🚫               |
| Use secure          | 🚫               |
| Use SSL             | 🚫               |


---

# 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://developer.ultimo.net/connectors/ldap/cloud-vs-on-premises.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.