homePhone Attribute still displaying in MS Teams for some users

Question

I'm currently implementing Mitel Revolution which uses a AD Sync to pull telephone numbers into the system for SMS texting. I had started to enter personal cellphones into the homePhone attribute field of our Local AD and noticed it was showing up inside Microsoft Teams when you hover over someone's emblem and look at their contact information. I went into my AD Connect and stopped the replication of this attribute before I continued on with my project of getting the data entered into AD.

The thing I'm noticing is a few users are still having their homePhone display even though it's no longer syncing. I went out and looked around to see where it could be removed and after using PowerShell to go into MSGraph and AzureAD I can't see any record of this attribute listed, yet it persists to show up, even though I'm not seeing it in AzureAD or anywhere else.

How do I PURGE this field from MS Teams when it displays contact information. It's been over 48 hours; I've cleared my Team's cache in case that was the issue but it's still hanging around and I want to keep this information confidential.

Answer 1

Hi @Nathan Glassburner

Please try to synchronize the updates of local AD to Azure AD.

You can also go to M365 admin center to modify the user's personal information:

---

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.

---

Answer 2

@Nathan Glassburner , did you ever find a resolution for this issue, we are seeing the same thing for one of our users. We have provisioned a new phone number in Teams but the old phone number still shows up in the Home Phone attribute in the profile card. The attribute is NOT populated in AD on-prem or in Entra ID. The old phone number is also assigned to a new user so we don't want to just delete it completely as a test.