Published Dec 6, 2024
Microsoft Teams now allows forwarding loop components. Rollout begins in early January 2025, with full availability by early April 2025. This update removes previous restrictions on forwarding messages with loop components and will occur automatically without admin action needed. Users can forward by selecting 'more actions' on a message. For more details, visit Microsoft 365 Roadmap ID 469507 or Microsoft Support.
Updated January 7, 2025: We have updated the rollout timeline below. Thank you for your patience.
There is now the ability to forward loop components in Microsoft Teams. With the addition of loop component forwarding, users have a new way to share loop components across chats and channels. To forward a message containing a loop component, simply navigate to the more actions menu of any message containing a loop component and select forward. From there, the forward this message dialog will populate, which provides users with a preview of the message being forwarded, including the loop component. In this view, users will be able to give permissions to recipients of the loop component to ensure all recipients have access to the content.
This message is associated with Microsoft 365 Roadmap ID 469507.
When this will happen:
Targeted Release: We will begin rolling out in early January 2025 and expect to complete by mid-January 2025.
General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late January 2025 and expect to complete by early April 2025 (previously early February).
How this will affect your organization:
Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained a loop component. With this improvement, no such restriction exists.
This update is available by default.
For additional information, see Forward a message in a Teams chat - Microsoft Support.
What you need to do to prepare:
This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.