Skip to main content

How to automatically assign assets to requesters using Active Directory

Learn to auto-assign assets to users per client using Azure AD last login identity. Save time and ensure accurate asset mapping.

Updated yesterday

Streamline asset management for your clients by automatically assigning assets to requesters based on their last login identity in Azure Active Directory (AD). This feature can now be configured individually for each client, eliminating manual mapping, reducing errors, and ensuring your asset inventory is always up-to-date.

Prerequisites

Before enabling this feature for a client, ensure the following conditions are met:

  • Client-Level Azure AD Integration: Each client must have an active Azure AD integration configured in SuperOps.

  • AD-Synced Users: The end-users must be synced from the respective client’s Azure AD directory.

  • AD-Linked Profile: The device profile must contain a User Principal Name (UPN) that matches a user in the client’s synced directory.

How to configure auto-assignment per client

  1. From your main dashboard, navigate to the Settings icon on the left-hand navigation panel.

  2. In the Settings menu, locate the Asset Management section and click on Auto Assign.

    Screenshot 1

    You will be directed to the 'Auto Assign' page, which lists all clients with an active AD integration.

    Screenshot 2

  3. Click on the client you wish to configure. This will open the Auto Assign Configuration window for that client.

    Screenshot 3

  4. Enable the Auto-Assign Assets using AD toggle. This activates the core feature, allowing assets for this client to be assigned based on the user's last AD login.

    Screenshot 4

  5. Next, configure the optional settings to customize the workflow:

    • Override Manual configuration: Enable this to replace any existing manual asset assignments with the last login user captured from AD. This is ideal for keeping asset ownership continuously updated.

      Screenshot 5

    • Asset Exclusion rules: Enable this to prevent specific assets (like shared devices, servers, or test machines) from being auto-assigned. Click + Conditions to build your rule. For example, to exclude assets with 'shared' in their name, set the condition as Name contains shared.

      Screenshot 6

      A completed configuration with an exclusion rule will look like this:

      Screenshot 7

  6. Click Save to apply the new configuration for the client.

  7. After saving, you will return to the Auto Assign list. You can see that the configuration is now active for the client, and the Rules column indicates that rules have been 'APPLIED'. You can disable the entire auto-assign configuration for the client at any time by clicking the main toggle switch next to their name.

    Screenshot 8

Verifying auto-assignment

Once configured, you can verify that assets are being assigned correctly by checking the activity logs. Navigate to an asset's summary page to view its history. The log will show events like 'Auto-assigned to [User] through an AD login', confirming the assignment was successful.

Did this answer your question?