Why do updates to Azure AD (now Microsoft Entra ID) not sync to Teams desktop client profile card ?

Scott Beane 21 Reputation points
2023-07-27T17:53:49.8433333+00:00

Hello,

We're a company using a Hybrid configuration and have deployed the Microsoft Teams desktop client to our user community. Periodically we receive calls about information on the profile card in Teams being out of date (often job title) and in some cases the data is reportedly incorrect weeks after the updated data has been synced from on-premises Active Directory to Azure AD. We've found that running a script to clear the local Teams cache typically fixes the problem but I wanted to ask why the sync of the data to the desktop client is failing and what might be done to improve the odds of updated data being displayed in the desktop Teams client.

Regards,

Scott

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
10,869 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. LiweiTian-MSFT 23,925 Reputation points Microsoft Vendor
    2023-07-28T02:19:42.4766667+00:00

    Hi @Scott Beane

    According to the document, after user attributes are updated in Microsoft Teams, users continue to see the old information in the Teams client. User attributes include information such as display name, telephone number, manager, and profile photo.

    This behavior is by design.

    Teams has a caching scheme that is designed for capacity and performance optimization. The Teams service caches general user information for up to three days. The Teams client also caches general user information locally. Some data, such as display name and telephone number, can be cached up to 28 days in the client. Profile photos can be cached up to 60 days.

    In order to better avoid this problem, our suggestion is to clear the Teams cache regularly.

    User's image


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


    2 people found this answer helpful.

  2. Q&A Assist
    2023-07-27T17:53:49.8433333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    According to Microsoft, the behavior of the Teams client caching scheme is designed for capacity and performance optimization. User attributes such as display name, telephone number, manager, and profile photo are cached for up to three days and general user information can be cached locally for up to 28 days. Profile photos can be cached locally for up to 60 days. If there is a delay in the update of Azure Active Directory data to the Teams cache, users may continue to see the old information in the Teams client for some time. To clear the cache and receive updated information, sign out of Teams and then sign back in or manually clear the Teams cache. Running a script to clear the local Teams cache is a suitable workaround. Microsoft is aware of these types of issues and is working on improving the pipeline between Azure AD and the Teams cache.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.