---
title: "What Azure Active Directory fields can be used when syncing with Opensense?"
slug: "what-azure-active-directory-fields-can-be-used-when-syncing-with-opensense"
description: "The Azure Active Directory (Entra ID) fields that Opensense can sync into signatures, with each field's Office 365 display name and LDAP name."
updated: 2024-01-12T20:11:01.000Z
canonical: "https://help.opensense.com/docs/what-azure-active-directory-fields-can-be-used-when-syncing-with-opensense"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.opensense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What Azure Active Directory fields can be used when syncing with Opensense?

## Overview

Opensense can sync these Azure Active Directory (Azure AD, now Microsoft Entra ID) fields into your signatures. The table lists each field's display name in Office 365 and its Lightweight Directory Access Protocol (LDAP) name.

## Fields you can sync

<div class="kb-deployment-compare kb-deployment-compare--plain">
  <div class="kb-deployment-compare__viewport" role="region" aria-label="Azure Active Directory fields and their LDAP names" tabindex="0">
    <table>
      <colgroup><col class="kb-deployment-compare__feature-col"></colgroup>
      <thead>
        <tr>
          <th scope="col">Office 365 display name</th>
          <th scope="col"><span class="kb-deployment-compare__method">LDAP name</span></th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <th scope="row">City</th>
          <td><code>city</code></td>
        </tr>
        <tr>
          <th scope="row">Company</th>
          <td><code>company</code></td>
        </tr>
        <tr>
          <th scope="row">Country or region</th>
          <td><code>co</code></td>
        </tr>
        <tr>
          <th scope="row">Department</th>
          <td><code>department</code></td>
        </tr>
        <tr>
          <th scope="row">Display name</th>
          <td><code>displayName</code></td>
        </tr>
        <tr>
          <th scope="row">Username / Email</th>
          <td><code>mail</code></td>
        </tr>
        <tr>
          <th scope="row">Fax number</th>
          <td><code>facsimileTelephoneNumber</code></td>
        </tr>
        <tr>
          <th scope="row">First name</th>
          <td><code>givenName</code></td>
        </tr>
        <tr>
          <th scope="row">Job title</th>
          <td><code>title</code></td>
        </tr>
        <tr>
          <th scope="row">Last name</th>
          <td><code>surname</code></td>
        </tr>
        <tr>
          <th scope="row">Mobile phone</th>
          <td><code>mobile</code></td>
        </tr>
        <tr>
          <th scope="row">Office location</th>
          <td><code>physicalDeliveryOfficeName</code></td>
        </tr>
        <tr>
          <th scope="row">Zip or postal code</th>
          <td><code>postalCode</code></td>
        </tr>
        <tr>
          <th scope="row">State or province</th>
          <td><code>state</code></td>
        </tr>
        <tr>
          <th scope="row">Street address</th>
          <td><code>streetAddress</code></td>
        </tr>
        <tr>
          <th scope="row">Office phone</th>
          <td><code>telephoneNumber</code></td>
        </tr>
        <tr>
          <th scope="row">Custom attributes 1–15</th>
          <td><code>extentionAttributes</code></td>
        </tr>
      </tbody>
    </table>
  </div>
</div>

## What's next

- [Syncing extension attributes from Azure AD (Entra ID)](https://help.opensense.com/docs/syncing-extension-attributes-from-azure-ad): sync custom attributes 1 to 15.
- [Why Active Directory changes take time to reach Opensense](https://help.opensense.com/docs/delay-in-ad-to-aad): why directory changes can take time to appear.
- [Field data priority](https://help.opensense.com/docs/field-data-priority): which data source a signature uses when a field has more than one value.