MS Teams ignores Table.minWidth, so wide Adaptive Card tables can't scroll horizontally

Vignesh Pethuraj 0 Reputation points
2026-10-30T17:30:59.56+00:00

Problem

In the Teams desktop client, an Adaptive Card Table with minWidth set does not get a horizontal scrollbar when the card is narrower than minWidth. The card renders the same as it does without minWidth: every column is squeezed into the available width and the text wraps heavily.

Expected

The Adaptive Cards schema describes Table.minWidth as: "A scrollbar will be displayed if the available width is less than the specified minimum width."

Repro

  1. Post the card below to a Teams chat, and post the same card without minWidth.
  2. In Teams desktop, both render identically and there is no scrollbar.
  3. In the Adaptive Cards Designer, the minWidth version scrolls horizontally as documented.
{
  "type": "AdaptiveCard",
  "version": "1.5",
  "body": [
    {
      "type": "Table",
      "minWidth": "1200px",
      "firstRowAsHeaders": true,
      "columns": [
        { "width": 1 },
        { "width": 1 },
        { "width": 1 },
        { "width": 1 },
        { "width": 1 },
        { "width": 1 },
        { "width": 1 },
        { "width": 1 }
      ],
      "rows": [
        {
          "type": "TableRow",
          "cells": [
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 1", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 2", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 3", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 4", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 5", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 6", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 7", "wrap": true, "weight": "Bolder" } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Column 8", "wrap": true, "weight": "Bolder" } ] }
          ]
        },
        {
          "type": "TableRow",
          "cells": [
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 1", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 2", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 3", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 4", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 5", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 6", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 7", "wrap": true } ] },
            { "type": "TableCell", "items": [ { "type": "TextBlock", "text": "Sample value 8", "wrap": true } ] }
          ]
        }
      ]
    }
  ]
}

What we tried

  • Delivery: a Power Automate Workflows webhook post (bot message) and a card returned by a message-extension command. Both gave the same result.
  • minWidth of 900px, 1200px and 2000px; card versions 1.5 and 1.6; with and without msteams.width: "Full".
  • Environment: Teams desktop, client version 26276.505.5234.9924. Not tested: Teams web, mobile, Outlook, Copilot.

Why this looks like a Teams issue

  • minWidth is defined in the newer schema at adaptivecards.microsoft.com/schemas/adaptive-card-2026-01-13.json, but not in the public 1.5 or 1.6 schemas on GitHub. It is unclear which hosts support it and from which version.
  • The Teams cards reference says Adaptive Cards must not display a horizontal scroll.

Impact

Wide tables can't be made readable in Teams. msteams.width: "Full" helps on desktop but can't add room on narrow surfaces, and there is no other way to keep a wide table usable.

Ask

Please either honor Table.minWidth with horizontal scrolling in Teams

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Ashlesha Pawar (Tata Consultancy Services Limited) 565 Reputation points Microsoft External Staff
    2026-11-02T05:40:06.5533333+00:00

    Hi Vignesh,

    We were able to reproduce the reported rendering behavior: the table columns are compressed into the available card width with heavy text wrapping, despite setting Table.minWidth to 1200px, and no horizontal scrollbar is displayed.

    We are raising this with the engineering team for investigation, including confirmation of whether Table.minWidth is supported in Teams and whether this behavior is a product limitation or a defect.

    We’ll share an update here as soon as we have more information. Thank you for providing the detailed repro steps and sample payload.User's image

    Was this answer helpful?

    0 comments
  2. Ruby Nguyen 3,640 Reputation points Independent Advisor
    2026-10-30T17:55:39.7266667+00:00

    Good day Vignesh, 

    Thank you for sharing the detailed findings and test results. 

    Just to gently clarify before going any further, this forum is separate from Microsoft Support. I don’t have the ability to access or investigate individual accounts or escalate the issue directly Microsoft Support because this is a user‑to‑user support forum. 

    Since the behavior remains the same across different minWidth values, Adaptive Card versions and delivery methods, I recommend opening a support ticket through the Microsoft 365 admin center > Support > Help & Support for further investigation: 

    • Turn off the "Support Assistant" feature.     
    • Use the keyword "Support" to quickly bypass automated suggestions > Select Contact Support.   

    User's image

    • In the ticket description, please clearly describe the issue, including any error messages or codes and the steps you’ve already tried. You can also attach screenshots or screen recordings.   
    • Additionally, sharing your preferred contact times may help the support team handle the case more efficiently.      

    Note: If you don't see the support option or don't have sufficient administrative permissions, please contact your Global Administrator for assistance.  

    A technical support engineer can review the reported behavior, validate whether this is a known limitation or an unexpected issue and investigate the current support status of Table.minWidth in Microsoft Teams. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.     

    I wish I could help more directly, but as a fellow user in this community, providing these steps is the best support I can offer. Thank you for your patience and understanding.  

    If you have any extra questions about this answer, please click "Comment".    

    Was this answer helpful?

  3. AI answer

    2026-10-30T17:32:04.94+00:00

    Teams chat Adaptive Cards cannot currently rely on Table.minWidth to create horizontal scrolling; redesign the card responsively and report the mismatch as a Teams renderer capability request.

    Why minWidth is ignored

    The documentation describes two related but distinct models:

    • The core Adaptive Cards Table element was introduced in schema 1.5. Its published properties include columns, rows, alignment, and grid settings, but not minWidth.^1^
    • minWidth is documented on Table in the newer @microsoft/teams.cards SDK model. That API says it accepts auto or a pixel value and produces a scrollbar when insufficient width is available.^2^
    • The API documentation does not establish that this newer SDK property is implemented by the Adaptive Card 1.5/1.6 renderer used for bot or message-extension cards in Teams chats.

    Teams’ host rules also explicitly state that Adaptive Cards must not display horizontal scrolling and advise against fixed-width layouts.^3^ The Teams Store validation rules repeat that horizontal scrolling in Adaptive Cards must not be present.^4^

    Consequently, the Designer demonstrates the newer property’s defined behavior, but it does not prove that the Teams chat host enables that behavior. The identical results from the webhook and message extension are consistent with a host renderer limitation, rather than either delivery mechanism.

    No supported card-version change, msteams.width setting, or larger minWidth value is documented as enabling this in Teams, so the variations already tested do not need to be repeated.

    Supported layout options

    Keep the chat card within the available width:

    1. Show fewer columns, retaining only the fields needed to identify or act on a row.
    2. Move secondary values below the primary value inside each row or represent each record as a vertically stacked container.
    3. Use weighted widths to prioritize important columns, while keeping wrap: true.
    4. Paginate long datasets with actions rather than placing the complete dataset in one card.
    5. Open a tab, dialog, or external application for a full data-grid experience when horizontal scrolling is essential.

    For example, restructure each result as a narrow summary:

    {
  "type": "Container",
  "separator": true,
  "items": [
    {
      "type": "TextBlock",
      "text": "Sample value 1",
      "weight": "Bolder",
      "wrap": true
    },
    {
      "type": "FactSet",
      "facts": [
        { "title": "Status", "value": "Active" },
        { "title": "Owner", "value": "Sample owner" }
      ]
    }
  ]
}

    Microsoft’s design guidance recommends designing for narrow screens first because narrow layouts scale to wider surfaces, while wide layouts do not reliably scale down. It also notes that available width varies by device and that mobile does not support horizontal scrolling in this scenario.^5^

    msteams.width: "Full" can still improve desktop presentation, but it cannot make a fixed-width table portable to chat panes, meeting side panels, or mobile surfaces.

    Report the renderer/API mismatch

    This is suitable for a Teams developer issue because the Teams Cards SDK documents Table.minWidth, while Teams message cards do not implement the documented result.

    1. Search the Teams SDK repository for an existing Table.minWidth issue.
    2. If none exists, open a Teams SDK → Issues report through the official Teams developer feedback route.^6^
    3. Include:
      • Teams desktop version and operating system.
      • Delivery paths: Workflows webhook and action-based message extension.
      • The minimal payload from the question.
      • Designer result versus Teams result.
      • Screenshots of both.
      • Links to the core Table schema and Teams Cards SDK minWidth documentation.
      • A request to clarify whether minWidth is planned for Teams message-card renderers or limited to the newer Teams Cards SDK model.

    Do not include tenant IDs, tokens, webhook URLs, or other credentials because repository issues are public. For a business-critical application, open a Microsoft 365 service request from Microsoft 365 admin center → Support; public GitHub issues have no guaranteed response time.^6^

    References

    1. Table Element - Adaptive Cards | Microsoft Learn
    2. Table class-Property Details
    3. Types of cards
    4. Teams Store validation guidelines
    5. Designing Adaptive Cards for your Microsoft Teams app
    6. Support and feedback for Teams developers
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.