Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 15:44 UTC Customize Public modeDiscuss ChangeIntel on Discord

Interact with your favorite apps on Teams using Slash ( / ) Commands

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
495002

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 25 Jun 2026 late July 2026 → early August 2026, late August 2026
  • Seen 27 May 2026 late May 2026, late June 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated June 25, 2026: We have updated the timeline. Thank you for your patience.  Introduction Microsoft Teams is introducing slash (/) commands for apps in the compose box across chats and channels. This change provides a standardized way for users to invoke app functionality directly from the compose box and receive responses inline. This message is associated with Microsoft 365 Roadmap ID 495002. When this will happen: Targeted Release (Worldwide): We will begin rolling out in early July 2026 (previously late May) and expect to complete by early July 2026 (previously late June). General Availability (Worldwide): We will begin rolling out in early August 2026 (previously early July) and expect to complete by late August 2026 (previously late July). How this affects your organization: Who is affected: All Microsoft Teams users App developers publishing apps in the Teams Store What will happen:Users can type “/” in the compose box to discover and invoke supported app commands. Apps can return responses as Targeted Messages (visible only to the user who invoked the command). The feature is available by default when apps support slash commands No changes to existing admin policies or permissions. Apps will only appear in slash commands if their developers update the app manifest to define supported commands. What you can do to prepare: No action is required. Review internal app inventory and confirm continued availability of apps that adopt slash commands. Update internal guidance if you provide documentation on Teams app usage. Compliance considerations: Introduces a new targeted messaging pattern (user-only visibility) within chats and channels.

What changed

Between archive captures, newest first
  1. Updated May 27,June 25, 2026: We have updated the timeline. Thank you for your patience.  Introduction … late June). General Availability (Worldwide): We will begin rolling out in early JulyAugust 2026 (previously early July) and expect to complete by late July 2026.August 2026 (previously late July). How this affects your organization: Who is affected: All Microsoft Teams users …

    • Tags New feature, User impact → Updated message, New feature, User impact

    Updated May 27, 2026: We have updated the timeline. Thank you for your patience.  Introduction Microsoft Teams is introducing slash (/) commands for apps in the … this will happen: Targeted Release (Worldwide): We will begin rolling out in late Mayearly July 2026 (previously late May) and expect to complete by early July 2026 (previously late June 2026.June). General Availability (Worldwide): We will begin rolling out in early July 2026 …

  2. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 15:44 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current