--- title: "Azure Entra ID for Windows Server | Vizito Help Center" description: "Azure Entra ID for Windows Server | Integrate Azure Entra ID user information colleagues employees hosts for notifications to host LDAP | Vizito | Visitor …" url: https://vizito.eu/faq/integrations/windows-azure/ language: en --- # Azure Entra ID for Windows Server Pieter-Jan Dries · Sep 1, 2026 · 5 min In this article Vizito has recently introduced a new feature that allows you to synchronize your Azure employees right from our cloud systems without you having to install any piece of software. Learn more about the [Azure Entra ID synchronization](https://vizito.eu/faq/integrations/azure-synchronization/). The benefits are that it is easier to set up. If you prioritize privacy over ease of use, you can still use our Azure Entra ID client synchronization, which does not duplicate all employee information to our servers. If you need any help configuring the following steps, be sure to get in touch: [info@vizito.be](mailto:info@vizito.be) or via chat. The Azure Entra ID integration is configured by using the Vizito Azure Entra ID client which needs to be installed on a device/server which the tablet can connect to. So the tablet needs to be able to communicate to this device/server via its network. Please find a schematic representation below: ![Vizito ldap client network](https://vizito.eu/faq/integrations/windows-azure/ldap_client_network.png?width=900) ### Step 1: NodeJS Use your favorite package manager to install NodeJS ### Step 2: Vizito Azure Entra ID client [Download](https://bitbucket.org/modulage/azure_ad_client/downloads/) and extract our Azure Entra ID client to a directory of your choice Steps 3 and 4 need to be executed by your Azure Entra ID administrator ### Step 3: Add an App Registration to your Azure Entra ID Go to the [Azure portal](https://portal.azure.com/) and log in. Select the domain / tenant you would like to integrate with Vizito. Now, follow these steps: Navigate to Azure Active Directory: ![Vizito integration Azure Active Directory](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_01.webp?width=900) Click on _App Registrations_ and then on _New registration_: ![Vizito integration Azure Active Directory App Registration](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_02.webp?width=900) Fill in the required fields. Choose a name: _Vizito Azure Client_ Select who can access this API, first option for a single tenant. Under _Redirect URI (optional)_ select application type _Web_ and sign-on URL: `https://backoffice.vizito.be/oauth`. Click on _Register_. ![Vizito integration Azure Active Directory Fields](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_03.webp?width=900) Copy the Application (client) ID and use this value for the configuration item _client\_id_ in the config.json file. Copy the Directory (tenant) ID and use this value for the configuration item _tenant\_id_ in the config.json file. ![Vizito integration Azure Active Directory Application ID](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_04.webp?width=900) Click on _Certificates & secrets_ > _Client secrets_ > _New Client secret_ Choose a description _Vizito Azure client secret_ and set an Expiry option (24 months) Click on _Add_ ![Vizito integration Azure Active Directory client Secret](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_05.webp?width=900) Copy the _value_ and use this for the configuration item _client\_secret_ in the config.json file. **Important: you can only copy this value now, it will not be exposed at a later time when you return to your client secrets as a safety measure.** ![Vizito integration Azure Active Directory Client secret overview](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_06.webp?width=900) Click on _API permissions_ > _Microsoft APIs_ > _Microsoft Graph_ ![Vizito integration Azure Active Directory API permissions](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_07.webp?width=900) Click on _Application permissions_ ![Vizito integration Azure Active Directory API permissions application](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_08.webp?width=900) Scroll down to _Directory_ and select **Directory.Read.All** ![Vizito integration Azure Active Directory API permissions Directory](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_09.webp?width=900) Scroll down to _Group_ and select **Group.Read.All** ![Vizito integration Azure Active Directory API permissions Group](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_10.webp?width=900) Scroll down to _User_ and select **User.Read.All** Click on _Add permission_ ![Vizito integration Azure Active Directory API permissions User](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_11.webp?width=900) Once completed, click on _Grant admin consent for_ and then _Yes_: ![Vizito integration Azure Active Directory Grant permissions](https://vizito.eu/faq/integrations/windows-azure/vizito_ldap_azure_integration_12.webp?width=900) ### Step 4: Vizito Azure Entra ID client - Config Edit config.json to match your environment. Here you can find the configuration values and a description of what information you need to enter: | **JSON property** | **Mandatory** | **Description** | | --- | --- | --- | | domain | Yes | Domain reference Example: vizito.eu | | client\*id | Yes | The client id used for accessing Azure Entra ID (created in Step 3). | | client\_secret | Yes | The client secret used for accessing Azure Entra ID (created in Step 3). | | tenant\_id | Yes | Your tenant id (selected in Step 3). | | group | No | Optional filtering for a specific group: provide the Azure Entra ID Group Object ID for which you want to fetch the members for. | | mobile\_prefix | No | If your LDAP dictionary contains local or internal mobile phone numbers (without country code), you can add a prefix containing the country code. The first character of the local or internal mobile phone number will be replaced with this prefix. | | api\_port | Yes | Default value: \_48800\*. This configures the port at which the node application will listen for HTTP(s) requests. | | use\*ssl\_for\_api | Yes | Default value: \_false\*. If set to _true_, it will use the _ssl.ca_, _ssl.key_ and _ssl.cert_ configuration items to load a private key / public key pair for enabling TLS communication. | | Read up on [creating your own self-signed certificates using a custom root CA](https://gist.githubusercontent.com/fntlnz/cf14feb5a46b2eda428e000157447309/raw/318beb5642577c16de2564666b04de99a215308e/self-signed-certificate-with-custom-ca.md). | | | IMPORTANT: You can configure multiple domains in the domains array. Be sure to have a complete domain configuration encapsulated with { } brackets. ### Step 5: Run Open a command prompt, navigate to the folder where your Azure Entra ID client resides, and run - “npm install” (only required once) - “node server.js” If everything works as intended, you should see a line like this in your console: `https://graph.microsoft.com/v1.0/users?$top=999`. You can now use a browser to test the Azure Entra ID http server by pointing your browser to `http://ip_or_hostname_of_machine_running_azure_entra_id_client:8080`. If you’re running a firewall, make sure it allows access to port 48800. If your browser shows a JSON object representing the users you want to expose, than everything works! ### Step 6: Configure the backoffice to make the tablet connect to the client Navigate to [Vizito backoffice](https://backoffice.vizito.be/) and under Settings, configure the Host datasource as ‘Managed externally’ and fill in the Integration URL. Now the tablet will look up the information from the installed client. ### Step 7 (optional): Use NSSM to daemonize the node process as a Windows Service. Download the [latest release of NSSM](https://nssm.cc/download) extract the appropriate architecture executable to a folder of your choice. now run the following command: nssm install vizito\_azure\_entra\_id\_client This will show a window where your service parameters can be configured. - Select “node.exe” as Path. It can usually be found in c:Program Files (x86)nodejsnode.exe - Type the full path to server.js in the Arguments field - Optionally, you can set a Display name for your service in the Details tab. Now go to your Windows Services, start your newly created service, and test! Remember to stop any manually started instances of the Azure Entra ID client before starting the service. ### Troubleshooting Demo services are available for testing purposes. They include names such as “Tesla”, “Newton”, etc.. - HTTP version: `http://178.162.136.223:48800` - HTTPS version: `https://source.vizito.eu:48801` If you’re using a HTTPS configuration you can configure multiple CA references. Add each CA between " (quotes) in the CA array, which you can find in the config.JSON file.