Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Microsoft account team messge in correspondents

deb36

Hi Today, several emails that I have received, which I think were sent from an Outlook account, have, instead of what I would expect to see as the sender's address under correspondents, have Microsoft account team <account-security-noreply@accountprotection.microsoft.com> When I click on the email, I can see the genuine sender's address This has only happened today At least one of the emails that I received came from someone that I know uses Outlook Any ideas? Thanks

Hi Today, several emails that I have received, which I think were sent from an Outlook account, have, instead of what I would expect to see as the sender's address under correspondents, have Microsoft account team <account-security-noreply@accountprotection.microsoft.com> When I click on the email, I can see the genuine sender's address This has only happened today At least one of the emails that I received came from someone that I know uses Outlook Any ideas? Thanks

All Replies (2)

fix your address book is my first reaction as it's contents is used to populate the sender in the message lists. I am guessing that address is in your collected address book

failing that right click the folder, select properties and then the repair button to force a reindex of the mail in the folder.

Hi Thanks. When you say "fix my address book" what do you mean? At least one of the senders is not in my address book, although is someone that regularly emails me. I don't have my address book set to collect email addresses.

I had some different issues earlier in the week, which prompted me to delete msf files & thus force reindexing of my folders - which didn't solve that problem. A reboot did

This issue is new. Happened on Tuesday for the first time & I haven't seen it since. Perhaps it was a one-off. I think I've subsequently rebooted my PC - but not entirely sure

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.