Why Your Email Signatures Are Wrong: Messy Entra ID Data
On this page · 10 sections
- Where your email signature gets its details from
- Which Entra ID attributes end up in a signature
- The seven most common attribute problems
- Hybrid tenants: why your fix does not show up
- How to audit your Entra ID attributes in an afternoon
- Who should own each attribute
- Keeping attributes clean when people join, move and leave
- Why wrong signature details are a compliance problem too
- What to do next
- Frequently asked questions
TL;DR: A directory-driven email signature does not store anyone’s details. It reads them from Microsoft Entra ID each time it builds the signature, so it is only as accurate as your directory. Most wrong signatures come from seven common data problems, such as blank fields, departments spelled three ways and job titles nobody updated after a promotion. In hybrid tenants there is an extra trap: fixes made in the cloud do not stick. You can audit the whole directory in an afternoon with an export and a short checklist. Keeping it clean means naming one owner per field and making “update the directory” part of every joiner, mover and leaver change.
You switched on centrally managed signatures, and now the complaints arrive. The sales director’s signature says “Account Manager”, her job title from four years ago. Half the finance team has no phone number. A new starter’s signature names a manager who left in the spring.
The signature tool is doing exactly what it was built to do. It copies what your directory says. This article explains where those details come from and which problems we see most often. Then it shows how to find every bad record and stop them coming back.
Where your email signature gets its details from
Most signature tools for Microsoft 365 build each person’s signature from their user account in Microsoft Entra ID (formerly Azure AD, Microsoft’s cloud directory of staff accounts). They usually read it through Microsoft Graph, the programming interface Microsoft provides for Microsoft 365 data.
The tool does not keep its own copy of anyone’s job title. It reads the directory when it builds the signature. A server-side tool does this as the email passes through it after sending. An add-in does it while the person writes the email in Outlook. Server-side vs add-in explains the difference.
Either way, the result is the same. The signature is exactly as accurate as the directory. Microsoft says the same profile appears across Outlook, Teams and Windows, so a wrong job title in Entra ID is already wrong in other places. A signature puts it on every email that leaves your organisation.
A signature tool does not make your directory wrong. It shows everyone that it already was.
Which Entra ID attributes end up in a signature
Each field in a signature maps to a property on the user account. Microsoft calls these properties “attributes” in some places. The table shows the usual mapping, using the property names from Microsoft Graph’s user resource.
| Signature field | Graph property | Returned by default? | Common problem |
|---|---|---|---|
| Name | displayName (also givenName, surname) | Yes | Legal name instead of the name the person uses |
| Job title | jobTitle | Yes | Not updated after a promotion |
| Department | department | No, must be requested | Spelled several ways |
| Company | companyName | No, must be requested | Blank, or the wrong legal entity |
| Office | officeLocation | Yes | Free text, so “London”, “LDN” and “London HQ” |
| Office phone | businessPhones | Yes | Mixed formats |
| Mobile | mobilePhone | Yes | Mixed formats, or stuck on an old number in hybrid tenants |
| Address | streetAddress, city, state, postalCode, country | No, must be requested | Blank for most people |
| Manager | manager (a relationship, not a property) | No, separate request | Points to someone who has left |
Two details in that table explain some odd behaviour.
Some fields are not returned unless asked for. When an app asks Graph for a user, it gets a short default set of properties. Department, company and address are not in it. A tool has to request them by name. If a signature shows a job title but never a department, check which fields the tool supports before you blame the data.
The manager is a link to another account. It is not a text field on the user. A tool has to make a separate request to follow that link, so some tools cannot show a manager at all. When a manager leaves, what happens depends on the account. If it is only disabled, the link still points to it, and signatures keep naming the leaver. If it is deleted, the link is removed and the manager line is blank.
businessPhones also behaves oddly. It is a list, but Microsoft’s documentation says only one number can be set in it. If your template has space for two office numbers, the directory cannot fill both.
The seven most common attribute problems
These are the problems that most often make a directory-driven signature look wrong.
- Blank fields. The account was created with a name and an email address, and nobody filled in the rest. Microsoft notes that only a few details are added when a user is created. The signature then shows an empty line, or a label with nothing after it.
- The same thing written several ways. “Sales”, “sales”, “Sales & Marketing” and “S&M” are one team to a person and four teams to a computer. This breaks more than looks. A rule that picks a banner or a disclaimer by department quietly skips anyone whose spelling does not match.
- Phone numbers in mixed formats. “07700 900123”, “+44 7700 900123” and “+447700900123” are the same number, but they look careless side by side. For anyone outside the UK, only the international format can be dialled.
- Stale job titles. Promotions are agreed in HR and announced in a meeting. Nobody tells IT. The directory still says “Junior Analyst” two years later.
- Managers who have left. The leaver’s account is disabled or deleted, but the people who reported to them still point to it.
- Leavers who still look current. An account that is still enabled can still send email, with a full signature. A disabled account that was converted to a shared mailbox can still send as well, if someone has been given permission. The signature then names a person who left months ago.
- Shared and room mailboxes with a person’s details. Someone copied an existing user when setting up the “accounts@” mailbox. Now every email from accounts@ carries a named person’s job title and mobile number.
Each of these is easy to fix once you can see it. The audit section below shows how to find them all at once.
Hybrid tenants: why your fix does not show up
Many organisations of 50 to 250 people still run Active Directory on their own servers and copy it to Entra ID with Microsoft Entra Connect. This is called a hybrid set-up. If yours works this way, there is a rule that catches most admins out at least once.
For synced users, the on-premises directory wins. Microsoft’s guidance on updating a user’s profile covers users whose source of authority is Active Directory. For them, you must change identity, contact and job details in Active Directory. Then you wait for the next sync. Entra Connect runs a sync every 30 minutes by default.
So change job titles, departments and phone numbers in Active Directory itself, using whatever tool your team uses for on-premises AD. Changing them in the Entra or Microsoft 365 admin centre either fails or does not last. The signature keeps showing the old value, and it looks like the signature tool is broken.
The mobile number that will not update
Mobile numbers have their own trap, which Microsoft documents in its guidance on the BypassDirSyncOverridesEnabled feature.
In the past, admins and users could change a synced user’s mobile number directly in the cloud, for example from a Microsoft 365 profile page. When that happened, Entra ID marked the number as overridden. From then on, it ignored any change to that person’s mobile number coming from Active Directory. Microsoft calls this behaviour “DirSyncOverrides”.
Microsoft says these cloud changes are no longer possible for synced users. But accounts that were changed before still carry the flag. That means:
- you correct someone’s mobile number in Active Directory
- Entra Connect reports a successful sync, with no errors
- Entra ID, and so the signature, keeps the old number
To find the affected people, Microsoft provides a command called Compare-ADSyncToolsDirSyncOverrides in its ADSyncTools PowerShell module. It needs Entra Connect version 2 or later. It writes a list of every synced user whose mobile number differs between Active Directory and Entra ID.
The fix is a tenant setting, BypassDirSyncOverridesEnabled, which tells Entra ID to accept the Active Directory values again. Be careful with it. Turning it on overwrites the cloud number with the Active Directory number for every affected user. Some of those cloud numbers may be the newer, correct ones. Review the list first, copy any newer numbers into Active Directory, and only then turn the setting on. Microsoft’s guidance walks through each step.
How to audit your Entra ID attributes in an afternoon
You do not need a tool for this. You need an export of your users, a spreadsheet and the checklist below.
- Export your users. In the Microsoft Entra admin centre, go to Entra ID > Users > All users and select Download users to get a CSV file. It includes job title, department, address and phone fields, but not each person’s manager. If you are comfortable with Microsoft Graph PowerShell, the
Get-MgUsercommand can export the same data, plus each person’s manager and last sign-in date. Ask for the fields your signature uses by name, because some are not returned by default. - Filter out accounts that are not people. Separate shared mailboxes, room mailboxes and service accounts. You will check them for a different problem.
- Work through the checks in the table below, one column at a time.
- Fix in the right place. For cloud-only users, use the admin centre. It can edit up to 60 users at once for fields such as job title, department, company name and office location. For synced users, fix the values in Active Directory.
- Check a few signatures afterwards. Send a test email from three or four of the corrected accounts. Make sure the change reached the signature.
| Field | What to look for | How to fix it |
|---|---|---|
| Any field your signature uses | Blank cells | Fill in from HR records. If a field is often empty, decide whether the signature needs it at all. |
department, officeLocation, companyName | Several spellings of one value | Sort the column and list the distinct values. Agree one spelling for each and fix the rest. |
businessPhones, mobilePhone | Mixed formats, missing country codes | Pick one format, such as +44 20 7946 0000, and apply it to everyone. |
jobTitle | Titles HR says are out of date | Send each manager a list of their team’s titles and ask them to confirm. |
| Manager | Managers who are disabled or deleted | Ask HR for the current reporting line and update it. |
| Account status and last sign-in | Enabled accounts with no recent sign-ins | Check with HR whether the person has left. Disable or convert the account through your leaver process. |
| Shared and room mailboxes | A person’s job title or phone number | Clear the personal details, or give the mailbox a team name and number. |
The last sign-in date comes from a property called signInActivity. Microsoft’s documentation says it needs a Microsoft Entra ID P1 licence, which Microsoft 365 Business Premium includes. Without one, check for leavers against HR’s list instead.
Who should own each attribute
Most directory data goes wrong because nobody owns it. IT owns the accounts, but IT does not know when someone is promoted. HR knows, but often cannot edit the directory.
Name one source of truth for each field. For most organisations it looks like this:
| Field | Usually owned by | Changes when |
|---|---|---|
| Name, job title, department, manager | HR | Someone joins, is promoted or moves team |
| Company, office location, address | HR or Operations | Someone moves office or legal entity |
| Office phone, mobile | IT | A number is issued or changed |
| Account status | IT, triggered by HR | Someone leaves |
The owner does not have to make the change themselves. What matters is that the owner tells the person who can, every time, through a set route. Who should own email signatures? covers the wider question of who is accountable for signatures as a whole.
If you run more than one company from one tenant, companyName carries extra weight, because it often decides which legal details appear. Email signatures for multiple companies covers that set-up.
Keeping attributes clean when people join, move and leave
A one-off clean-up fixes today’s data. Keeping it clean means changing how updates happen. The joiner, mover and leaver process (often shortened to JML) is where to do it.
- Joiners. Make “complete the directory record” a step in the new-starter checklist, before the account is handed over. A new joiner’s first emails go to clients too. Email signatures for HR teams explains why the first week matters.
- Movers. Make “update the directory” part of signing off a promotion or team move, not something HR remembers later. This is the step that is most often missed.
- Leavers. Disable the account on the last day. Reassign anyone who reported to the leaver to a new manager in the same change.
- Fixed lists. Keep an agreed list of department and office names. Pick from it rather than typing.
- A quarterly check. Run the audit above every three months. The second time takes far less work than the first.
Can you automate it?
Partly, depending on your licences.
If your HR system has a connector, Microsoft’s HR-driven provisioning can copy details such as job title and department from HR into the directory. Then HR’s record is the only one anybody updates.
Microsoft’s Lifecycle Workflows can also update attributes automatically when someone joins, moves or leaves. But they need Microsoft Entra ID Governance or Microsoft Entra Suite licences. Most organisations of 50 to 250 people on Business Premium do not have either. Lifecycle Workflows also cannot change the built-in fields, such as job title, on users synced from on-premises Active Directory. For most readers, the manual process above is the realistic default. If user changes take up a lot of your week, a third-party console can speed them up: our Microsoft 365 admin tools roundup compares the options.
Why wrong signature details are a compliance problem too
A signature is personal data that your organisation publishes on every email. Under UK GDPR, personal data must be accurate and, where necessary, kept up to date. The ICO’s guidance on the accuracy principle explains what that means in practice. A wrong job title, or a leaver’s name still going out on email, is an accuracy problem as well as a brand one.
There is a second risk. Some organisations choose a disclaimer or a regulatory notice based on the sender’s department or company. When those fields are wrong, people get the wrong legal wording, and nobody notices. Disclaimers by department, office or country explains how those rules match on directory fields.
Accuracy also links to how much data a signature tool reads. A well-built tool reads only the fields it shows. Email signature tools and GDPR covers what a tool should and should not read from your directory, and what to ask the vendor.
What to do next
If you have not yet seen how your signatures look today, start there. How to audit your team’s email signatures takes five minutes and shows the real signatures people send. Put the results next to your directory export. You will see which problems come from the data and which come from people setting their own signatures.
If you are about to choose a signature tool, ask how it handles directory data. The directory sync section of the email signature software buying checklist lists the questions. If you would rather run signatures yourself, Set-OutlookSignatures reads the same attributes from Active Directory or Graph, so the same clean-up applies. The complete guide to centralised signatures in Microsoft 365 covers the wider set-up.
Frequently asked questions
Should people be able to change their own job title?
We recommend that they cannot. A job title in a signature is a statement your organisation makes to clients. It should match what HR has agreed. Let people ask HR for a change, and let HR’s record drive the directory. Fields such as pronouns or a preferred first name are different, and you may want people to control those.
How long does a change take to reach the signature?
It depends on two things. For a hybrid user, a change in Active Directory reaches Entra ID at the next Entra Connect sync, every 30 minutes by default. A cloud-only change is in Entra ID straight away. Then the signature tool has to pick it up. Some read the directory each time they build a signature, and others sync on a schedule. Ask your vendor which it does.
Does a signature tool need write access to Entra ID?
No. Building a signature only needs permission to read user details, such as Microsoft Graph’s User.Read.All. If a tool asks for permission to write to your directory, ask the vendor what it writes and why. Some tools offer extras, such as letting people edit their own details, that need more access. Decide whether you want those before you grant it.