Skip to content

displayName returns and emtpy string calling https://graph.microsoft.com/v1.0/$metadata#chats('chatIDx')/messages #82

Description

@Ashlesha-MSFT

Hi there,
we are developing an app that shows Microsoft Teams chats within an Atlassian Jira issue, so people can chat from Jira back and forth. This is basically an iframe.
When displaying this iframe we use different Ms Graph API calls to show user names, messages etc.

For one customer last week we were facing a situation where certain displayNames of users within these chats couldn't be retrieved and returned an empty string.
When we do the following call for getting the messages via graph:

“https://graph.microsoft.com/v1.0/$metadata#chats('chatIDx')/messages"

The “displayName” of one user (A) is simply empty. In the following screenshot I highlighted the missing name (first for the one user that is missing the displayName (A) and the existing name for the other; I needed to blur them due to data sensitivity):

Image
When we however call the user information for the missing user A via Microsoft Graph we are getting the display Name correctly.

When our customer tries to reproduce this the name is showing up correctly for new chats.

Please note: this did not happen only for one user in this environment but also for other users but they are now working fine.

Would be happy to learn why this can fail and what the reasons might be?

Activity

  1. atktroubleshootingapp commented on Sep 29, 2026

    @atktroubleshootingapp

    👋 Hi @Ashlesha-MSFT,

    Thank you for reporting this issue. Here is an AI-generated initial response:

    Classification: By design — Microsoft Graph documents that a chat message sender’s displayName is not always present. That explains why the integration must handle a missing name, but not why these particular messages lack one.

    • The reporter observes that the same users have names in their Graph user profiles and that new chats show names. Neither observation establishes the cause of the older messages’ empty values.
    • The quoted .../$metadata#chats('chatIDx')/messages looks like the response’s @odata.context, not the request URL. The documented request is GET /chats/{chat-id}/messages.

    What to do now:

    1. If from.user.displayName is blank, use from.user.id to look up the profile name where permitted; handle messages with no user sender separately.
    2. If the discrepancy persists, capture a redacted response, actual request URL, message ID, timestamp, and Graph request-id for support. The specific cause remains unverified.

    Useful links:


    Note: AI-generated guidance may be incomplete or incorrect. Please verify suggestions before applying them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    AI-generated responseAn AI-generated response has been posted to this issue.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions