Active directory Asset Management means connecting your Active Directory to your IT Asset Management (ITAM) tool so the people and computers registered in the directory feed the asset inventory. IT teams look for it when they want asset owners to come straight from the directory, technicians to sign in with their corporate account, and every computer in the domain to show up in the inventory.
This guide shows how to set it up in InvGate Asset Management with numbered steps for each scenario. You'll sync users from an on-premises Active Directory over Lightweight Directory Access Protocol (LDAP), connect Microsoft Entra ID for single sign-on (SSO) and provisioning, move from one to the other without duplicate users, and bring Active Directory computers into your inventory.
Why connect InvGate Asset Management to Active Directory
Every asset needs an owner, and your directory already knows who works at the company, in which department and under which manager. Connecting both systems turns that data into the people side of your inventory, with these benefits:
- Owners that stay current. User provisioning from the directory creates and updates people automatically, so new hires are ready to receive assets on day one.
- One login for your team. Technicians sign in with their Active Directory credentials or through SSO with Microsoft Entra ID, and the multi-factor authentication (MFA) policies of your identity provider apply to InvGate Asset Management too.
- Computers you didn't know about. An Active Directory discovery source lists the computers registered in the domain, so devices missing from the inventory come to light.
- Access control that stays in your hands. The directory confirms who each user is, and roles and tag-based permissions in InvGate Asset Management decide what each one can see and change.
- Any deployment model. The integration works in the cloud and on-premises, and a cloud instance reaches an on-premises directory through the InvGate Connector without exposing it to the internet.
The result is an inventory where each asset is tied to a real, up-to-date person. That makes onboarding, offboarding and audits faster, because the question of who has what is already answered.
Which setup fits your environment
The steps you need depend on where your directory lives and where your InvGate Asset Management instance runs. Use this table to find your scenario before you start:
| Your environment | What you configure |
| On-premises Active Directory and on-premises InvGate Asset Management | LDAP connection in Directory services |
| On-premises Active Directory and InvGate Asset Management in the cloud | InvGate Connector plus LDAP connection in Directory services |
| Microsoft Entra ID only | SAML single sign-on plus SCIM provisioning |
| Hybrid (on-premises Active Directory and Microsoft Entra ID) | LDAP for provisioning, SAML against Entra ID for sign-in, then SCIM |
Discovering the computers registered in Active Directory is a separate setup that works in any of these scenarios. You'll find it in the last section of this guide.
Prerequisites
Gather these before you begin, so you can complete each procedure in one sitting. Not every item applies to every scenario in the table above:
- An administrator account in InvGate Asset Management.
- A domain account with read access to Active Directory, for the LDAP connection.
- The InvGate Connector installed in your network, if your InvGate Asset Management instance is in the cloud and your Active Directory is on-premises.
- Administrator access to Enterprise applications in Microsoft Entra ID, for SSO and SCIM provisioning.
- A Proxy installed in your network, for the Active Directory discovery source.
If you're connecting Entra ID, keep both admin consoles open side by side. Several values are copied from one to the other during the setup.
How to sync users from on-premises Active Directory over LDAP
LDAP is the protocol InvGate Asset Management uses to read users from an on-premises Active Directory. Cloud instances first need the InvGate Connector to reach the directory, and on-premises instances can go straight to the second step.
Step 1: Set up the InvGate Connector (cloud instances)
The InvGate Connector is a component included with your InvGate subscription that links your cloud instance with services in your local network. InvGate generates it for your organization, so the setup starts with a request:
- Request the Connector from InvGate Support. Share the IP address or DNS name of your Active Directory server and the MAC address of the Windows server where you'll install the Connector (it can be the domain controller itself or another server).
- Run the installer as an administrator on that Windows server. The installation takes a few clicks and creates a Windows service called InvGate Connector.
- Allow outbound traffic from the Connector to the InvGate cloud in the Windows firewall, using the ports and addresses InvGate shares with you. If your network has firewalls outside the server, ask your infrastructure team to apply the same rule there.
- Write down the hostname (pytun-node-X.invgate.com) and port that InvGate assigns to your tunnel. You'll enter them in the Directory services form in the next step.
The Connector opens an encrypted tunnel from your network to the InvGate cloud, so Active Directory stays private and you don't need a VPN. It doesn't store any passwords, because authentication stays with Active Directory, and it reconnects by itself after a network cut.
Step 2: Add Active Directory in Directory services

With the connection ready, you'll create the directory service in InvGate Asset Management. The form tests the connection before you save, so you can fix any credential or port issue on the spot:
- Log in as an administrator, go to Settings > Users > Directory services and click Add.
- In Type, select Active Directory, and enter a Name to identify the connection.
- In Hostname / IP and Port, enter your domain controller and its port (389 by default). On a cloud instance, enter the hostname and port InvGate assigned to your Connector.
- In Security, select TLS, SSL or None.
- Enter the Domain. Domain's name and Base DN (the base Distinguished Name of your directory) fill in automatically once the previous fields are complete.
- Optionally, in DNs, enter the DNs of the organizational units you want to sync, one per line.
- In User or DN, enter the credentials of the account that reads the directory, and click Test to check the connection.
- Under Directory Services, enable Auto import new users to bring in new users on each sync, and Schedule to choose how often the sync repeats. If you leave auto import off, you can pick the users to import by hand.
- Under Authentication, enable Authentication so users can log in with their Active Directory credentials, and Auto provisioning to create users the first time they log in, with the role you select for them.
- Click Save. The directory service is enabled by default.
InvGate Asset Management matches users by email, so people you had already loaded by hand get updated with the directory data and keep the assets assigned to them. For contractors or anyone outside the directory, Settings > Users > Users > Import takes a CSV file: those users have no credentials, and they can still be the owners of their assets.
How to connect Microsoft Entra ID (formerly Azure AD)
Microsoft Entra ID is the new name Microsoft gave to Azure Active Directory, with the same capabilities. In InvGate Asset Management it covers two jobs through a single enterprise application: SSO with Security Assertion Markup Language (SAML) and user provisioning with System for Cross-domain Identity Management (SCIM).
Set up SAML first, because SCIM provisioning reuses the same enterprise application. You'll need administrator access to Entra ID and to InvGate Asset Management at the same time.
Set up Microsoft Entra ID SSO with SAML

Microsoft Entra ID SSO lets your team open InvGate Asset Management with their Microsoft account. The values travel in both directions between the two consoles, so follow the steps in order:
- In the Microsoft Entra admin center, go to Enterprise applications and click New application.
- Select Create your own application, name it "InvGate Asset Management" and choose Integrate any other application you don't find in the gallery.
- Open the new application, go to Single sign-on and select SAML.
- In InvGate Asset Management, go to Settings > Users > Authentication and click Add SAML. Copy the Assertion Consumer Service (ACS) URL that the form shows.
- Back in Entra ID, edit Basic SAML Configuration. In Identifier (Entity ID), enter the URL of your InvGate Asset Management instance, and in Reply URL (Assertion Consumer Service URL), paste the ACS URL.
- Edit Attributes & Claims. Set Unique User Identifier (Name ID) to user.mail, map the firstname, lastname and email attributes, and leave the namespace field empty.
- In the SAML certificate settings, edit the signing options and select Sign SAML response and assertion.
- Assign the users and groups that will sign in through the application.
- Copy the Microsoft Entra Identifier and the Login URL, and download the certificate in Base64.
- In the SAML form of InvGate Asset Management, paste the identifier in Entity ID and the Login URL in Login URL. Select Public Key as the certificate type, upload the certificate in PEM format and save.
- In Settings > Users > Authentication, select the new service in the Single Sign-On drop-down and save.
- Test the login with a user who already has a role in InvGate Asset Management, such as a technician.
SAML creates a user the first time they sign in, and it doesn't import anyone ahead of time. To have your whole directory in InvGate Asset Management before people log in, add SCIM provisioning with the next steps. Since sign-in now runs through Entra ID, the MFA and conditional access policies you set there apply to InvGate Asset Management as well.
Provision users with SCIM
SCIM lets Entra ID create and update users in InvGate Asset Management on its own, which makes it the Active Directory sync option for organizations whose users live in the cloud. Okta supports the same SCIM provisioning, and the logic of these steps is the same:
- In InvGate Asset Management, go to Settings > Users > Directory services, click Add and, in Type, select Azure AD (Entra ID) / Okta / SCIM applications. Copy the URL and the token the form gives you.
- In Entra ID, open the enterprise application you created for SAML and go to Provisioning.
- Set the provisioning mode to Automatic. Under Admin Credentials, paste the URL and the token from InvGate Asset Management, and click Test Connection.
- Review the Mappings to confirm which attributes reach InvGate Asset Management.
- Assign the users and groups to provision, set Provisioning Status to On and save.
From Entra ID, InvGate Asset Management receives first and last name, email, phone, address, job title, company, employee ID, department and manager. Each asset owner arrives with the context IT needs to assign hardware and track who has what.
Moving from on-premises Active Directory to Microsoft Entra ID
Many organizations run a hybrid identity setup for a while, with Active Directory on-premises and Microsoft Entra ID in the cloud. InvGate Asset Management supports a staged move, so you can change one piece at a time:
- Keep LDAP for provisioning. Your on-premises Active Directory keeps creating and updating users, through the InvGate Connector if your instance is in the cloud.
- Switch sign-in to SAML against Entra ID. Users log in with their Microsoft account, and MFA comes from Entra ID.
- Move provisioning to SCIM when you're ready. Coordinate this step with InvGate Support so existing users are merged with their SCIM records and nobody ends up duplicated.
Roles, permissions and asset assignments stay in InvGate Asset Management throughout the move, because authorization is managed inside the tool. Only the source of users and the way people sign in change at each stage.
How to bring Active Directory computers into your inventory

Active Directory also knows which computers belong to the domain, and that list is a quick way to find devices missing from your inventory. InvGate Asset Management reads it through an Active Directory discovery source, which brings in the hostname and operating system of each computer. The InvGate Agent, network discovery, integrations such as Microsoft Intune and CSV imports then complete each record with the hardware and software details you need to manage it.
This setup runs through a Proxy, the InvGate component that discovers devices inside your network. Follow these steps:
- Make sure a Proxy is installed in a network that can reach your domain controller. If you don't have one, the form offers to install it.
- Go to Settings > Discovery > Discovery sources, click Add (or View catalog if it's your first source) and select Active Directory.
- Enter a Name, select the Proxy and fill in Hostname/IP and Port (389 by default) and Security.
- Enter the Windows username in the suggested format, its Windows password and the Domain. Domain name and Base DN complete automatically, and DNs is optional.
- In Discover active devices from, choose a time window. Only computers that logged in during that period are taken into account.
- Enable Auto import devices to add every computer found to the Assets explorer on each sync. Leave it off if you prefer to review the devices first and convert them from the Discovery section.
- Enable Schedule, set the date and time of the first sync and choose how often it repeats. Save.
- In the list of discovery sources, start the sync manually to test it, and check its status, the number of devices found and the logs.
To sum up
Active directory asset management connects the people and computers in your directory with the assets IT manages. With InvGate Asset Management, you can sync users from Active Directory or Microsoft Entra ID, sign in with SSO and add domain computers to the inventory, whether your instance runs in the cloud or on-premises.
If your team also uses InvGate Service Management, see how to set up its own integration with Active Directory for requesters and agents. To try the whole setup with your own directory, start a free trial or talk to Sales.
Frequently Asked Questions
These are the questions IT teams ask most often when they connect InvGate Asset Management to their directory. The answers are short, and the sections above have the full steps for each setup.
Can the cloud version of InvGate Asset Management connect to an on-premises Active Directory?
Yes. The InvGate Connector, included with your subscription, opens an encrypted tunnel between your network and the InvGate cloud, so the LDAP connection works without exposing Active Directory to the internet.
Which identity providers work with InvGate Asset Management for single sign-on?
Any identity provider compatible with SAML 2.0, such as Microsoft Entra ID and Okta. Entra ID and Okta can also provision users through SCIM.
Does InvGate Asset Management support multi-factor authentication?
Yes, through your identity provider. When users sign in with SAML, the MFA policies you configured in Entra ID or Okta apply to InvGate Asset Management.
Can I add users who aren't in Active Directory?
Yes. You can create them by hand or import them from a CSV file in Settings > Users > Users. They don't get login credentials, and they can still be assigned as owners of assets.