Short answer:
To use a custom attribute from Active Directory or Entra ID (Azure AD) in Xink, you must first identify the correct property name and then map it to a custom field in Xink.
When is this needed?
This applies to hybrid environments where custom attributes exist in Active Directory (on-premises) or Entra ID (Azure AD), and you want to use them in Xink email signature templates.
Step 1: Find the Entra ID (Azure AD) property name
- Go to the Microsoft Graph Explorer.
- Sign in with a Global Admin account.
- Accept the required permissions if prompted.
- Change the API version from v1.0 to beta.
- In the query field, enter a request using the user’s User Principal Name (UPN).
- Run the query and locate your custom attribute in the response (often shown as an extension property).
Alternative: Use PowerShell
You can also retrieve extension attributes using PowerShell:
Get-AzureADUser -SearchString user@domain.com | Select -ExpandProperty ExtensionProperty
Step 2: Create and map the field in Xink
- Go to Preferences > Fields in the Xink portal.
- Click the + icon to create a new field.
- Paste the Entra ID property name into the Property Name field.
- Click Save.
Step 3: Verify the sync
The custom field will be populated after the next Entra ID (Azure AD) sync.
Explanation
Custom attributes from Active Directory are synchronized to Entra ID as extension properties. Xink can read these values when the correct property name is mapped to a custom field.
Once mapped, the data can be used dynamically in email signature templates.
