Teams Communicator: a genuine setup job, and a reason to review what you already pay for

Communicator is a new standalone Teams app, not a feature bolted onto an existing one, built specifically for organisation-wide announcements: safety alerts, compliance notifications, training updates, the kind of message that needs to be tracked, not just sent.

If that sounds like something you already handle through a separate tool, this is worth a proper look before renewing it.

Public Preview and General Availability both begin worldwide in mid-August 2026, an unusually overlapping timeline, with Public Preview expected to complete by mid-January 2027 and General Availability by late January 2027. It applies to Microsoft Teams, affecting admins, designated communicators, and the users and channels receiving communications.

Once set up, designated communicators can create and publish targeted announcements to individuals or Teams channels, deliver operational communications directly within Teams, attach required actions and acknowledgment workflows to a message, and track delivery and acknowledgment status through built-in reporting.

Recipients see announcements and operational communications directly within Teams itself.

This is the rare update in this set that genuinely needs setup work before launch, and it’s worth two different kinds of attention:

• There’s real configuration required, not just a heads-up. Admins need to install the Communicator app for designated senders, install the Communicator Bot for recipients, and review Teams app permission policies, app setup policies and availability settings to make sure the right people have the right access. None of this happens automatically.
• The Public Preview and General Availability windows overlap almost entirely, both starting in mid-August 2026. That’s unusual, worth double-checking against the live roadmap closer to rollout rather than assuming it’s a typo, since it affects how you’d sequence a rollout plan.
• This is a genuine tool-consolidation moment. If your organisation already pays for a separate internal communications or mass-notification platform for safety alerts, compliance notices or training updates, Communicator’s acknowledgement tracking and reporting may cover that need natively within Teams. Worth evaluating before assuming the existing tool is still necessary.

• Microsoft Teams administrators, who have genuine setup work to do here
• Users designated to create and send organisational communications
• All users and Teams channels receiving organisational or operational communications
• Anyone currently managing a separate internal comms or mass-notification tool, worth a comparison before this rolls out further

This is one of the few updates in this set where doing nothing means the feature simply won’t work when people expect it to:

1. Install the Communicator app for designated communicators, and the Communicator Bot for recipients, ahead of Public Preview reaching your organisation.
2. Review Teams app permission policies, app setup policies and availability settings now, to confirm the right people get the right Communicator experience from the start.
3. Identify who in your organisation should be a designated communicator, this is a role decision as much as a technical one, particularly for compliance and safety-related messaging.
4. Compare this against any existing internal comms or mass-notification tool your organisation currently pays for, before assuming it’s still needed once Communicator is available.
5. Watch for Microsoft’s additional documentation, promised ahead of General Availability, since Public Preview guidance is likely incomplete at this stage.

This update is based on Microsoft 365 Message Centre update MC1459143, published 21 August 2026. Rollout dates are provided by Microsoft and may change.