'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Active Directory and Entra ID Name Sync Issues in Outgoing Emails
Question details
Users need to resolve a synchronization issue where an updated surname in Active Directory and Entra ID does not reflect in the display name of outgoing SMTP emails.
- Product
- Active Directory / Microsoft Entra ID
- Device & OS
- not provided
- Scenario
- Updating a user's surname for a generic SMTP account across an enterprise directory environment.
- Observed behavior
- Outgoing messages continue to display the old surname, even though Microsoft Entra Connect reports no synchronization errors and the directory shows the updated information.
Ensure you have administrative privileges to access the Microsoft Entra Connect server and that the ADSync PowerShell module is properly imported on your machine.
Force an Initial Sync Cycle via PowerShell
Running an initial synchronization cycle forces Microsoft Entra Connect to comprehensively re-evaluate and push all directory attributes, ensuring updated email display names are accurately synced.
By default, Delta sync cycles might occasionally miss updates to specific display attributes if the baseline properties didn't trigger a full change alert. Forcing an Initial sync cycle overrides this behavior.
Right-click the Start menu on your Microsoft Entra Connect server, select Windows PowerShell (Admin), and confirm the User Account Control prompt.
Type the command 'Start-ADSyncSyncCycle -PolicyType Initial' and press Enter to trigger a full directory synchronization.
Wait for the synchronization cycle to complete. Note that Exchange Online may require additional time (up to a few hours) to update its global address lists and caching.
Send a test email from the generic SMTP account to an external or internal address to confirm the sender's display name now reflects the updated surname.
Maintain High Productivity with WPS Office
While resolving complex IT directory synchronization issues, ensure your daily document workflow is not interrupted. WPS Office provides a seamless, robust, and cost-free alternative to Microsoft Office, letting you create, edit, and share documents effortlessly.
- 1. Download the Installer: Visit the official WPS website and download the free WPS Office installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen instructions to complete the fast installation process.
- 3. Open and Edit Seamlessly: Launch WPS Office to directly open and edit your existing Microsoft Word, Excel, and PowerPoint files.
Frequently Asked Questions
Why does Microsoft Entra Connect report no errors even though the email surname didn't update?
Entra Connect may have successfully synced standard directory attributes (which triggers the 'no error' status), but failed to update specific Exchange-related display name properties due to caching or incremental sync limitations. An Initial sync forces a full evaluation.
How long does it take for a manual AD sync to propagate to outgoing emails?
While the AD to Entra ID synchronization takes about 30 minutes, updates to outgoing email display names can take up to 24 hours to fully propagate due to Exchange Online server caching and Offline Address Book (OAB) generation.
What should I do if the old surname returns after running the initial sync?
If the old surname reverts, it is likely being overwritten by a conflicting attribute in your on-premises Active Directory or a third-party HR system integration. Check the local AD attributes and consult Microsoft Q&A for advanced tracing guidance.
