web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Enable custom preview ...
Power Automate
Suggested Answer

Enable custom preview text for Adaptive Cards posted via Power Automate in Teams

(2) ShareShare
ReportReport
Posted on by 6
When posting Adaptive Cards to Microsoft Teams channels using Power Automate, the notification currently displays “Preview Unavailable”. This occurs because the connector does not provide a way to define a preview message for notifications. As a result, users only see a generic message, which reduces engagement and clarity. This happens with users, service accounts, and bots.
 
Main Point: This simple enhancement could significantly improve the flexibility and effectiveness of custom card posting in Microsoft Teams across any scenario.

Problem:
 
  • Notifications are critical for visibility and quick action.
  • “Preview Unavailable” provides no context, causing users to ignore or miss important messages.
  • Bot Framework and Graph API allow specifying a text property for previews, but Power Automate does not.

Proposed Solution:
  • Add a “Preview Text” field to the Post Adaptive Card in a chat or channel action in Power Automate. This field would:
  • Accept a short text string (e.g., “Critical Incident Notification: Please review details in the card”).
  • Display this text in Teams notifications instead of “Preview Unavailable.”

Benefits:
  • Improves user experience and engagement.
  • Provides parity with Bot Framework capabilities.
  • Simple implementation with high impact for organizations using Power Automate for Teams notifications.

Enterprise Justification:
Large organizations rely on Power Automate and Teams for critical workflows such as incident management, compliance alerts, and operational updates. These notifications often require immediate attention. When the preview shows “Preview Unavailable,” users may overlook urgent messages, leading to delays in response and potential business impact.
 
Providing a customizable preview text ensures:
  • Faster decision-making by giving context at a glance.
  • Improved adoption of Teams-based workflows.
  • Reduced operational risk by ensuring critical alerts are not ignored.
Preview Unavailable.jpg
I have the same question (4)
  • Expiscornovus Profile Picture
    33,876 Most Valuable Professional on at
     
    Yes, those sound like good improvements.
     
    Microsoft has an ideas section for these type of improvements, my suggestion would be to post this idea over there as well. This gives others the option to upvote your idea and to bring this to the attention of the product team.
    https://ideas.powerautomate.com


     
    Happy to help out 😁

    I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel
     
  • yong_lee8838 Profile Picture
    21 on at
    I strongly agree. The removal of the preview text by Power Automate teams was a very poor decision.
  • Suggested answer
    nickyl Profile Picture
    4 on at
    I finally figured something out that worked for me, after looking for a solution for about a year. 
    In my flow, I use the  action "Post a card in a chat or channel" and post as a User. Under the "Adaptive card" section, there is a section for "Advance parameters" with a dropdown menu. I checked the box for "Subject" and this enables a subject field, where in my case I added text and a dynamic function. 

    Update: If you update an existing adaptive card using the action "Update a card in a chat or channel",as a "user"  there is no
    "Subject" parameter field under the section for "Advance parameters". The card will update with a "Preview Unavailable". They need to add in the "Subject" parameter for this action.
  • Laurenz_H Profile Picture
    4 on at

    ’ve implemented the workaround (to get a preview message) using the Subject field, but unfortunately it introduces a couple of issues:

    1. Duplicate / wasted space
      The subject is rendered above the Adaptive Card as a header.
      This leads to duplicated information if the same content is already included in the card itself, and it unnecessarily consumes valuable space.

    2. Phone number auto-detection on mobile
      In the Teams mobile app, any number in the subject (starting from ~3 digits) is automatically interpreted as a phone number.
      This makes it clickable and can trigger unintended calls.

      Attempts to prevent this (e.g., adding spaces, hyphens, or even zero-width spaces) do not work.

     

    But I found another workaround: Send a chat first and then update it with a card. Pretty annoying but it works. Source: https://github.com/MicrosoftDocs/msteams-docs/issues/9135#issuecomment-3853584260

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 462

#2
Vish WR Profile Picture

Vish WR 256

#3
David_MA Profile Picture

David_MA 242 Super User 2026 Season 1

Last 30 days Overall leaderboard