Microsoft Teams Messaging Extension - Copy Button Fails with Adaptive Cards Containing More Than 5 FactSet Items

[shreyanshjha]

Dear Microsoft Support Team,
We are experiencing a critical issue with the copy functionality in Microsoft Teams messaging extensions when using Adaptive Cards with FactSet elements containing more than 5 facts.
Issue Summary
Problem: The copy button in the messaging extension search results fails silently when an Adaptive Card's FactSet contains more than 5 items. The button appears but does nothing when clicked - no error is shown to the user, and the card is not copied to the clipboard.

Environment:

• Microsoft Teams Version: [Latest Desktop/Web Client]
• Adaptive Card Version: 1.5
• Bot Framework SDK: Node.js
• Messaging Extension Type: Search-based (composeExtension/query + composeExtension/selectItem)

Reproduction Steps

1. Create a messaging extension with search functionality
2. Implement composeExtension/selectItem handler that returns an Adaptive Card
3. Include a FactSet with 6 or more facts in the card
4. Search for and select an item from the messaging extension
5. Click the copy button (clipboard icon) in the card detail view
6. Attempt to paste (Ctrl+V) in the compose box

Expected Result: Card is copied to clipboard and can be pasted
Actual Result: Nothing happens - copy fails silently

Working vs. Non-Working Examples

✅ WORKING - 5 Facts (Copy Button Works)

function buildTaskCard (taskData) {
return {
    composeExtension: {
      type: "result",
      attachmentLayout: "list",
      attachments: [{
        contentType: "application/vnd.microsoft.card.adaptive",
        content: {
          $schema: "http://adaptivecards.io/schemas/adaptive-card.json",
          type: "AdaptiveCard",
          version: "1.5",
          body: [
            {
              type: "TextBlock",
              text: `NE382-1 xxcvcxv`,
              weight: "Bolder",
              size: "Large"
            },
            {
              type: "FactSet",
              facts: [
                { title: "Project", value: "New project" },
                { title: "Assignee", value: "Unassigned" },
                { title: "Status", value: "New1" },
                { title: "Priority", value: "Medium" },
                { title: "Type", value: "task1" }
              ]
            }
          ],
          actions: [{
            type: "Action.OpenUrl",
            title: "View Task",
            url: "https://example.com/task/123"
          }]
        },
        preview: {
          contentType: "application/vnd.microsoft.card.thumbnail",
          content: {
            title: `NE382-1 xxcvcxv`,
            subtitle: "New project",
            text: "View task"
          }
        }
      }]
    }
  };

❌ NOT WORKING - More than 5 Facts (Copy Button Fails)

function buildTaskCardWithSection(taskData) {
  return {
    composeExtension: {
      type: "result",
      attachmentLayout: "list",
      attachments: [{
        contentType: "application/vnd.microsoft.card.adaptive",
        content: {
          $schema: "http://adaptivecards.io/schemas/adaptive-card.json",
          type: "AdaptiveCard",
          version: "1.5",
          body: [
            {
              type: "TextBlock",
              text: `NE382-1 xxcvcxv`,
              weight: "Bolder",
              size: "Large"
            },
            {
              type: "FactSet",
              facts: [
                { title: "Project", value: "New project" },
                { title: "Section", value: "SPRINT 2" },        // Additional fact
                { title: "Assignee", value: "Unassigned" },
                { title: "Status", value: "New1" },
                { title: "Priority", value: "Medium" },
                { title: "Type", value: "task1" }
              ]
            }
          ],
          actions: [{
            type: "Action.OpenUrl",
            title: "View Task",
            url: "https://example.com/task/123"
          }]
        },
        preview: {
          contentType: "application/vnd.microsoft.card.thumbnail",
          content: {
            title: `NE382-1 xxcvcxv`,
            subtitle: "New project / SPRINT 2",
            text: "View task"
          }
        }
      }]
    }
  };
}

Attempted Workarounds (All Failed)

1. Multiple FactSets: Split facts into two separate FactSet elements → Still fails
2. TextBlock with Markdown: Replace FactSet with formatted TextBlock → Copy works but formatting is poor after paste
3. ColumnSet Layout: Use ColumnSet with TextBlocks → Copy fails
4. Different Field Names: Changed field names thinking "Section" might be reserved → Still fails

Questions

1. Is the 5-fact limit a documented limitation or a bug?
2. If it's intentional, what is the reasoning behind this limit?
3. Is there a recommended workaround that maintains good formatting AND copy functionality?
4. Will this limitation be addressed in future releases?

Request
We kindly request that this issue be investigated and either:

• The 5-fact limit be removed or significantly increased (to at least 10-12 facts)
• Official documentation be updated to clearly state this limitation
• Alternative approaches be provided that support more than 5 facts while maintaining copy functionality

[m365-agent-toolkit-assistant]

👋 Hi @shreyanshjha,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Your issue with the copy button failing for FactSet elements in Adaptive Cards (with more than 5 items) in Teams messaging extensions matches known limitations/discussions in GitHub and Stack Overflow—though a hard 5-item copy limit is not officially documented.

Findings:

• Multiple developers report copy/paste (clipboard) issues when FactSet facts >5, with no user error shown.
• Attempts to split into multiple FactSets, use TextBlocks, or alternate layouts all produce poor results or failed copy-action.
• Microsoft engineers have confirmed markdown and formatting limitations for FactSet elements in Teams.
• Some related limits are card size/character count (~2400 chars) and single FactSet formatting quirks, but no official Fix or clear reasoning for a 5-item copy limit.

Actionable Workarounds:

• Most reliable: Use a single TextBlock to present facts (markdown for bold/labels), if copy is essential.
• For better formatting, split information across cards or reduce FactSet count to ≤5 per card.

Next Steps:

• Track these issues: GitHub discussion #1787
• Upvote/request clear documentation/feature fix via Teams Feedback portal.

Summary:
The 5-fact copy limit is likely an undocumented bug. Use TextBlock as a workaround; monitor official channels for future updates.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[microsoft-github-policy-service]

Hi @@shreyanshjha! We will investigate and if we require further information we will reach out to you. Please use this link to escalate if you don't get replies in two working days.

Best regards, Teams Platform

[sayali-MSFT]

Hello @shreyanshjha ,Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[sayali-MSFT]

Hello @shreyanshjha ,We have already raised an ICM for this issue, and our engineering team is actively working on it. We will keep you updated as soon as we have any further information.

[shreyanshjha]

Hello @shreyanshjha ,We have already raised an ICM for this issue, and our engineering team is actively working on it. We will keep you updated as soon as we have any further information.

Thanks for the update. I appreciate you escalating this to the engineering team.
Please keep me posted if any additional details or testing are needed from my side.

[shreyanshjha]

Hi @sayali-MSFT,

Just checking in to see if there are any updates from the engineering team regarding this issue.

Our Teams app relies on Adaptive Cards that may contain more than 12–15 fields. We are concerned that this copy limitation could potentially be raised during Microsoft’s validation process when we submit the app.

We explored alternative layouts, but both FactSet and ColumnSet appear to have the same limitation, and using TextBlock breaks our design completely after copy/paste — so we don’t currently have a workable workaround that preserves formatting.

If a fix timeline isn’t available yet, could you please advise whether this limitation might impact Teams app validation, or if there is any recommended workaround that maintains the intended design?

Thank you again for your support — happy to provide more details or testing if needed.

[sayali-MSFT]

Hello @shreyanshjha ,
Thank you for your inquiry regarding the status of the ICM. We are currently checking in with the engineering team for any updates.

We appreciate your patience and will inform you as soon as we have more information. Thank you!

However, if you have any business-critical issue which need immediate attention, please raise a support request here:
https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide&tabs=online

[shreyanshjha]

Hi @sayali-MSFT,
Thank you for the update.
I appreciate you checking with the engineering team and will wait for further information from their side.