Outlook: retiring "Contact Masking" (hide suggested recipients) - March 31, 2026

Posted by outremer_empire@reddit | sysadmin | View on Reddit | 19 comments

What’s changing

In Outlook, users can hide a suggested recipient while addressing an email. For example, selecting the X next to a name in the To/Cc/Bcc suggestions list. This behaviour is commonly referred to as “Contact Masking”.

We are retiring this feature for users. This does not impact admin controls for contacts.

When this will happen

Contact masking will reach end of support on March 31, 2026.

How this affects your organization

Who is affected

All Outlook users (Desktop, Web, Mobile) who previously hid suggested recipients

Why we’re making this change

This feature has been a recurring source of customer confusion and escalations, because contacts can be accidentally hidden for one user but not others.

While the impact is felt across Microsoft 365 experiences (not just Outlook). It also isn’t managed as a contact entity setting, which creates transparency and compliance challenges.

https://ibb.co/6RwjpxPJ

[-]

reserved_seating@reddit

They are removing it because people are confused? I really don’t care but holy hell.

Regular_Painter_1289@reddit

Number of people I have heard of being 'confused' by this feature in my decades of IT work:
0
Number of people negatively impacted by this change just TODAY:
2

WHY??!!

I didn’t even m own it was a thing till this post 🙂

Such-Heart1032@reddit

I hate this decision. Microsoft keeps suggesting an external contact who we occasionally work with ahead of our internal staff member because they have the same first name. I cannot prevent this. It is infuriating!

Bgexplorer@reddit

Does anyone have a solution to this? We have users sending to incorrect addresses now or personal addresses that they have sent to in the past instead of the internal email address.

Weak_Ambition_8700@reddit

I can confirm that this bollocks is implemented now...
All my deleted incorrect email addresses has returned (both external and internal). So each time I type the first letters of a person that changed their email multiple times I get 7 suggestions and the correct one is of course hidden in the middle...
And to annoy you a little bit more Outlook is still displaying a X after all addresses making it possible to hide them from the dropdown. But.. Next time you type it returns.

And hte Microsoft solution is still: "clear the suggestion cache completly..."

After contacting support I get the answer that it is a design change and no workaround will be available. So someone got confused (in swedish kränkt/offended...) . And then they remove a feature used by everyone I would say?

Solution clear suggestion list everytime you get an incorrect address in there....

I created a feedback. Please upvote.

Dont implement MC1234566 · Community

I got some answers from MS.
1: Contacts you removed will come back.
Result: Angry users will go postal when i.cant.spell at somewhoere dot com returns in suggestion list.
2: There will be no new way to remove adresses from autocomplete list.
Solution: Remove everything from your autocomplete list....
Reseult: WHY HAVE YOU REMOVED MY ADDRESS BOOK!!!

Borgquite@reddit

I wonder if this is going to make it harder to resolve email bouncing 550 errors caused by out of date autocomplete entries in the Outlook cache...

The article which is linked to to 'Learn more about the retiring feature', is also referenced as one of the solutions in this troubleshooting article:

Fix NDR error code "550 5.1.1" through "550 5.1.20" in Exchange Online

Perhaps I should not worry, it's not like Microsoft have a track record of not thinking things through when it comes to Outlook.

TheOriginal_Frostbyt@reddit

Yeah we used this feature all the time for clearing what i called a "cached" address that would get a bounce back. Usually this was a local outlook problem and this helped all the time with sorting out those issues. I am not sure how many times we have used it recently but we definitely used for previous version of Outlook.

Created a case to ask them what the h*ll they were thinking. And referred to the fact that they are using this as solution to problems in their own KB:s.
And because my question was why and how they made do two cases because they are only capable of answering one question per case. Even though the question was practically the same thing.
Our user wont be happy when all the misspelled address returns in their suggestion list... Or users that had multiple mailboxes returns.

JerikkaDawn@reddit

If I'm reading this correctly --- me deleting people out of the suggested contacts in the To: line on an email I'm writing --- is accidentally not affecting other people's suggested contacts.

I don't understand what the fuck the problem is.

BlockBannington@reddit

I don't even understand what this is referring to, to be honest.

dracotrapnet@reddit

Such a terrible idea.

We have a few dumb dumb vendors that CC: managernameuser@typodomainofours then our users reply-all which those messages bounce. The next day the same user goes to email managername and gets the typodomain suggested ahead of their actual manager's contact.

They should rework auto-suggest to only suggest contacts in the address book.

Wario_world@reddit

There are about 100 issues I can think of off the top of my head that are higher priority than this.
This shouldn't even be on a list. MS say we're confused. I'm not, anyone else?

For clients that refuse to turn off suggested recipients and have well curated suggestions lists, MS are now going to force all the contacts they've previously dismissed to reappear on March 31st.

Seriously, who the hell made this decision?!

KaleidoscopeEast2875@reddit

Ms, why!?

EngineerInTitle@reddit

Got a Microsoft link by any chance?

outremer_empire@reddit (OP)

https://admin.cloud.microsoft/?ref=MessageCenter/:/messages/MC1234566

Why?