Share via

Adaptive Card feedback button icon not loading for some Microsoft Teams desktop users

NageshwarPatilRohini-7820 20 Reputation points
2026-06-04T14:22:35.8466667+00:00

We are using an Adaptive Card JSON and sending the card to multiple users in Microsoft Teams. Most users can view the card correctly, including the feedback button icon. However, a couple of users on the Teams desktop application noticed that the feedback button icon is not loading or displaying properly.

Since the same Adaptive Card works correctly for other users, we would like to understand:

  • Could this issue be related to a specific Microsoft Teams desktop version?
  • Are there any known rendering differences between Teams client versions?
  • Is there any caching, policy, or environment-related reason why icons/images in Adaptive Cards may fail to load for only certain users?
  • Are there any recommended troubleshooting steps to identify the root cause?

Additional observations:

  • The issue is only reported by a few desktop users.
  • Other users receiving the same card can see the icon correctly.
  • The Adaptive Card JSON is the same for all users.

Please let us know if there are any compatibility requirements or diagnostics we should check
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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vergil-V 13,625 Reputation points Microsoft External Staff Moderator
    2026-06-04T15:05:25.0433333+00:00

    Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data. 
    Hi NageshwarPatilRohini-7820

    At the moment, I was not able to find any official documentation that directly addresses the behavior you described. 

    For a more definitive confirmation, I recommend reaching out to the Microsoft Support team through the Microsoft Admin Center. They have access to internal tools and resources that allow them to investigate this type of behavior more thoroughly. You can refer to: Get support - Microsoft 365 admin | Microsoft Learn  

    Please note that we are not Microsoft support, and this is a user-to-user support forum. Moderators and contributors, including external Microsoft employees, do not have backend access and cannot directly intervene in Microsoft products or features. Our role is limited to providing technical guidance and best practice recommendations based on reported issues, requests, or ideas. 

     

    In the meantime, you may consider guiding the affected users to clear the Teams client cache, as this can help refresh the local environment. You can follow this guidance: Clear the Teams client cache - Microsoft Teams | Microsoft Learn 

    image

    Additionally, you may explore alternative approaches for displaying the feedback icon, such as: 

    • Converting the icon to a Base64 Data URI 
    • Hosting the icon on a public CDN 
    • Temporarily relying on text with emoji in the button title 
    • Placing small image elements above the buttons instead of using the iconUrl property 

    I hope this provides some additional insight. If you have any updates, please feel free to share, as it would be valuable for others with a similar experience. 

     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.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-04T14:23:05.2266667+00:00

    Adaptive Card rendering, including icons and media, can differ between clients and versions, and some limitations are documented.

    Key points from the available information:

    1. Client and platform differences
    • Adaptive Cards in Teams have known differences between desktop and mobile clients, especially for media and visual elements. For example, media elements support different behaviors on desktop vs. mobile (inline vs. full screen, PiP, etc.), which shows that host clients can implement features differently and may lag in support for some capabilities.
    • TeamsJS dialog.adaptiveCard and related capabilities are explicitly documented as preview and have different support matrices across web, desktop, and mobile, indicating that not all clients are aligned at all times.
    1. Icon support and limitations
    • Adaptive Card Extensions (ACEs) in Viva/SharePoint show that only a subset of Fluent icons (the “Card Designer” set) is fully supported. Icons outside this set or certain manifest properties (such as officeFabricIconFontName) can fail to render or appear inconsistently across surfaces.
    • There are explicit limitations where icons can be missing in some environments (for example, toolbox or mobile card bar) and the workaround is to override the icon in code.
    • By analogy, if the feedback button icon in the Adaptive Card uses an icon or image that is not fully supported, or relies on a host-specific icon set, certain clients or versions may fail to render it.
    1. Environment and policy-related causes
    • The documented issues around icons and media show that:
      • Some hosts do not support arbitrary Fluent UI icons.
      • Some surfaces (for example, mobile) may not show certain icons at all.
    • This pattern suggests that environment differences (client capabilities, feature flags, preview vs. GA builds) can cause icons to fail for specific users even when the JSON is identical.
    1. Recommended troubleshooting steps Based on the documented limitations and patterns, the following checks are recommended:
    1. Verify icon type and source
    • Confirm whether the feedback button icon is:
      • A Fluent UI icon name (for example, from Fluent 1 or Fluent 2), or
      • A custom image URL (for example, SVG/PNG).
    • If using a Fluent icon name, ensure it is from a supported set similar to the “Card Designer” icons. Unsupported icon names may render for some clients and not others.
    1. Check client/platform differences
    • Compare the affected users’ Teams desktop client build/version with those where the icon renders correctly.
    • Check whether affected users are on a different channel (preview/insider vs. stable) or different OS.
    1. Validate network and content access
    • If the icon is an external image URL, verify that affected users can reach that URL (no network blocks, firewall, or proxy issues).
    • If the icon is hosted in SharePoint/OneDrive, ensure affected users have permission to the file.
    1. Test with a supported icon or local asset
    • Replace the current icon with a known-supported icon (for example, a simple image or a basic icon from a supported set) and send a test card.
    • If the replacement icon renders for all users, the issue is likely with the original icon’s type, source, or support in certain clients.
    1. Use preview tools and samples
    • Use Microsoft Adaptive Card Previewer (with Microsoft 365/Teams tooling) to validate the card design and ensure the card schema and elements are valid.
    • Compare behavior with official samples that include media or icons to see whether the issue reproduces.

    These steps help isolate whether the problem is due to unsupported icon types, client version differences, or environment/network constraints for specific users.

    References:

    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.