Entra ID Import Mappings

When importing data from Entra ID into Totalview, the mappings listed in below table are used.

The grid also shows if the default mappings can be changed.

Mappings are defined in the Totalview Active Directory connector setup.

Totalview Field	Mapping Change Supported	Mapping Field	Entra ID Field	Description
Enabled	No		accountEnabled	If not enabled, and the user is known to Totalview, the user will be deactivated in Totalview. And vice versa.
Group caption	No		displayName	Group’s display name
Name	Yes	FIRSTNAME	givenName	First name of user
Surname	Yes	LASTNAME	surname	Surname of the user
Calendar ID	Yes	DEFAULTSMTP	proxyAddresses (the first in list, if multiple)	Calendar ID for the user. Used for Microsoft 365 or Google Calendar synchronization.
Win Login	No		onPremisesSamAccountName (fallback to mailNickname)	User’s Windows login id
UserId	No		onPremisesSamAccountName (fallback to mailNickname)	User’s Totalview user id
Work	Yes	WORK	businessPhones	User’s work number.
Local	Yes	LOCAL	businessPhones	User’s local number. Conversion rules can be applied to the local number.
e-mail	Yes	EMAIL	mail	User’s email address
Homepage	Yes	HOMEPAGE	N/A	User’s homepage
Fax	Yes	FAX	faxNumber	User’s fax number.
Home	Yes	HOME	N/A	User’s home number.
Mobile	Yes	MOBILE	mobilePhone	User’s mobile number.
Sip	Yes	SIP	imAddresses (the first in list, if multiple)	User’s sip address.
User picture	No		N/A	User’s profile picture. Synchronization of user’s profile picture is not part of daily sync. To import picture from Entra ID, it must be done from end user’s client, via User Settings page in clients (Normal, Contact Center, Switchboard). See The User Settings page.

Supported Entra ID Mapping Fields

Fields are documented on user resource type.

accountEnabled

ageGroup

assignedLicenses

assignedPlans

businessPhones

city

companyName

consentProvidedForMinor

country

createdDateTime

creationType

customSecurityAttributes

deletedDateTime

department

displayName

employeeHireDate

employeeLeaveDateTime

employeeId

employeeOrgData

employeeType

externalUserState

externalUserStateChangeDateTime

faxNumber

givenName

id

identities

imAddresses

jobTitle

mail

mailNickname

mobilePhone

officeLocation

onPremisesImmutableId

onPremisesLastSyncDateTime

onPremisesProvisioningErrors

onPremisesSamAccountName

onPremisesSecurityIdentifier

onPremisesSyncEnabled

onPremisesUserPrincipalName

otherMails

passwordPolicies

passwordProfile

postalCode

preferredLanguage

provisionedPlans

proxyAddresses

serviceProvisioningErrors

securityIdentifier

state

streetAddress

surname

usageLocation

userPrincipalName

userType

Supported Extensions

Importing data from Entra ID into Totalview supports two types of extensions: Extension Attributes and Directory Extensions.

More general information about extensibility can be found at https://learn.microsoft.com/en-us/graph/extensibility-overview

Extension Attributes

Microsoft Entra ID offers a set of 15 extension attributes, these can also be used in the Totalview Active Directory connector. To map to these extension attributes, use the naming onPremisesExtensionAttributes:extensionAttribute{ExtensionNumber}, there are only 15 extension attributes available, so the extension number needs to between 1 and 15.

Directory Extensions

Directory Extensions can be created when synchronizing through Microsoft Entra Connect. The extensions always follow the naming scheme extension_{ApplicationId}_<attributeName>, where ApplicationId is the application identifier of your Tenant Schema Extension App.

More info on Directory Extensions can be found at https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-directory-extensions