Forum Discussion
Copilot using first name instead of preferred name in meeting summary
How to force Copilot to use preferred display name in meeting summaries ?
The above is rubbish (more likely generated by a cheap AI)!
It’s important to note that there is currently no universal standard for how Microsoft apps display user names. For example, the Teams app typically uses the “displayName” property, while Copilot and several other services concatenate the “givenName” and “sn” (surname) attributes to form the full name. This inconsistency can be confusing, especially since some applications—such as Project Online—will always use “givenName” + “sn”, regardless of any updates made to the user profile.
Additionally, many organisations restrict updates to these profile fields because they are synchronised with HR systems. As a result, users may notice discrepancies in how their name appears across different Microsoft services, and this often leads to IT support being contacted about issues that are, in fact, due to these underlying platform differences.
Unless all three attributes (“displayName”, “givenName”, and “sn”) are updated to reflect the desired name format—and your organisation’s policies and synchronisation settings allow these changes—you may continue to see inconsistencies in how names are displayed across Microsoft 365 apps.
3 Replies
1. Check the Microsoft 365 profile:
2. Sign in to your Microsoft 365 account
Click on the user's avatar in the top right corner and select My Account.
Under Personal Information, check and update the Preferred Name.
Synchronize Azure Active Directory (AAD):
If the organization uses Azure AD, ensure that the Preferred Name is synchronized:
Log in to the Azure AD Administrator Center
Navigate to Users > All Users and locate your account.
Click Edit and update the Display Name and Preferred Name in the Name section.
Save the changes and wait for the synchronization to complete
2. Check the Teams profile:
Open Microsoft Teams, click on the user's avatar in the upper right corner and select Settings.
In the General tab, check that the Name is correctly displayed as the preferred name.
If not, manually update and save.
3. Regenerate the meeting summary:
In Teams, find the relevant meeting and try to regenerate the summary.
If the problem persists, wait for the next meeting or edit the summary manually.
4. Contact Microsoft Support:
If the issue remains unresolved, submit a support request through the Microsoft 365 Administrator Center.
Provide detailed error messages and screenshots to quickly diagnose the issue.The above is rubbish (more likely generated by a cheap AI)!
It’s important to note that there is currently no universal standard for how Microsoft apps display user names. For example, the Teams app typically uses the “displayName” property, while Copilot and several other services concatenate the “givenName” and “sn” (surname) attributes to form the full name. This inconsistency can be confusing, especially since some applications—such as Project Online—will always use “givenName” + “sn”, regardless of any updates made to the user profile.
Additionally, many organisations restrict updates to these profile fields because they are synchronised with HR systems. As a result, users may notice discrepancies in how their name appears across different Microsoft services, and this often leads to IT support being contacted about issues that are, in fact, due to these underlying platform differences.
Unless all three attributes (“displayName”, “givenName”, and “sn”) are updated to reflect the desired name format—and your organisation’s policies and synchronisation settings allow these changes—you may continue to see inconsistencies in how names are displayed across Microsoft 365 apps.Your answer is correct. The problem was HR system. My issue is resolved as "unfixable" status a few months ago because the limitation is the HR system they require the legal name for travel purposes, and it conflicts with other apps displaying the whole legal name in service now tickets and other applications due to one change in a portal.
My problem is definitely this "many organisations restrict updates to these profile fields because they are synchronised with HR systems." and Microsoft is lazy to fix their limitations.
