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 14:43 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Forward messages with app cards

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

Rollout

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 13 Jun 2025 late May 2025 → late June 2025
  • Seen 9 May 2025 late April 2025 → late May 2025
  • Seen 4 Apr 2025 late March 2025 → late April 2025
  • Seen 26 Mar 2025 early March 2025 → late March 2025
  • Seen 11 Feb 2025 early February 2025
  • Seen 16 Jan 2025 early January 2025, mid-January 2025, late January 2025 → mid-February 2025, late February 2025, early March 2025

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 13, 2025: We have updated the timeline below. Thank you for your patience. We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card.  Please note: Forwarding of bot cards is excluded from this release.  This message is associated with Microsoft 365 Roadmap ID 469506. When this will happen: Targeted Release: We will begin rolling out mid-February 2025 (previously early February) and expect to complete by late February 2025 (previously mid-February). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by late June 2025 (previously late May). How this will affect your organization: Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained app cards. With this improvement, this restriction does not exist.  What you need to do to prepare: Users must have the latest Microsoft Teams build to receive these updates. You may want to notify your users about this change and update any relevant documentation as appropriate.

What changed

Between archive captures, newest first
  1. Updated May 8,June 13, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing the ability … late February 2025 (previously late January) and expect to complete by late MayJune 2025 (previously late April).May). How this will affect your organization: Users will now have less restrictions …

  2. Updated April 4,May 8, 2025: We have updated the rollout timeline below. Thank you for your … late February 2025 (previously late January) and expect to complete by late AprilMay 2025 (previously late March).April). How this will affect your organization: Users will now have less restrictions …

  3. Updated March 26,April 4, 2025: We have updated the rollout timeline below. Thank you for your … late February 2025 (previously late January) and expect to complete by late MarchApril 2025 (previously earlylate March). How this will affect your organization: Users will now have less …

  4. Updated February 11,March 26, 2025: We have updated the rollout timeline below. Thank you for your … out late February 2025 (previously late January) and expect to complete by earlylate March 2025 (previously early February).March). How this will affect your organization: Users will now have less restrictions …

  5. Updated January 17,February 11, 2025: We have updated the rollout timeline below. Thank you for your … 469506. When this will happen: Targeted Release: We will begin rolling out early February mid-February 2025 (previously early January)February) and expect to complete by mid-Februarylate February 2025 (previously mid-January).mid-February). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out …

  6. Updated January 16,17, 2025: We have updated the rollout timeline below. Thank you for your … is associated with Microsoft 365 Roadmap ID 469506. When this will happen: Public Preview:Targeted Release: We will begin rolling out early February 2025 (previously early January) and …

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

    Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing the ability to forward app cards. With the addition of … When this will happen: Public Preview: We will begin rolling out early JanuaryFebruary 2025 (previously early January) and expect to complete by mid-January 2025.mid-February 2025 (previously mid-January). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late JanuaryFebruary 2025 (previously late January) and expect to complete by early February 2025.March 2025 (previously early February). How this will affect your organization: Users will now have less restrictions …

  7. · 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.

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.
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 14:43 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current