Azure AD for Windows Server

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 Active Directory 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 AD 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: or via chat.

The Azure AD integration is configured by using the Vizito Azure AD 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

Step 1: NodeJS

Use your favorite package manager to install NodeJS

Step 2: Vizito Azure AD client

Download and extract our Azure AD client to a directory of your choice

Steps 3 and 4 need to be executed by your Azure AD administrator

Step 3: Add an App Registration to your Azure AD

Go to 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

Click on App Registrations and then on New registration:

Vizito integration Azure Active Directory App Registration

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:

Click on Register.

Vizito integration Azure Active Directory Fields

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

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

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

Click on API permissions > Microsoft APIs > Microsoft Graph

Vizito integration Azure Active Directory API permissions

Click on Application permissions

Vizito integration Azure Active Directory API permissions application

Scroll down to Directory and select Directory.Read.All and Directory.ReadWrite.All

Vizito integration Azure Active Directory API permissions Directory

Scroll down to Group and select Group.Read.All and Group_ReadWrite.All

Vizito integration Azure Active Directory API permissions Group

Scroll down to User and select User.Read.All and User.ReadWrite.All

Click on Add permission

Vizito integration Azure Active Directory API permissions User

Once completed, click on Grant admin consent for and then Yes:

Vizito integration Azure Active Directory Grant permissions

Step 4: Vizito Azure AD 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:
client*id Yes The client id used for accessing Azure AD (created in Step 3).
client_secret Yes The client secret used for accessing Azure AD (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 AD 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.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.

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 AD 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:$top=999.

You can now use a browser to test the Azure AD http server by pointing your browser to http://ip_or_hostname_of_machine_running_google_suite_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 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 at extract the appropriate architecture executable to a folder of your choice. now run the following command: nssm install vizito_azure_ad_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 AD client before starting the service.


Demo services are available for testing purposes. They include names such as “Tesla”, “Newton”, etc..

  • HTTP version:
  • HTTPS version:

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.