Schedule import of users from CSV

With Adaxes, you can automate user account provisioning by importing user data from a CSV file. For example, such a CSV file can be created by your HR system or other third-party software. Adaxes can regularly process this file and create new users in your directory. On top of that, Adaxes will execute all the provisioning workflows you have configured.

The CSV file has to be imported using a PowerShell script. The script will read the CSV file via the Import-Csv cmdlet and pass the data to the New-AdmUser cmdlet to create new users.

The New-AdmUser cmdlet is included in Adaxes PowerShell module. To use the cmdlet in a scheduled task, you need to install Adaxes PowerShell module on the computer where your Adaxes service is running.

Create CSV file

Create a CSV file with the following structure.

Adaxes will expect the columns in the CSV file to have specific names. If the columns in your CSV file are named differently or are not represented in the default set, you will need to use column mapping in the import script.

 Default column set {id=default-column-names}
Column mame Description Example Type
AccountExpirationDate The expiration date for the account. When set to 0, the account never expires. 4/17/2006
Monday, April 17, 2006
Monday, April 17, 2006 2:22 PM
Mon, 17 Apr 2006 21:22:48 GMT
05/01/2012 5:00:00 PM
AccountNotDelegated Specifies whether the security context of the user is delegated to a service. true
AccountPassword The user password. secret Secure String
Specifies whether reversible password encryption is allowed for the account. true
CannotChangePassword Specifies whether the account password can be changed. true
ChangePasswordAtLogon Specifies whether the password must be changed during the first logon. true
City The user's town or city. London String
Company The user's company. Acme String
Country The country or region code for the user's language of choice. US
Department The user's department. Sales String
Description The description of the user. External subcontractor String
DisplayName The display name of the user. John Smith String
Division The user's division. Software String
EmailAddress The user's e-mail address. String
EmployeeID The user's employee ID. A123321 String
EmployeeNumber The user's employee number. 112233 String
Enabled Specifies if the account is enabled. true
Fax The user's fax phone number. +1 (999) 555 1122 String
GivenName The user's first name. John String
HomeDirectory The user's home directory. \\SERVER\johnsmith String
HomeDrive The drive that is associated with the UNC path defined by the HomeDirectory property. D: String
HomePage The URL of the home page of the user. String
HomePhone The user's home telephone number. +1 (999) 555 2222 String
Initials The initials that represent part of the user's name. L String
LogonWorkstations The computers that the user can access. COMP1, String
Manager The user's manager. john.doe
MobilePhone The user's mobile phone number. +1 (999) 555 3333 String
Name The user's full name. John Smith String
Office The location of the user's office or place of business. B1021 String
OfficePhone The user's office telephone number. +1 (999) 555 4444 String
Organization The user's organization. Accounting String
OtherAttributes Values for user properties that cannot be specified in the CSV file columns. 'extensionAttribute1'=value
'attr1'=val; 'attr2'=val1,val2
OtherName The name in addition to a user's given name and surname, such as the user's middlename. Peter String
PasswordNeverExpires Specifies whether the password of the account can expire. true
PasswordNotRequired Specifies whether the account requires a password. true
Path The DN of the organizational unit (OU) or container where the new user will be created. CN=Users,DC=acme,DC=com String
POBox The user's post office box number. 25656 String
PostalCode The user's postal code or zip code. 18711 String
ProfilePath The path to the user's profile. \\SERVER\profiles\johndoe String
Specifies whether an object is protected from accidental deletion. true
SamAccountName The user's logon name (pre-Windows 2000). johnsmith String
ScriptPath The path to the user's log on script. \\SCRIPTS\johnsmithLogin String
SmartcardLogonRequired Specifies whether a smart card is required to logon. true
State The user's state or province. Nevada String
StreetAddress The user's street address. 100 Main Street String
Surname The user's last name or surname. Smith String
Title The user's title. Sales Manager String
TrustedForDelegation Specifies whether an account is trusted for Kerberos delegation. true
UserPrincipalName The user's logon name. String

Schedule user import

To schedule the import process, you need to create a scheduled task that will execute a PowerShell script.

  1. Launch Adaxes Administration console.

    • On the computer where Adaxes Administration console is installed, open Windows Start menu.

    • Click Adaxes Administration Console.

  2. Expand your Adaxes service, right-click Scheduled Tasks, point to New and click Scheduled Task.

  3. Enter a name for the new scheduled task, and click Next.

    It is recommended to use nouns to name scheduled tasks (e.g. CSV Importer), because tasks will appear as operation initiators in the acitivity log and approval email notifications.

  4. Specify how often the task should run and click Next.

  5. To import user accounts into an organizational unit, select the Organizational Unit object type.

    Click Next.

  6. Click Add an action.

  7. Select Run a program or PowerShell script.

  8. Click Edit.

    You can click the button to provide a custom description for the action.

  9. Paste the following script into the script editor.

    $file = "\\SERVER\Share\users.csv"
    $targetDN = "%distinguishedName%"
    $domain = $Context.GetObjectDomain($targetDN)
    $importedUsers = Import-Csv $file
    foreach ($user in $importedUsers)
        # Process special columns (see below)
        # Process mapped columns (see below)
        $user | New-AdmUser -Path $targetDN -Server $domain -AdaxesService localhost

    The $targetDN variable specifies the distinguished name (DN) of the organizational unit or container where to create user accounts. The %distinguishedName% value reference will be replaced with the DN of the organizational unit included in the activity scope of the task.

    Processing special columns

    If your CSV file contains columns with the following data types, they need to be processed in the script:

    • Password (e.g. AccountPassword)
    • Boolean (e.g. ChangePasswordAtLogon, Enabled)
    • DN (e.g. Manager)

    The columns have to be processed because Adaxes expects data of a specific type from each column.

    For example, to specify a manager, you need to pass the manager's distinguished name (DN) or username to the New-AdmUser cmdlet. This means you need to obtain the correct property value in the script if the column in your CSV contains some other unique identifier, like Employee ID.

    $file = "\\SERVER\Share\users.csv"
    $targetDN = "%distinguishedName%"
    $domain = $Context.GetObjectDomain($targetDN)
    $importedUsers = Import-Csv $file
    foreach ($user in $importedUsers)
        # Password column
        $user.AccountPassword = `
            ConvertTo-SecureString -AsPlainText $user.AccountPassword -Force
        # Boolean columns
        $user.Enabled = [System.Boolean]::Parse($user.Enabled)
        $user.ChangePasswordAtLogon = [System.Boolean]::Parse($user.ChangePasswordAtLogon)
        # DN columns
        $managerID = $user.Manager
        $manager = Get-AdmObject -Filter {employeeID -eq $managerID} `
            -Server $domain -AdaxesService localhost -ErrorAction SilentlyContinue
        $user.Manager = $manager.DistinguishedName
        $user | New-AdmUser -Path $targetDN -Server $domain -AdaxesService localhost

    Column mapping

    If columns in your CSV file have custom names or the file contains columns that are not included in the default property set, you need to map these columns to the properties of the new user.


    The $columnMap variable specifies a hashtable that maps column names to property names from your directory schema.

    Import-Module Adaxes
    $file = "\\SERVER\Share\users.csv"
    $targetDN = "%distinguishedName%"
    $columnMap = @{
        "First Name" = "givenName";
        "Last Name" = "sn";
        "EmpID" = "employeeID";
        "EmpRole" = "adm-CustomAttributeText1";
    $domain = $Context.GetObjectDomain($targetDN)
    $importedUsers = Import-Csv $file
    foreach ($user in $importedUsers)
        $otherAttributes = @{}
        foreach ($property in $user.PSObject.Properties)
            # Map property name if mapping specified
            if ($columnMap[$property.Name])
                $propertyName = $columnMap[$property.Name]
            # Get property value
            $value = $property.Value
            if ([System.String]::IsNullOrEmpty($value))
            $otherAttributes.Add($propertyName, $value)
        $user | New-AdmUser -Path $targetDN -Server $domain `
            -AdaxesService localhost -OtherAttributes $otherAttributes

    For quick reference, here is a list of most commonly used properties, their names, and their availability.

     Property names
    • Display name

    • Property name in schema

    • Availability

    • Full Name

    • cn, name

    • Active Directory / Microsoft Entra ID

    • First Name

    • givenName

    • Active Directory / Microsoft Entra ID

    • Last Name

    • sn

    • Active Directory / Microsoft Entra ID

    • Initials

    • initials

    • Active Directory only

    • Description

    • description

    • Active Directory / Microsoft Entra ID

    • Office

    • physicalDeliveryOfficeName

    • Active Directory / Microsoft Entra ID

    • Telephone Number

    • telephoneNumber

    • Active Directory / Microsoft Entra ID

    • Telephone Number (Other)

    • otherTelephone

    • Active Directory only

    • Email

    • mail

    • Active Directory / Microsoft Entra ID

    • Web Page

    • wwwHomePage

    • Active Directory / Microsoft Entra ID

    • Web Page (Other)

    • url

    • Active Directory only

    • Username

    • userPrincipalName

    • Active Directory / Microsoft Entra ID

    • SAM Account Name

    • sAMAccountname

    • Active Directory only

    • Password

    • unicodePwd

    • Active Directory / Microsoft Entra ID

    • Account Expires

    • accountExpires

    • Active Directory / Microsoft Entra ID

    • Protect from Accidental Deletion

    • ProtectedFromAccidentalDeletion

    • Active Directory / Microsoft Entra ID

    • Street Address

    • streetAddress

    • Active Directory / Microsoft Entra ID

    • P.O.Box

    • postOfficeBox

    • Active Directory / Microsoft Entra ID

    • City

    • l

    • Active Directory / Microsoft Entra ID

    • State/Province

    • st

    • Active Directory / Microsoft Entra ID

    • Zip/Postal Code

    • postalCode

    • Active Directory / Microsoft Entra ID

    • Country/Region

    • c, co, and countryCode

    • Active Directory / Microsoft Entra ID

    • Title

    • title

    • Active Directory / Microsoft Entra ID

    • Department

    • department

    • Active Directory / Microsoft Entra ID

    • Company

    • company

    • Active Directory / Microsoft Entra ID

    • Division

    • division

    • Active Directory / Microsoft Entra ID

    • Manager

    • manager

    • Active Directory / Microsoft Entra ID

    • Profile Path

    • profilePath

    • Active Directory only

    • Logon Script

    • scriptPath

    • Active Directory only

    • Home Directory

    • homeDirectory

    • Active Directory only

    • Home Directory Drive

    • homeDrive

    • Active Directory only

    • Home Phone, Home Phone (Other)

    • homePhone, otherHomePhone

    • Active Directory only

    • Mobile Phone

    • mobile

    • Active Directory / Microsoft Entra ID

    • Mobile Phone (Other)

    • otherMobile

    • Active Directory only

    • Fax

    • facsimileTelephoneNumber

    • Active Directory / Microsoft Entra ID

    • Fax (Other)

    • otherFacsimileTelephoneNumber

    • Active Directory only

    • IP Phone

    • ipPhone, otherIpPhone

    • Active Directory only

    • Notes

    • info

    • Active Directory only

    • Employee Type

    • employeeType

    • Active Directory / Microsoft Entra ID

    • Employee ID

    • employeeID

    • Active Directory / Microsoft Entra ID

    • Age Group

    • ageGroup

    • Microsoft Entra ID only

    • Hire Date

    • employeeHireDate

    • Microsoft Entra ID only

    • Leave Date

    • employeeLeaveDateTime

    • Microsoft Entra ID only

    • Cost Center

    • costCenter

    • Microsoft Entra ID only

    • Responsibilities

    • responsibilities

    • Microsoft Entra ID only

    • Schools

    • schools

    • Microsoft Entra ID only

    Error email notifications

    You might want the script to send an email notification if an error occurs during user account creation. In this case, use the following code:

        $user | New-AdmUser -Path $targetDN -Server $domain `
            -AdaxesService localhost -ErrorAction Stop
    catch [System.Exception]
        $to = ""
        $subj = "Failed to Import User from CSV"
        $bodyText = "Adaxes failed to import user " + $user.Name + " from $file."`
            + "`nError: " + $_.Exception.Message
        $bodyHtml = $null
        $Context.SendMail($to, $subj, $bodyText, $bodyHtml)
        $Context.LogMessage($bodyText, "Error")

    For information on how to create scripts for business rules, custom commands, and scheduled tasks, see Server-side scripting.

    When done, click OK two times.

  10. Click Next.

  11. On the Activity Scope step, specify the organizational unit where imported user accounts will be created:

    • Click Add.

    • Select the target organizational unit.

    • In the Assignment Options dialog, select the The Organizational Unit object checkbox and clear the Objects located in the Organizational Unit checkbox.

    • Click OK two times.

    Using business rules you can automatically move newly created users to appropriate organizational units based on certain rules. For more details, see Automatically move users between organizational units.

  12. The activity scope of the scheduled task must include a single organizational unit! Otherwise the task will import user accounts to each OU included into the scope.

    Click Finish.

Default Property Values

With the help of property patterns you can assign a default value to any property of directory objects. If a user account is created during data import, and the value of a property is empty, the default value will be set for that property. For details, see:

See also