Share via

Render adaptive card full width in Teams

Pandaraboina, Rajesh 0 Reputation points
2025-12-10T14:56:26.35+00:00

I'm experiencing the width issue with adaptive card rendering in teams — even when using:

YAML

msteams: { "width": "full" }

With msteams: { "width": "full" } The rendering is slightly better compared to the previous version. However, it still doesn't appear to occupy the full available width.

Could you please confirm:

  • Is this the maximum width that Teams allows for Adaptive Cards?
  • If not, what would be the recommended approach to achieve true full-width rendering?

Looking forward to your clarification.User's image

Without msteams: {"width":"full"} User's image

Microsoft Teams | Development
Microsoft Teams | Development
Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teddie-D 9,045 Reputation points Microsoft External Staff Moderator
    2025-12-11T01:49:21.8166667+00:00

    Hi @Pandaraboina, Rajesh 

    Thank you for posting your question in the Microsoft Q&A forum. 

    I tested Adaptive Card rendering in both a Teams channel and a group chat. 

    When using: 

    "msteams": { 
    "width": "full" 
  }, 

    -In a channel, the card renders at the maximum width that Teams allows within the channel post. This confirms the feature is working as designed. 
    User's image

    -In a group chat, the card expands only to the maximum width permitted inside the chat bubble, not the full window width. This matches previous observations. 
    User's image

    This confirms that Teams enforces the layout limits consistently across chat surfaces.
    For this issue, I also recommend raising it as a GitHub issue in either the Microsoft Teams or Adaptive Cards repository. As forum moderators, we don’t have access to backend systems or engineering telemetry, so we’re unable to determine whether this behavior is intentional or a regression. By reporting it on GitHub, the product group and engineering team can investigate directly, clarify the expected behavior, and provide updates if any changes are planned. This is similar to how issues such as https://github.com/MicrosoftDocs/msteams-docs/issues/7638were escalated to engineering for further review.
    Thank you for your patience and understanding.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    0 comments

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.