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 30 Apr 2026late May 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 April 30, 2026: We have updated the timeline. Thank you for your patience. Introduction We’re introducing a new slash command, /createworkflow, in the Microsoft Teams message compose box. A workflow is an automated process that handles repetitive tasks for users, such as sending notifications, creating tasks, or starting approvals when something happens in Teams. With this update, users can type /createworkflow while composing a message to quickly begin creating an automation, instead of navigating through menus. This change is designed to make workflow creation faster, easier to discover, and more accessible directly from chats and channels. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It is associated with Microsoft 365 Roadmap ID 558544. When this will happen: Targeted Release (Worldwide): We will begin rollout in late April 2026 and expect to complete by late April 2026. General Availability (Worldwide): We will begin rollout in mid-May 2026 (previously late April) and expect to complete by complete by late May 2026 (previously mid-May). How this affects your organization: Who is affected: All Microsoft Teams users. What will happen: Users can create workflows directly from the compose box using the /createworkflow slash command. Screenshot: Example of the /createworkflow slash command appearing in the Teams message compose box The feature is enabled by default. No existing admin policies are changed. Workflow creation is faster with fewer clicks. If the Workflows app is blocked for users, they will see the Create Workflow slash command, however they will not be able to use it and will see the following dialogue: What you can do to prepare: No action is required. Optionally inform users about the new slash command. Learn more: Use commands in Microsoft Teams | Microsoft Support (will be updated before rollout) Compliance considerations: Question Explanation Does the change allow a user to enable and disable the feature themselves? The /createworkflow slash command provides users with a new, self-initiated entry point to create workflows directly from the Teams compose box. The feature is enabled by default, and usage is initiated by end users without admin action.
Updated MarchApril 30, 2026: We have updated the content.timeline. Thank you for your patience. Introduction We’re introducing a new slash command, … by late April 2026. General Availability (Worldwide): We will begin rollout in late April 2026 mid-May 2026 (previously late April) and expect to complete by complete by mid-May 2026.late May 2026 (previously mid-May). How this affects your organization: Who is affected: All Microsoft Teams users. …
TagsNew feature, User impact → Updated message, New feature, User impact
Updated March 30, 2026: We have updated the content. Thank you for your patience. Introduction We’re introducing a new slash command, /createworkflow, in the Microsoft Teams … existing admin policies are changed. Workflow creation is faster with fewer clicks. If the Workflows app is blocked for users, they will see the Create Workflow slash command, however they will not be able to use it and will see the following dialogue: What you can do to prepare: No action is required. Optionally inform …
· 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.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
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.