User Logon Name

The User Logon Name rule is used to define how the cn, userPrincipalName and sAMAccountName LDAP attributes will be defined during user provisioning

This rule allows you to specify multiple naming formats to use for scenarios where the user logon name may already be in use by another user. Remember that each user logon must be unique, so be sure to provide additional naming formats to avoid a conflict and failure point.

If required you can use different formats for sAMAccountName and cn (Common Name) as shown below.

Connect to AD will load default naming formats, which are evaluated from the top down during provisioning. You can change each one of these as required by your security policies.

The default naming formats are:

Person.PreferredName + '.' + Person.LastName
john.doe
Person.PreferredName + '.' + Person.LastName + '1'
john.doe1
Person.PreferredName + '.' + Person.LastName + '2'
john.doe2
Person.PreferredName + '.' + Person.LastName + '3'
john.doe3
Person.PreferredName.SubString(0,1) + '.' + Person.LastName
j.doe
Person.PreferredName + '.' + Person.LastName.SubString(0,1)
john.d
Person.PreferredName + '_' + Person.LastName
john_doe
Person.PreferredName + Person.LastName
johndoe
Employment.EmployeeNumber
001234
Person.LastName + Person.DateOfBirthYear
doe75
Person.LastName + '.' + Person.DateOfBirthYear
doe.75
Person.LastName + '_' + Person.DateOfBirthYear
doe_75

The logon name value that is used during provisioning is available to be used in other mappings via the User.userPrincipalName or User.userPrincipalNamePrefix field.

In this example below the Mail mapping references the User.userPrincipalName field to define the users mail attribute value. 

User.UserLogonNamePrefix

In this example below the Mail mapping references the User.userPrincipalNamePrefix field to define the users mail attribute value. 

User.UserLogonNamePrefix + "@example.com"

Next User Logon Name Suffix