Home › Knowledgebase › KB-492

How to recognise and safely handle a suspicious email or impersonation attempt on Microsoft Teams or Teams chat

Summary

This guide helps you troubleshoot and resolve: How to recognise and safely handle a suspicious email or impersonation attempt on Microsoft Teams or Teams chat. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Cyber criminals increasingly use Microsoft Teams and Teams chat to impersonate colleagues, IT staff, or external organisations. These messages often arrive as a direct chat from someone you do not know, a sudden "external tenant" warning, or a request to click a link, sign in, or share a code. Because Teams is trusted as an internal communication tool, these impersonation attempts can be particularly convincing. This guide explains how to spot a suspicious Teams message, what to do before you click anything, and how to report the incident to 220 Internet Services so we can investigate and protect your environment.

Common signs of a suspicious Teams message

If a message asks you to read out an MFA code, approve a sign-in prompt, install software, or hand over remote access, treat it as a scam. No legitimate technician from 220 Internet Services will ever ask for these.

Quick Fix Steps

  1. Do not click any links, open any attachments, or reply to the message.
  2. Do not approve any MFA prompts or share verification codes.
  3. Use the Teams Report option to flag the message to Microsoft and your organisation.
  4. Take a screenshot of the chat, including the sender's email address and any external tenant warning.
  5. Open a support ticket with 220 Internet Services so we can review and contain any risk.

Detailed Instructions

Step 1: Stop and assess the message

Before you do anything, read the message carefully and look for the red flags listed above. Pay particular attention to:

If anything feels rushed, unusual, or too good to be true, assume it is suspicious and proceed without clicking.

Step 2: Verify the sender through a separate channel

If the message appears to come from a colleague, manager, or known organisation, confirm it through a different channel before acting. For example:

Never use the contact details provided inside the suspicious message itself.

Step 3: Report the message in Microsoft Teams

Microsoft Teams includes a built-in reporting option that notifies your security team and Microsoft.

  1. Open the suspicious chat in Teams.
  2. Hover over the message or click the More actions (...) menu in the top-right corner of the chat.
  3. Select Report this message (in some tenants this appears as Security then Report).
  4. Choose the most appropriate category, such as Phishing or Impersonation.
  5. Click Report to submit. The message will be sent to your organisation's security team for review.
If your organisation has the Microsoft Defender for Office 365 Teams protection feature enabled, reported messages are also analysed by Microsoft automatically.

Step 4: Capture evidence before deleting

Before you block or delete the sender, take a screenshot of:

This evidence is essential if 220 Internet Services needs to investigate, block the sender at the tenant level, or report the incident to authorities.

Step 5: Block the sender and leave the chat

  1. In the chat, click the sender's name or profile picture at the top of the window.
  2. Select Block, then confirm by clicking Block again.
  3. Optionally, click Leave to remove yourself from the chat if it is a group or external conversation.

Blocking prevents further direct messages from that account, although the user may still appear in shared channels or meetings.

Step 6: Secure your account

If you have already clicked a link, entered credentials, or approved an MFA prompt, act immediately.

  1. Change your Microsoft 365 password from a device you trust by visiting account.microsoft.com, selecting Security, then Change password.
  2. Review and remove any unfamiliar sign-in sessions by going to account.microsoft.com then Security then Sign-in activity.
  3. Remove any suspicious App registrations or Multi-factor authentication methods from your account.
  4. Sign out of all sessions by selecting Sign out everywhere.
  5. Run a full antivirus scan on the device you used.

Step 7: Report the incident to 220 Internet Services

Once you have secured your account and captured evidence, lodge a ticket so our security team can investigate and take protective action across your tenant.

  1. Go to the 220 support portal at app.220.com.au.
  2. Click Open a Ticket and choose the Security category.
  3. Include the screenshots, the sender's email address, the time of the message, and a summary of any actions you took (for example, "I clicked the link but did not enter my password").
  4. Submit the ticket and watch for a response from our team.

Troubleshooting

I cannot find the "Report this message" option

The option may be disabled by your organisation's Teams policy, or it may appear under a slightly different menu. Try the following:

The message came from inside my organisation but still looks suspicious

Internal accounts can also be compromised. Treat the message with the same caution and verify the request through a separate channel such as a phone call. If you cannot confirm the request, report it to our security team.

I approved an MFA prompt by mistake

If you accidentally approved an MFA prompt, your account may already be at risk. Take these steps immediately:

  1. Do not approve any further MFA prompts that you did not initiate.
  2. Change your Microsoft 365 password immediately from a trusted device via account.microsoft.com.
  3. Go to account.microsoft.com, select Security, then Advanced security options, and review your sign-in activity for unfamiliar locations or devices.
  4. Remove any unfamiliar MFA methods or authentication apps from your security settings.
  5. Select Sign out everywhere to terminate all active sessions.
  6. Run a full antivirus scan on the device you used.
  7. Open a ticket with 220 Internet Services via Open a Ticket so we can check for unauthorised access and reset MFA if required.

I clicked a link or entered my credentials

If you clicked a suspicious link or entered your username and password into a page reached from a Teams message, treat your account as compromised.

  1. Change your Microsoft 365 password immediately from a device you trust via account.microsoft.com.
  2. Review Sign-in activity under Security at account.microsoft.com and remove any sessions you do not recognise.
  3. Check for unexpected App registrations or added Multi-factor authentication methods and remove anything suspicious.
  4. Sign out of all sessions using Sign out everywhere.
  5. Capture screenshots of the message and the page you were taken to, then open a ticket with 220 Internet Services via Open a Ticket.

I am receiving repeated messages from a blocked sender

Blocking a sender in Teams stops direct messages from that account, but they may still reach you through shared channels, group chats, or a different account.

  1. Confirm you clicked Block on the sender's profile and not just Leave the chat.
  2. If the messages continue from a different account, block that account as well.
  3. Do not engage with the sender or reply to their messages.
  4. Take screenshots of the new messages and report them to 220 Internet Services via Open a Ticket so we can investigate tenant-level blocking options.

My colleague says they sent me a message I did not receive

Impersonation attempts often use a display name identical to a real colleague but a different email address.

  1. Hover over the sender's name in Teams to reveal the full email address.
  2. Compare the email address to your colleague's known address in your organisation's address book.
  3. If the addresses do not match, do not reply. Treat the message as an impersonation attempt.
  4. Report the message using the Teams Report this message option and open a ticket with 220 Internet Services via Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket