Calendar meetings showing legacyExchangeDN instead of DisplayName

Last Updated: July 2, 2021

ISSUE

Calendar meetings are displaying attendee names as legacyExchangeDN instead of DisplayName.  When you respond to one of these meeting invites, this issue migrates into your cache in Outlook, causing future meetings to be impacted as well. 

Note: This issue is not impacting the meeting organizer. 

STATUS: FIXED

The Outlook team has released a fix in build 15.20.4305.000 that will mitigate the initial root cause of one-offs from appearing in the autocomplete cache. With this fix, newly created meetings will no longer be affected. 

You can check if the fix has reached your tenant by having an affected attendee accept/tentative/decline the meeting, and they can choose to select "do not respond" as long as it is not in Outlook for Windows. If responding from Outlook for Windows, a response needs to be sent. The meeting should be back to normal once the tracking changes are replicated back to the attendee.

Note: All meetings need to be a future date. As an estimate, if the meeting has less than 500 attendees, users should see this fixed within 10 minutes of the response sent. The organizer can also send a meeting update to resolve the issue.

After you receive the fix, If you have been impacted by this issue you will need to manually clean your autocomplete cache list. Organizers can address this issue for future meetings by modifying meeting invites and sending the update to all users, or attendees can respond to any meeting set for the future to also resolve this issue.