Teams contact card showing incorrect mobile number

When you encounter an issue where Microsoft Teams is showing incorrect contact information, despite the correct information being updated in various Microsoft 365 Admin tools, it could be due to several reasons. Here are some steps you can take to troubleshoot and resolve the issue:

Syncing Delays:

Changes in Microsoft 365 may take some time to propagate to all services, including Teams. It's possible that there's a syncing delay. Give it some time and check if the correct information is eventually reflected in Teams.
User Attributes in Azure AD:

Verify that the correct mobile number is set in the user attributes in Azure Active Directory (Azure AD). Teams relies on Azure AD for user information.
Force a Directory Synchronization:

Force a manual synchronization of your Azure AD directory to ensure that the latest user attributes are synced to Teams. You can do this using the Azure AD Connect tool.
Teams PowerShell Module:

Use the Teams PowerShell module to check and update user information. The Set-CsPhoneNumber cmdlet can be used to update the phone number for a user.
powershell
Copy code
Set-CsPhoneNumber -Identity email address removed for privacy reasons -PhoneNumber +155555514
Teams App Cache:

Teams has its cache, and sometimes, issues can be related to cached data. Try clearing the Teams cache:
Close the Teams app.
Navigate to the following path and delete the contents: %appdata%\Microsoft\Teams\Cache.
Teams Mobile App:

If users are accessing Teams on mobile devices, ensure that they are using the latest version of the Teams mobile app. Sometimes, discrepancies can occur between the desktop and mobile versions.
Contact Card in Outlook:

Check if the incorrect number is also shown in the contact card in Outlook. If it's incorrect there, it might indicate an issue with the data source or synchronization.
Check for Custom Policies:

Review any custom policies or settings related to Teams in the Microsoft 365 Admin Center that might affect contact information.
Support from Microsoft:

If the issue persists, consider reaching out to Microsoft Support. They can provide more in-depth assistance and investigate if there are any service-specific issues causing the discrepancy.
Remember to approach any changes cautiously, especially when dealing with PowerShell commands that can affect user attributes. Always verify and test in a controlled environment before applying changes in a production environment.