MC1532241: Microsoft Defender XDR Adds Advanced Hunting for Suspicious Teams Calls and Meetings

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
50
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Security TeamsCompliance TeamsMicrosoft 365 AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a new capability in Microsoft Defender XDR enabling investigation of Microsoft Teams calls and meetings through the CallActivityEvents table. It primarily impacts security teams that manage Defender for Office 365 Plan 2 and integrate with APIs or Microsoft Sentinel. Admins should review schema changes, permissions and ingestion pipelines. User impact is indirect since the feature enhances backend visibility rather than altering Teams behaviour.
62
🛡️ Admin Impact
18
👥 User Impact
55
⚡ Urgency
48
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Security teams can now use advanced hunting in Defender XDR to investigate Microsoft Teams call and meeting activity using the new CallActivityEvents table.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Share this with security teams and review permissions, schema, and API configurations before rollout.
📅

ROLLOUT TIMELINE

Upcoming:
Early November 2026

📢 Official Microsoft Message Center Announcement


Microsoft Defender XDR: Investigate suspicious Microsoft Teams calls and meetings with advanced hunting
Message ID: MC1532241

[What and why]

When investigating a suspicious Microsoft Teams call or meeting, your security team needs to understand what happened, who initiated the activity, and the organization associated with the initiator.

The CallActivityEvents table in Microsoft Defender XDR advanced hunting provides visibility into activities performed during Teams calls and meetings in your organization. Security teams can use this information to investigate suspicious activity, review related messages, and correlate findings with other security signals.

This capability is available to organizations with Microsoft Defender for Office 365 Plan 2. 

[Rollout schedule]

  • General Availability (Worldwide): Beginning in early November 2026 and expected to complete by mid-November 2026

[Impact on your organization]

Who is affected

  • Security operations and threat hunting teams in organizations with Microsoft Defender for Office 365 Plan 2

Platforms and services

  • Microsoft Defender XDR advanced hunting
  • Microsoft Teams

What will happen

Your security team can use the CallActivityEvents table on the Advanced hunting page in the Microsoft Defender portal to:

  • Understand what happened by reviewing activities performed during Teams calls and meetings, including whether an activity succeeded or failed and whether it was performed on the initiator or another participant.
  • Investigate who initiated an activity by reviewing the initiator’s identity, account and membership types, organization, tenant region, and Teams client platform.
  • Identify the organizer by reviewing the identity and tenant of the user who organized the call or meeting.
  • Review related messages by joining CallActivityEvents with the MessageEvents table using ThreadId to examine recorded messages exchanged in the associated call or meeting chat.
  • Broaden investigations by correlating call and meeting activity with other available advanced hunting data.
  • Call and meeting activity data will also be available through the event streaming API and Microsoft Sentinel API, allowing security teams to incorporate the data into existing security monitoring and investigation workflows.

[Action required and recommendations]

Share this update with your security operations and threat hunting teams.

We recommend that you:

  • Review the CallActivityEvents schema and identify how call and meeting activity can support your existing Teams investigation workflows.
  • Ensure analysts who will use this capability have appropriate advanced hunting access. Microsoft documents that permissions are required to run advanced hunting queries.
  • If your organization uses the event streaming API or Microsoft Sentinel API, review your data ingestion configuration and plan to incorporate call and meeting activity into your existing workflows.

Learn more

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update