Forum Discussion
RyanSpoonerJCB
Sep 18, 2020Iron Contributor
User renamed on AD, name not updating in Microsoft Teams.
Hey all, hope you're all well. I've got a user who's AD account has been renamed (stephen.hawkes to steve.hawkes). This has been synced to Azure AD and reflects correctly in admin.microsoft.com ...
- Jan 14, 2022
D0ugW This issue is resolved for me. I had tried a number of things including things suggested by Microsoft tech support (see my previous post). Another team member suggested that I sign out of Teams and sign back in.
After doing this, the display names appear correctly on all my devices.
I don't understand the mechanism for this or why "Sign Out" had different impact than "Quit", but I am glad that this nuisance behavior is fixed for me.
Brian_Thomson
Jan 13, 2022Copper Contributor
We recycle accounts for temporary student employees which involves changing the display name. For some members of our Team, these updates are reflected in the Teams experience once all the syncs etc. have taken place. For some members of the Team, the display name is stuck on the old values. In attempts to resolve this we have:
- Restarted Teams (numerous times)
- Stopped Teams, deletes all Teams cache files, restarted Teams
- Removed these accounts from the Team, added them back in.
- Removed these accounts from the Team, removed them from chat history, added them back in.
This is a 20 member Team and the new display names update immediately for some, update after an extended period (several days) for others, never update for a few of us.
It seems like a minor thing but it is frustrating to have to have a post it note that says:
Ali=Zeynep
Eddy=Caleb
D0ugW
Jan 14, 2022Copper Contributor
I'm experiencing an identical issue. Students sign in under my organizational tenant as guests, and all students see the correct names. As reported in Vasil's earlier response, the initial backend sync has not been made as all users still show student IDs under members and guests.
- Brian_ThomsonJan 14, 2022Copper Contributor
D0ugW This issue is resolved for me. I had tried a number of things including things suggested by Microsoft tech support (see my previous post). Another team member suggested that I sign out of Teams and sign back in.
After doing this, the display names appear correctly on all my devices.
I don't understand the mechanism for this or why "Sign Out" had different impact than "Quit", but I am glad that this nuisance behavior is fixed for me.
- starbuckedApr 22, 2025Copper Contributor
I can confirm that three years later, this is still the solution, and obviously still an unfixed bug/error in Teams personal / free edition. We are seeing this problem all over the place as we migrate our business from Skype to Teams. We have a number of Skype / Microsoft accounts that are created by the employee role, not the person. So when there is a staff change (someone changes role, quits, gets hired), they take over that microsoft account and we have to update the display names. This wreaked havoc for us going through the Skype transition....
- GreenVomit8Apr 28, 2022Copper Contributor
When I first read Brian's solution, I thought the person's account that was not showing with updated details in MS Teams had to log out and back in again. This did not resolve the issue.
However, when I personally logged out of my MS Teams client app and back in again the problem account details were immediately updated. In this case it was the 'Job Title'.I suspect there is a MS Teams client app caching issue that resolves once you log out and back in again. This is a bit frustrating as all users would need to log out and back in again to MS Teams for any user change to be displayed correctly to all users.
- Kevin TaberAug 03, 2022Copper Contributor
This worked in our situation as well. The OTHER users had to sign out, not quit, to get the updated name to show. Weeks had gone by and the others still didn't see the change. So yes this is a bummer when there are a lot of users that need to sign out.
- dliedkeMar 10, 2022Copper ContributorThanks a lot, worked fine here!