Forum Discussion
Copilot using first name instead of preferred name in meeting summary
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.
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.