MC1466296: Microsoft Teams Adds Option to Report Security Concerns During Meetings

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
56
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTeams AdminsSecurity TeamsCompliance TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a new Teams security reporting feature that will be enabled by default and requires admins to review Defender settings, validate incident response processes, and update training and documentation. Admin impact is significant due to integration with Microsoft Defender portal and Teams admin centre for investigation workflows. User impact is moderate as it introduces a new meeting option for reporting security concerns, but usage is discretionary. Urgency is moderate because rollout starts in about three weeks, so organisations should start planning and communications now.
68
🛡️ Admin Impact
38
👥 User Impact
55
Urgency
50
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams meetings will have a new option for participants to report suspicious or malicious activity, with reports available for admin review.
👥

END USERS

Users will see a ‘Report a concern’ option during meetings.
🛡️

IT ADMINS

Review Defender settings, update incident processes, and inform users about the new reporting option.
📅

ROLLOUT TIMELINE

Upcoming:
October 2026

📢 Official Microsoft Message Center Announcement


Microsoft Teams: Report security concerns in meetings
Message ID: MC1466296

[What and why]

We’re introducing a new security reporting capability in Microsoft Teams meetings that allows meeting participants to report suspicious, malicious, or potentially fraudulent behavior during or after a meeting.

This capability helps organizations identify and investigate threats such as phishing attempts, impersonation, scams, social engineering, and other suspicious activity. Submitted reports provide additional security signals that can be reviewed by administrators in Microsoft security and administration tools to support investigation and response workflows.

This message is associated with Microsoft 365 Roadmap ID 569207.

[Rollout schedule]

  • Targeted Release: Beginning in late September 2026 and expected to complete by late September 2026
  • General Availability (Worldwide): Beginning in mid-October 2026 and expected to complete by late October 2026

[Impact on your organization]

Who is affected

  • Users participating in Microsoft Teams meetings on Windows, Mac, and web

Platforms and services

  • Microsoft Teams
  • Microsoft Defender portal
  • Teams admin center

What will happen

  • Users will see a new Report a concern option in the participant tile and participant pane during Teams meetings: 

    21800 1

  • Users will be able to report suspected phishing attempts, impersonation, scams, social engineering activity, and other security concerns directly from Teams meetings: 

    21800 2

  • Users will also be able to mark a previously reported participant as Not a concern.
  • Relevant meeting metadata and limited contextual information will be collected to support security investigations and remediation activities.
  • Information associated with reported meetings will be available for administrator review and investigation.
  • Organizations with Microsoft Defender for Office 365 Plan 1, Microsoft Defender for Office 365 Plan 2, or Microsoft Defender XDR will be able to review detailed reported meeting submissions in the Microsoft Defender portal.
  • Report information will also be available in the Teams admin center under Protection reports > User-reported security submissions.
  • Administrators can investigate reported meetings and take actions according to their organization’s security processes and policies.
  • This capability will be enabled by default.

[Action required and recommendations]

Review your organization’s security investigation and incident response processes before rollout.

Recommended actions:

  • Review Microsoft Defender user reporting settings and ensure reporting workflows align with organizational requirements.
  • If your organization uses Microsoft Defender for Office 365 or Microsoft Defender XDR, verify that Teams meeting reporting is configured appropriately so detailed submissions are available to security investigators.
  • Inform users about the new Report a concern capability and when it should be used.
  • Inform users about the Not a concern option and when it should be used.
  • Update security awareness training, incident response documentation, and internal guidance as needed.
  • Verify that security administrators responsible for reviewing reports have the appropriate access to the Microsoft Defender portal or Teams admin center.

[Compliance considerations]

QuestionAnswer
Does this change provide a new way for users to communicate security concerns to their organization?Yes. Users will be able to report suspected phishing attempts, impersonation, scams, social engineering activity, and other security concerns directly from Microsoft Teams meetings.
Does this change collect new customer or user data for investigation purposes?Yes. Relevant meeting metadata and limited contextual information will be collected and made available to support security investigation and remediation activities.
Does this change alter how administrators monitor, investigate, or report on security-related activities?Yes. Administrators will be able to review and investigate reported meetings through the Microsoft Defender portal and the Teams admin center.
Does this change introduce new reporting or compliance-related records that administrators can review?Yes. User-submitted meeting security reports will be available in the Teams admin center under Protection reports > User-reported security submissions and, where licensed, in the Microsoft Defender portal.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update