How to Configure Channel Moderation, Guest Posting Permissions, and Information Barriers in Microsoft Teams

As enterprise organisations expand their Microsoft Teams footprint across thousands of internal staff, external vendors, and contract partners, unstructured collaboration introduces substantial operational and regulatory liabilities. Without rigorous governance, high-visibility announcement channels become flooded with conversational chatter, external guest accounts post unapproved third-party links, and cross-department communications risk violating financial compliance mandates (such as FINRA and SEC conflict-of-interest regulations).

Microsoft 365 addresses these governance challenges through a layered compliance framework consisting of Channel Moderation, granular Guest Posting Permissions, and Information Barriers (IB). When properly configured by tenant administrators and team owners, these features restrict channel message initiation to designated moderators, control guest capabilities, and enforce cryptographic communication firewalls between conflicting enterprise segments.

Architectural Overview: Microsoft Teams Governance and Isolation Layers

Microsoft Teams enforces compliance boundaries across three distinct operational layers:

Governance Layer	Administrative Mechanism	Compliance & Operational Impact
Channel Moderation	Team Owner / Channel Settings	Converts channels into controlled broadcast streams; only moderators can start new conversation threads.
Guest Access Policies	Teams Admin Centre (CsTeamsMessagingPolicy)	Restricts external Azure AD B2B guests from editing messages, deleting posts, or sharing Giphy media.
Information Barriers (IB)	Purview Compliance Substrate & Graph API	Blocks 1:1 chats, calling, and team discoverability between segregated corporate user groups (e.g. Traders vs. Analysts).
App & Bot Submission Filters	Channel Bot Governance	Prevents automated webhooks and third-party bots from submitting unvetted payloads into critical channels.

Configuring Channel Moderation in Standard Channels

Channel Moderation converts open collaboration channels (such as Company Announcements or Incident Response Alerts) into broadcast feeds where only authorized moderators can publish top-level posts.

Step 1: Open Channel Management

1. In Microsoft Teams, locate the team and hover over the target standard channel.
2. Click the three dots (More options) and select Manage channel.
3. In the settings tab, locate the Channel moderation section.

Step 2: Enable Moderation and Designate Moderators

1. Toggle the Channel moderation switch from Off to On.
2. Under Who are the moderators?, select Team owners or click Manage to add individual members (e.g. Corporate Communications Leads).
3. Configure member permissions beneath:
   • Allow members to reply to channel messages: Keep checked if attendees can ask questions beneath existing posts, or uncheck for pure one-way broadcasts.
   • Allow bots to submit channel messages: Toggle off to block rogue webhook noise.
   • Allow connectors to submit channel messages: Uncheck unless verified RSS/webhook feeds are mandatory.

Non-moderator members and guests will see the bottom message input bar replaced with the text: “Only channel moderators can post in this channel.”

Restricting Guest Posting Permissions via Teams PowerShell

While channel moderation applies per-channel, tenant administrators can restrict guest messaging capabilities globally using the Microsoft Teams PowerShell module.

Step 1: Connect to Teams PowerShell

# Authenticate to Microsoft Teams tenant
Import-Module MicrosoftTeams
Connect-MicrosoftTeams -TenantId "your-tenant-uuid"

Step 2: Inspect and Enforce Guest Messaging Policies

Prevent external guest participants from modifying posts or posting unvetted media across corporate channels:

# Restrict guest messaging capabilities in the Global policy
Set-CsTeamsMessagingPolicy -Identity Global `
    -AllowUserEditMessage $true `
    -AllowUserDeleteMessage $true `
    -AllowGiphy $true `
    -GiphyRatingType "Strict"

# Create a restricted policy specifically for external guests
New-CsTeamsMessagingPolicy -Identity "Restricted-GuestPolicy" `
    -AllowUserEditMessage $false `
    -AllowUserDeleteMessage $false `
    -AllowGiphy $false `
    -AllowMemes $false `
    -AllowStickers $false

# Assign policy to guest accounts
Grant-CsTeamsMessagingPolicy -Identity "guest.contractor_external.com#EXT#@enterprise.onmicrosoft.com" `
    -PolicyName "Restricted-GuestPolicy"

Deploying Information Barriers for Regulated Segments

Information Barriers (IB) prevent conflicts of interest by blocking communication between segregated divisions (e.g. Investment Banking and Equity Research). When IB is active, users in conflicting segments cannot search for each other, join the same teams, or initiate private chats.

Step 1: Connect to the Compliance PowerShell Module

# Connect to Security & Compliance PowerShell
Import-Module ExchangeOnlineManagement
Connect-IPPSSession -UserPrincipalName "[email protected]"

Step 2: Create User Segments Based on Azure AD Attributes

# Define Segment 1: Investment Bankers
New-OrganizationSegment -Name "IB-InvestmentBanking" `
    -UserGroupFilter "Department -eq 'Investment Banking'"

# Define Segment 2: Financial Research Analysts
New-OrganizationSegment -Name "IB-ResearchAnalysts" `
    -UserGroupFilter "Department -eq 'Research Analysis'"

Step 3: Enforce the Information Barrier Policy

# Create block policy preventing communication between the two segments
New-InformationBarrierPolicy -Name "Block-Banking-Research" `
    -AssignedSegment "IB-InvestmentBanking" `
    -SegmentsBlocked "IB-ResearchAnalysts" `
    -State Active

# Trigger tenant policy application background service
Start-InformationBarrierPoliciesApplication

Teams enforces the barrier within hours: if an Investment Banker attempts to add a Research Analyst to a channel or call, Teams rejects the invitation with an administrative block banner.

Troubleshooting Teams Moderation and Information Barrier Conflicts

Consult this diagnostic reference table to debug permission errors and barrier enforcement anomalies:

Issue	Underlying Root Cause	Remediation Procedure
“Channel moderation” toggle is missing in channel settings.	The channel is a Private Channel or Shared Channel. Moderation is only supported on Standard channels.	Channel moderation is an architectural feature of Standard channels. For Private/Shared channels, manage access by pruning channel membership lists.
Users cannot add a colleague to a team: “We couldn’t add member due to policy”.	An active Information Barrier (IB) policy blocks membership between the user segment and the team’s existing members.	Verify segment assignments via Get-InformationBarrierPolicy. If membership is legitimate, update the user’s Department attribute in Azure AD / Entra ID.
Guest users are able to delete posts despite policy restrictions.	Policy assignment has not fully propagated across Microsoft Teams client cache tokens.	Teams policy replication takes up to 24 hours. Instruct the guest user to sign out and clear local Teams cache in %APPDATA%\Microsoft\Teams.
Automated webhook notifications fail with HTTP 403 Forbidden.	Channel moderation was enabled with “Allow bots to submit channel messages” toggled off.	Open channel management, navigate to Channel moderation, and check the box labeled Allow bots to submit channel messages.

Configuring channel moderation, strict guest posting rules, and Information Barriers establishes a disciplined communication environment in Microsoft Teams, protecting enterprise intellectual property and maintaining strict regulatory compliance.