Crossware Email Signature integrates seamlessly with Azure Active Directory (AAD) to automatically retrieve user details for email signatures. This ensures every message includes accurate, consistent, and up-to-date information. Since Microsoft 365 stores all user data in AAD, Crossware leverages this directory to access attributes for use in lookups within your signature designs.
How Lookup Configurations Work
-
The data you configure in Lookup Configurations is used by Crossware Email Signature to compile information for signatures.
-
Not all AD fields are available for use. this limitation is set by Microsoft. As Microsoft continues to expand AAD capabilities, more fields will become available.
-
To work around these restrictions, Azure AD Connect can synchronize custom on-premises AD attributes to Extension Attributes within AAD.
-
These Extension Attributes are accessible in Crossware Email Signature and can be referenced in lookups and rules. Learn more here.
Available Fields
The following table shows the fields currently available from AAD, what values are returned, and the corresponding lookup names that are pre-configured in Crossware.
|
AAD Field |
Value Returned |
Crossware Lookup Name |
|---|---|---|
|
Names and Title Fields |
|
|
|
givenName |
First name of the user. |
(!FirstName!) |
|
surname |
Last name (family name). |
(!LastName!) |
|
jobTitle |
User’s job title. |
(!Position!) |
|
displayName |
Display name shown in the address book (often first name + last name). |
(!DisplayName!) |
|
thumbnailPhoto |
Thumbnail photo of the user. |
(!ADImageThumb!) |
|
Email Information Fields |
|
|
|
|
User’s email address. |
(!Email!) |
|
Company Information Fields |
|
|
|
companyName |
Company name. |
(!Company!) |
|
department |
Department in which the user works. |
(!Department!) |
|
telephoneNumber |
Primary business phone number. |
(!Phone!) |
|
facsimileTelephoneNumber |
Business fax number. |
(!Fax!) |
|
mobile |
Mobile phone number. |
(!Mobile!) |
|
Address Information Fields |
|
|
|
streetAddress |
Street address of the user’s workplace. |
(!Street!) |
|
city |
City location. |
(!City!) |
|
state |
State or province. |
(!State!) |
|
postalCode |
Postal/ZIP code. |
(!PostalCode!) |
|
country |
Country/region (e.g., “US”, “UK”). |
(!Country!) |
|
Other Fields |
|
|
|
physicalDeliveryOfficeName |
Office location. |
(!OfficeName!) |
|
mailNickName |
User’s mail alias. |
(!MailNickName!) |
|
preferredLanguage |
User’s preferred language (ISO 639-1 code, e.g., en-US, en-NZ). |
Not configured |
|
usageLocation |
Two-letter country code (ISO 3166, e.g., US, JP, GB). |
Not configured |
|
otherMails |
List of additional email addresses. |
Not configured |
|
userPrincipalName |
User Principal Name (UPN) – an Internet-style login name (per RFC 822). |
Not configured |
Important Notes
-
Fields with values of null will not return data.
-
Field names are case-sensitive. Be sure to match them exactly.
-
Microsoft regularly updates AAD, which means more fields will become available for use in the future.