June 23, 2026 Stories worth reading. Perspectives worth sharing.
Microsoft Teams: Proactively Block All Identified External Bots from Meetings—Automated Controls Arrive in August 2026
Microsoft 365

Microsoft Teams: Proactively Block All Identified External Bots from Meetings—Automated Controls Arrive in August 2026

Mo Wasay June 23, 2026 5 min read
Microsoft Teams: Proactively Block All Identified External Bots from Meetings—Automated Controls Arrive in August 2026

REPORT

Microsoft Teams is introducing a new automated capability to block all recognized external bots from joining meetings, arriving in General Availability August CY2026 (Roadmap Item 566201). This feature expands on existing bot management controls by allowing admins to set a global policy that denies meeting access to any bot identified by Microsoft’s external bot classification system. This responds directly to increasing concerns over AI-driven bots infiltrating meetings for data scraping, social engineering, or unauthorized recording—risks amplified by recent advances in generative AI and cross-platform integrations.

Previously, admins had to manually review and block bots, relying on guest access and app permission settings. The new automation closes gaps where bots might slip through due to missed updates or evolving bot identity methods. The change is surfaced via:

  • Teams Admin Center: Meetings > Meeting policies > External access > Block identified bots
  • PowerShell: The Microsoft.Graph.Teams module now exposes Set-MgTeamMeetingPolicy with the BlockIdentifiedBots property.
  • API: The Microsoft Graph endpoint for meeting policies supports the new parameter.

WHAT’S NEW THIS CYCLE

  • Feature: “Block all identified external bots”—Global, automated enforcement.
  • Status: General Availability August 2026.
  • Admin Center Path: Teams Admin Center > Meetings > Meeting policies > External access.
  • PowerShell: Set-MgTeamMeetingPolicy -BlockIdentifiedBots $true (Microsoft.Graph.Teams 2.0+).
  • API: PATCH /policies/meetingPolicy with blockIdentifiedBots flag.

IMPACT

Any organization running public or partner-facing Teams meetings is affected. External bots are increasingly sophisticated, often masquerading as legitimate users or apps. Unchecked, they can:

  • Record meetings without consent
  • Extract sensitive content (chat, audio, video)
  • Trigger downstream integrations (e.g., unauthorized AI summarization)

Real-world risk: If you haven’t actively blocked bots, your meetings may be exposed to silent data harvesting. The new feature reduces manual oversight and ensures that new bot IDs (as discovered by Microsoft) are automatically denied.

EDUCATE

What is an “Identified External Bot”? Microsoft classifies bots based on authentication patterns, app registration, and behavioral analytics across Teams and the broader Microsoft 365 ecosystem. An identified external bot is any automated entity recognized as such by Microsoft, typically outside your tenant, attempting to join a Teams meeting.

Why can bots join meetings? Bots (including AI assistants, transcription tools, and integration apps) often use guest access, app tokens, or service accounts. Without explicit blocking, these entities can gain access under the umbrella of legitimate third-party collaboration. Microsoft’s new classification system flags these attempts and enables automated policy enforcement.

DETECT

To audit your current meeting policies for bot access and identify any recent external bot join attempts, use Microsoft Graph PowerShell. This script audits policies and logs bot join events:

# Requires Microsoft.Graph.Teams 2.0+ and Microsoft.Graph.Authentication
Connect-MgGraph -Scopes "TeamsMeetingPolicy.Read.All", "AuditLog.Read.All"
try {
  $policies = Get-MgTeamMeetingPolicy -All
} catch {
  Write-Error "Failed to retrieve meeting policies: $_"
  return
}
foreach ($policy in $policies) {
  Write-Output "Policy: $($policy.DisplayName)"
  Write-Output "BlockIdentifiedBots: $($policy.BlockIdentifiedBots)"
}
# Audit bot join events (last 30 days)
try {
  $events = Get-MgAuditLogTeamsAudit -Filter "ActivityDisplayName eq 'BotJoinedMeeting'" -Top 100
} catch {
  Write-Error "Failed to retrieve audit logs: $_"
  return
}
if ($events.Count -eq 0) {
  Write-Output "No bot join attempts detected in the last 30 days."
} else {
  foreach ($event in $events) {
    Write-Output "Bot: $($event.InitiatedBy.AppDisplayName), Meeting: $($event.TargetResources[0].DisplayName), Time: $($event.ActivityDateTime)"
  }
}

Note: Use -All for policy pagination. Audit logs are paged via -Top and can be further extended by looping through @odata.nextLink if required for larger tenants.

REMEDIATE SAFELY

To enable automated bot blocking across your tenant:

# Dry-run: Preview which policies would be affected
Connect-MgGraph
$policies = Get-MgTeamMeetingPolicy -All
foreach ($policy in $policies) {
  Write-Output "Policy: $($policy.DisplayName) would have BlockIdentifiedBots set to true"
}
# To enable (use -WhatIf if supported, or review $policies list and apply manually)
# Never bulk modify from a live query. Always review output first.
# Example for a single policy:
# Set-MgTeamMeetingPolicy -TeamMeetingPolicyId $policy.Id -BlockIdentifiedBots $true

Review policies, decide which should be updated, and apply changes individually. Do not auto-modify all policies from a live query. Always perform a dry-run and confirm with stakeholders before enforcement.

PORTAL EQUIVALENT

In the Teams Admin Center, navigate to Meetings > Meeting policies > External access. The new checkbox or toggle labeled “Block all identified external bots” will appear as rollout completes. Changes can be made per policy, with a summary view of affected meetings/groups.

THE UPGRADE

Compared to previous manual controls (block guest access, block specific apps), automated bot blocking delivers:

  • Productivity: Less admin time spent reviewing bot lists and event logs.
  • Security: Immediate protection from new bot types as Microsoft updates its detection system.
  • Cost: Reduces risk of accidental data exposure (potential fines/regulatory impact).

Admins can focus on strategic governance rather than chasing bot identities.

WHAT’S COMING IN THE NEXT 90 DAYS

  • Teams: Expansion of meeting join analytics and bot classification reporting (preview, due by October 2026).
  • Entra ID: Improved third-party app risk scoring integrated with Teams policies.
  • Defender for M365: In-meeting threat detection for bot activity (rolling out to E5 tenants).
  • Purview: Enhanced audit retention and export for bot join/leave events (roadmap 2026Q3).

Prepare by reviewing meeting policy assignments, updating documentation, and informing end users about new bot restrictions and their rationale.

RELATED M365 CHANGES

Admins should also note:

  • Recent changes to guest access policies in Teams (granular controls for external domains, June 2026)
  • Entra ID’s new “App Risk Insights” dashboard (preview, integrates with Teams bot detection)
  • Exchange Online’s updated notification system for external participant activity (pilot, July 2026)

These upgrades collectively strengthen the external access workflow, helping you enforce bot and app controls across the Microsoft 365 suite.

RECOMMENDATION

  • Priority 1: Audit your meeting policies for bot access now—before the new feature is live.
  • Priority 2: Plan for staged rollout—start with high-risk groups (executive, R&D, legal).
  • Priority 3: Update user guidance and app registration documentation to reflect new bot restrictions.

Takeaway: Automated bot blocking is a major upgrade for Teams security. Review, prepare, and adopt the new policy as soon as it becomes available to protect your meetings from unauthorized AI access.