Check Azure AD Sync: Ensure that Azure AD Connect (or any other sync tool you might be using) is running without any errors and that the sync cycle has completed successfully. This ensures that changes made in Okta are properly propagated to Azure AD and subsequently to Microsoft Teams.
Check User Attributes in Azure AD: Confirm that the name attribute you updated in Okta is correctly mapped to the corresponding attribute in Azure AD. The most common attribute for a user's display name is "DisplayName." Double-check that it is correctly synchronized with Okta.
Wait for Replication: After making changes in Azure AD, it can take some time for the changes to propagate throughout the Microsoft 365 services. This is especially true for display name changes, and it might take a few hours for the updates to appear in Microsoft Teams.
Teams Client Update: Make sure that all users have the latest version of the Microsoft Teams client installed. Outdated clients might not reflect changes immediately.
Force Teams Address Book Update: If you've waited for a reasonable amount of time, and the changes are still not reflecting in Teams, you can try forcing an address book update in Teams. Here's how:
In Microsoft Teams, click on your profile picture at the top right.
Choose "Settings" from the dropdown menu.
In the "General" section, scroll down and click on "Clear cache."
After clearing the cache, restart Microsoft Teams and see if the updated names are now visible.
Check for Teams Policy Restrictions: Ensure that there are no specific policies in place that might be preventing the display name updates in Teams. Check Teams admin center settings and policies that could be affecting user display names.
Test with a New User: To determine if the issue is specific to existing users, create a new user in Okta and check if the display name properly syncs to Teams. This will help narrow down the scope of the problem.