MAC Outlook can't change display name imap in new version

Anonymous
2021-05-25T19:38:24+00:00

When I switch to the new version of Outlook on my Imac, my name from my imap account will be changed to my e-mail address.

How can i resolve this?

Thanks!

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

111 answers

Sort by: Oldest
  1. Anonymous
    2021-10-27T10:42:09+00:00

    Awesome! you are a life-saver! This did solve the problem.

    Regards

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-10-27T10:50:47+00:00

    I finally came up with a solution to this by removing the IMAP account, and adding it back by turning off the "Sync with Microsoft Cloud" switch, above the various mail protocols, before I clicked IMAP. In that state, I had difficulty getting it to accept the account (I was connecting to a hosted Exchange server via IMAP, since New Outlook doesn't yet support non-365 Exchange), but was finally able to get it to go by choosing "Use SSL" for incoming server and "StartTLS" for the outgoing server. Once the IMAP account was added without Microsoft Sync, I was able to go to Tools > Accounts, and set the full name.

    (Of course, switching back to non-New Outlook works too.)

    It's working. Thanks!!

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-11-03T19:05:42+00:00

    Thank you!! You're better than MS engineers !

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-12-28T09:28:41+00:00

    Thanks for the solution. It is working the way you told. :)

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-12-29T23:44:37+00:00

    It's really ridiculous we have to go to these lengths to fix this issue. I hope Microsoft is listening.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments