SOLVED

User renamed on AD, name not updating in Microsoft Teams.

%3CLINGO-SUB%20id%3D%22lingo-sub-1682972%22%20slang%3D%22en-US%22%3EUser%20renamed%20on%20AD%2C%20name%20not%20updating%20in%20Microsoft%20Teams.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1682972%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20all%2C%20hope%20you're%20all%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20got%20a%20user%20who's%20AD%20account%20has%20been%20renamed%20(stephen.hawkes%20to%20steve.hawkes).%26nbsp%3B%20This%20has%20been%20synced%20to%20Azure%20AD%20and%20reflects%20correctly%20in%20admin.microsoft.com%20and%20on%20the%20Azure%20portal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20in%20Microsoft%20Teams%20he%20continues%20to%20be%20shown%20as%20Stephen%20not%20Steve.%20Two%20days%20after%20the%20rename.%26nbsp%3B%20I've%20forcibly%20signed%20him%20out%20of%20all%20sessions%20to%20ensure%20he's%20logging%20in%20fresh%2C%20but%20he%20still%20shows%20as%20Stephen.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnecdotally%20I've%20read%20in%20various%20forums%20(including%20here)%20that%20it%20can%20take%20Teams%20several%20days%20to%20pick%20up%20account%20changes%20such%20as%20the%20display%20name%2C%20profile%20picture%2C%20etc.%26nbsp%3B%20Why%20is%20this%3F%26nbsp%3B%20What%20can%20I%20do%20about%20it%3F%26nbsp%3B%20More%20importantly%20what%20are%20Microsoft%20doing%20about%20it%3F%20It's%20really%20poor.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1682972%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1684790%22%20slang%3D%22en-US%22%3ERe%3A%20User%20renamed%20on%20AD%2C%20name%20not%20updating%20in%20Microsoft%20Teams.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1684790%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20multiple%20syncs%20that%20need%20to%20happen%20on%20the%20backend%2C%20and%20there's%20nothing%20you%20can%20do%20until%20they%20complete.%20Then%2C%20there%20is%20the%20client%20cache%20factor%2C%20which%20might%20add%20additional%20delays.%20If%20you%20can%20see%20the%20new%20name%20in%20the%20Teams%20admin%20center%2C%20you%20can%20assume%20the%20backend%20sync%20is%20done%2C%20so%20you%20can%20try%20clearing%20Teams%20cache%20or%20open%20a%20private%20session%20in%20the%20browser.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

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 and on the Azure portal.

 

However, in Microsoft Teams he continues to be shown as Stephen not Steve. Two days after the rename.  I've forcibly signed him out of all sessions to ensure he's logging in fresh, but he still shows as Stephen.

 

Anecdotally I've read in various forums (including here) that it can take Teams several days to pick up account changes such as the display name, profile picture, etc.  Why is this?  What can I do about it?  More importantly what are Microsoft doing about it? It's really poor.

 

 

2 Replies
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

There are multiple syncs that need to happen on the backend, and there's nothing you can do until they complete. Then, there is the client cache factor, which might add additional delays. If you can see the new name in the Teams admin center, you can assume the backend sync is done, so you can try clearing Teams cache or open a private session in the browser.

@Ryan Spooner 
We're having the same problem.
I suppose the result of software being designed by only males.

We have found that Teams will only update names changes when people log out of Teams and back in. (fat client) this may include password resets on expiry.
We have seen Days greater than 3  days so far where a name has changes in the directory but when people do mentions it still uses the old name..

Worse yet other 3rd party cloud systems that have sso setup typically only uses the email so the users will now lose access to the old data or needs to manage two accounts and manually move data around between old account and new account.

Maybe people should just stop changing their names from now on.