Messaging policies in Teams control the behaviours available to users in chats and channels: whether they can send GIFs, edit or delete their own messages, use stickers, send urgent notifications, and more. Compared to meeting policies, messaging policies are less complex — but they're still worth configuring deliberately, especially for organisations in regulated industries where message editing and deletion have compliance implications.
What Messaging Policies Control
The settings in a messaging policy fall into a few categories:
Message editing and deletion. Owners can delete sent messages controls whether team owners can delete messages sent by others in channels. Users can delete sent messages controls whether the message sender can delete their own messages. Users can edit sent messages controls whether a user can go back and modify something they sent. From a compliance standpoint, if you're subject to regulations that require message immutability (certain financial services regulations, for example), you need to turn off both edit and delete for end users. Note that even with these settings off, compliance retention policies in Microsoft Purview preserve original message versions regardless of edits and deletions — but disabling editing and deletion in the policy makes it simpler to explain to regulators.
Read receipts. When enabled, users can see read receipts in private chats. This is a user experience setting more than a governance one. Some users strongly prefer having it; others find it creates unnecessary social pressure. The default is that users control their own read receipt visibility. You can remove that control via policy if you need consistency.
Chat. The master switch for whether a user can use chat at all. Turning this off is appropriate for frontline workers or kiosk scenarios where chat isn't part of the workflow. Disabling chat also removes the ability to send messages in channel conversations, so use it carefully.
Giphy, stickers, and memes. These are the fun settings. Most governance teams don't spend much time here, but certain regulated industries (financial services, healthcare) disable these for all users as part of a general policy to minimise informal communication that could be captured in compliance archives. If that's not a concern for you, the defaults are fine.
URL previews. Controls whether URLs in messages generate rich link previews (title, image, description). This is a bandwidth setting as much as anything. In low-bandwidth environments, turning off URL previews reduces data consumption. It's also occasionally relevant if you're concerned about users being able to preview content from external URLs without clicking through.
Translate messages. Allows users to translate incoming messages into their preferred language inline. This is a user experience feature; leave it on unless there's a specific reason not to.
Immersive reader. Accessibility feature for reading messages. Always leave this on.
Priority notifications. Urgent messages with repeated audio alerts until the recipient acknowledges them. Useful for critical scenarios; can be disruptive if overused. Consider enabling it for supervisors and managers, and leaving it off for frontline workers unless they have a specific use case.
Audio messages. Controls whether users can record and send voice messages in chat. Off by default in most enterprise configurations. Some organisations enable it for specific use cases (field workers, accessibility scenarios); others prefer to keep all chat communication text-based for archiving reasons.
Compliance Implications of Edit and Delete Settings
This is the area where messaging policies intersect most directly with compliance requirements.
When a user edits a message in Teams, the original version is preserved in the compliance copy (the version stored in Exchange Online mailboxes for compliance purposes, which is separate from the version displayed to users). When a user deletes a message, the compliance copy is also preserved. So even if users have edit and delete permissions, your compliance records are intact.
However, disabling edit and delete at the policy level has two practical advantages. First, it makes compliance audits simpler — there's no question about whether a user changed a message after the fact. Second, it's easier to explain to regulators and auditors: "Users cannot edit or delete messages" is a clean statement. "Users can edit messages but we preserve compliance copies in Exchange" requires more explanation.
For most organisations, the right approach is: disable edit and delete for users in regulated roles (financial advisors, healthcare professionals, insurance adjusters), and leave them enabled for standard employees where the compliance case is weaker.
External Chat: The Setting People Forget
Messaging policies also include a setting for external chat — whether users can chat with people outside your organisation using Teams (Teams Connect, or federated chat). This setting works in conjunction with the external access settings in Org-wide settings.
The external access org-wide setting controls whether external chat is technically possible at all. The messaging policy setting controls whether a specific user can initiate or receive external chats. Both need to allow it for external chat to work. A common misconfiguration: enabling external chat in messaging policies but forgetting to enable external access in Org-wide settings (or vice versa).
Structuring Your Messaging Policies
For most organisations, two or three messaging policies are sufficient:
- Global (standard): Edit and delete enabled; Giphy and stickers enabled; URL previews enabled. Appropriate for the majority of employees.
- Restricted (compliance): Edit and delete disabled; Giphy and stickers disabled; audio messages disabled. For regulated roles.
- Frontline: Chat disabled or minimal capabilities. For kiosk or shift-worker scenarios.
- Supervisors: Priority notifications and audio messages enabled; Giphy left off. Used for on-call leads who need an interrupt path without opening stickers to the whole tenant.
- Contractors: Same chat surface as employees, with URL previews and external chat turned off so a six-month contractor cannot mint link cards or open federated threads.
As with all policy types, assign via group policy assignment to Entra ID groups that mirror your HR job categories. The messaging policy for a financial advisor should be the same as for any other financial advisor in the organisation — consistency is what makes audits manageable.
A Note on Message Retention and Compliance
Messaging policies control what users can do with messages in the Teams interface. They do not control how long messages are retained or who can search for them in eDiscovery. Those are handled separately through Microsoft Purview retention policies and eDiscovery. Don't confuse the two layers of control — they're complementary, not overlapping.
What Happens When a User Sits in Two Messaging Policies
Group assignment does not blend settings. Microsoft Teams applies one messaging policy per user, chosen by the rank of the group policy assignment, the same way meeting and calling policies resolve. A claims handler who is also in an "all staff" group does not receive a mix of the restricted profile and the global profile. The higher-ranked assignment wins for every toggle in the policy, including the ones an administrator assumed were inherited from Global.
That all-or-nothing behaviour is easy to miss in a tenant of about 1,800 people, which is a common size for a regional insurer. The compliance group is ranked 1 and contains every licensed adjuster. A later project adds those same accounts to a collaboration group ranked 3 so they can join a cross-team channel. Chat behaviour does not change, because rank 1 still holds. The surprise arrives when someone removes the adjuster from the compliance group after a role change and forgets the collaboration group is still there. The user drops to rank 3, or to Global if that group is not a messaging assignment at all, and edit/delete switches back on overnight.
Check the effective policy on the user record in the Teams admin center before and after any group membership change that touches a regulated role. The PowerShell view is Get-CsEffectivePolicy or the per-user policy readout from Get-CsOnlineUser. Either one shows the messaging policy name actually in force, which is the only name worth comparing to the written standard.
Policy packages complicate the picture only when a package is assigned directly to the user on top of a group assignment. Direct assignment outranks group assignment. A package applied during onboarding "to save time" will silently beat the compliance group until the direct assignment is removed. Treat packages as a starting template for a cohort, then move that cohort to group assignment and clear the direct policy so rank stays predictable.
Propagation is not instant. A rank change can take several hours to reach a mobile client that has been backgrounded, and the desktop client may show the old toggle set until the next sign-in. If a control is being tightened because of an audit finding, do not close the finding on the strength of the admin-center screenshot alone. Spot-check a user session the next morning.
A quarterly export of effective messaging policies, joined to the HR cost-centre code, catches the adjuster who changed desks and lost the restricted profile. Keep the restricted policy's display name stable. Renaming it mid-audit forces every evidence screenshot to be recaptured. URL preview is a data-egress control as well as a bandwidth one: the preview fetch contacts the destination host from Microsoft's service, which some security teams treat as an implicit outbound request. Audio messages land in the same compliance store as text, but reviewers often skip them because the export shows a media attachment rather than a sentence. If a role is prohibited from editing text, decide explicitly whether voice notes are in or out. Frontline chat-off is brittle if the same account is also used at a shared desk with a full client. Confirm the licence and the policy together, not the policy alone. Document the rank order next to the policy matrix. A matrix without rank is not operable by the next administrator.
