cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
vbvbvb
Employee
Employee

Ms Teams @ Mentions in adaptive cards

There were already couple of posts with this  topic but without definitive answers.

According to recently published documentation: https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-format?t...

 

To include a mention in an Adaptive Card your app needs to include the following elements

  • <at>username</at> in the supported adaptive card elements
  • The mention object inside of an msteams property in the card content, which includes the Teams user id of the user being mentioned

And a bit vague code with following example how to add that:


"msteams": {
"entities": [
{
"type": "mention",
"text": "<at>John Doe</at>",
"mentioned": {
"id": "29:123124124124",
"name": "John Doe"
}

Many 3rd party websites are full with information about that ID value - some say it should be Teams user ID (or Azure AD orgID - same thing), but this example format doesn't look like this - i have tried various version with full OrdID,  without "-", etc ,even using pure JSON from this article example - all lead to Flow simply failing. 

 

It seems need to have very Teams specific context like that 'id':

"id": "29:1GcS4EyB_oSI8A88XmWBN7NJFyMqe3QGnJdgLfFGkJnVelzRGos0bPbpsfJjcbAD22bmKc4GMbrY2g4JDrrA8vM06X1-cHHle4zOE6U4ttcc",

"objectId": "9d3e08f9-a7ae-43aa-a4d3-de3f319a8a9c",

"givenName": "Larry",

"surname": "Brown",

"email": "Larry.Brown@fabrikam.com",

"userPrincipalName": "labrown@fabrikam.com"

 

Any idea how to retrieve that from the team? Some Graph query maybe?

 

Is there's anything else required for "Post your own adaptive card as Flow bot to a channel" to simply process this mentions ? And also, how to make it multi-user if this is possible?

1 ACCEPTED SOLUTION

Accepted Solutions
vbvbvb
Employee
Employee

Managed to self-resolve it , instead of trying to get that "29:" Teams ID bot ID context, using "8:orgid" instead:

 

"type": "mention",
"text": "<at>John Doe</at>",
"mentioned":
{
"id": "8:orgid:{org-ID-of-the-user}",
"name": "John Doe",
}

View solution in original post

19 REPLIES 19
vbvbvb
Employee
Employee

Managed to self-resolve it , instead of trying to get that "29:" Teams ID bot ID context, using "8:orgid" instead:

 

"type": "mention",
"text": "<at>John Doe</at>",
"mentioned":
{
"id": "8:orgid:{org-ID-of-the-user}",
"name": "John Doe",
}

alrez
Community Support
Community Support

Hi,

 

Its great that you were able to solve your issue here. It looks like graph was doing some interesting transforming of the data which made it a little unintuitive. 

 

Regards,

 

Alex

 

-------

 

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 I think main issue here that all @ metnions in adaptive cards documentation only says 29:xxxxxxxxxx ID in Bot Framework context. I posted GitHub query on that documentation page and got reply with screenshot saying that 29:xxxxx ID is obtainable via Bot Builder etc. But for Flow this is not very intuitive indeed to use that - would make so much sense to make <at> work like they do in the Flow bot messages without jumping via hoops of determining orgID etc.

 

For example, I want to have @ mentions in the adaptive card dynamically generated  - with <at>User1</at>,<at>User2</at>, etc it's quite simple to make Flow read this from SPO list for example, but when i need to make dynamically generated list of users to mention in form of string which looks like this: {"type":"mention","text":"<at>User1</at>","mentioned":{"id":"8:orgid:1234etc","name":"User1",}},{"type":"mention","text":"<at>User2</at>","mentioned":{"id":"8:orgid:5678etc","name":"User2",}}, - and then still have to match all these users with <at>User1</at>, <at>User 2</at> - it's is such overengineering to be honest..

 

Anonymous
Not applicable

Hey vbvbvb,

 

Could you help with an example on how to get the orgid and org-ID-of-the-user in your example?

"id": "8:orgid:{org-ID-of-the-user}"

 

Also, should I always use "8:" at the front?

 

Thanks!

Hi @Anonymous ,

 

OrgID or objectID can be obtained via multiple ways - get Azure AD user, via Graph query , etc.  As example:

Get-ADUser -Identity user -Properties * > look for objectGUID

 

8:orgid: always has to be there, followed by user object ID (orgID), for example:

 

"id": "8:orgid:e1418d64-096c-4cb0-b903-ebb66562d99d"

 

I managed to automate that via Flow too via HTTP request to Azure AD action using Graph query :

 

https://graph.microsoft.com/v1.0/users?$filter=mail eq 'jon.doe@contoso.com'&$select=id

 

Output would be like this and you just have to use Pase JSON to get dynamic value for orgID to use (for example write to SPO list of something to use later in @metnions .

{
  "value": [
    {
      "id""e1418d64-096c-4cb0-b903-ebb66562d99d"
    }
  ]

 

 

Anonymous
Not applicable

Hi vbvbvb,

 

Thanks for the quick response! I have tested it out in a simple card with just text and it seems to be working.

I'm having trouble integrating this into my actual adaptive card that looks abit like this below.

I read that the msteams entities part of the code should be placed after the $schema.

Could you help to take a look to see where it should be included?

{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.0",
    "body": [
        {
            "type": "TextBlock",
            "text": "Mention_Test",
            "weight": "Bolder",
            "size": "Medium"
        },
        {
            "type": "ColumnSet",
            "columns": [
                {
                    "type": "Column",
                    "width": "stretch",
                    "items": [
                        {
                            "type": "TextBlock",
                            "spacing": "None",
                            "text": "Created 1234",
                            "isSubtle": true,
                            "wrap": true
                        }
                    ]
                }
            ]
        },
        {
            "type": "TextBlock",
            "text": "<at>testing</at>",
            "size": "Medium",
            "wrap": true
        },
    "msteams": {
      "entities": [
        {
          "type": "mention",
          "text": "<at>testing</at>",
          "mentioned": {
            "id": "8:orgid:baae7aa8-035a-zzzz-yyyy-xxxx",
            "name": "test123"
          }
        }
      ]
    }
  ]
}

 

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous,

 

I think you need to correct two things in your json. Try and use version 1.2 of the schema. They added mentioned support in that one:

https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-format?tabs=adaptive-md%2Cconnector-html

 

Also the name of the user was different in the mentioned section. So I changed that too.

 

Here is a new code snippet:

 

{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.2",
    "body": [
        {
            "type": "TextBlock",
            "id": "MentionTextBlock",
            "text": "Mention_Test",
            "weight": "Bolder",
            "size": "Medium"
        },
        {
            "type": "ColumnSet",
            "id": "MentionColumnSet",
            "columns": [
                {
                    "type": "Column",
                    "id": "MentionColumn",
                    "width": "stretch",
                    "items": [
                        {
                            "type": "TextBlock",
                            "id": "MentionTextBlock2",
                            "spacing": "None",
                            "text": "<at>Testing</at>",
                            "isSubtle": true,
                            "wrap": true
                        }
                    ]
                }
            ]
        }
    ],
    "msteams": {
        "entities": [
            {
                "type": "mention",
                "text": "<at>Testing</at>",
                "mentioned": {
                    "id": "8:orgid:yourid",
                    "name": "Testing"
                }
            }
        ]
    }
}

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Is the OrgID constant for every user in a org?

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @AlexBal,

 

Like mentioned by @vbvbvb it's the user object ID. So it will be different for every user.



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Indeed, @AlexBal , it would be different for every user, but constant throughout  the tenant.  

@vbvbvb 

 

I'm having a problem having a dynamic username for the mention.  Have you come up with a way to do this?  The solution I am using appears to break in Android, but works successfully everywhere else.

@cdn4lf  works fine in Adaptive cards in Android and visually still in iOS, but using that method with OrgID slightly break card design and this bug is get worked on already. If in you case you just get blank card in Android when @ mentions are used, you have issue in card JSON. Try to reduce card code it to bare minimum, ensure you are using  adaptive card version 1.2+ etc.

@vbvbvb here is the link to my other post /question. Would you be able to assist with correcting the issue?

 

https://powerusers.microsoft.com/t5/Building-Flows/Teams-Adaptive-Card-Mentions/m-p/650918#M87114

I think you have to be sure that both mention TextBlock and msteams part have "Name, Surname" identical to that in 'name':

"items": [
                        {
                            "type": "TextBlock",
                            "id": "MentionTextBlock2",
                            "spacing": "None",
                            "isSubtle": true,
                            "wrap": true,
                            "text": "Dear <at>{$root.Name} {$root.Surname}</at>,"
                        }

 

"msteams": {
        "entities": [
            {
                "type": "mention",
                "text": "<at>{$root.Name} {$root.Surname}</at>",
                "mentioned": {
                    "id": "8:orgid:{$root.id}",
                    "name": "{$root.Name} {$root.Surname}"
                }
            }
        ]
    },

 

@vbvbvb 

 

When I attempt to use your suggestion I get an invalid json error when attempting to launch the flow.

 

The request failed. Error code: 'MissingOrInvalidBotAdaptiveCardRequest'. Error Message: 'The specified Teams flowbot adaptive card request is missing or invalid. The tracking Id is '23fc4d80-7b06-4261-9073-0232d4c77de1'.'.

 

When I switch it back to <at>username</at>, everything works.  What it appears to be is that the Android version of Teams isn't reading the mention the same way, when part of an adaptive card, and is falling back to the static name of the mention instead of the dynamic code.

Probably you would have to change the way how Name, Surname is populated. Can't you use HTTP to Azure AD query or Get O365 user action and use returned DisplayName value to use in mentions?

@vbvbvb  I am using the 0365 connector to get the employee information from AD.  From there, I am get their unique ID as well as their display name/surname/given name.

 

The problem is that Android is falling back to the default text and not properly reading the information.  Apparently this could be due to issues with the developer preview.

 

From what I understand, the <at>name</at> is a placeholder and references the mention entity below.  The name within that mention entity is what is supposed to appear, but doesn't due to the issues with the developer preview.

 

Using the mention token called within Power Automate also doesn't work within the new card editor, as it simply passes the information then fails.

Hellder
New Member

Considering my complete lack of knowledge, I had a hard time using the orgid method. If it can be of any help, I added this to the adaptive card and it worked perfectly fine for what I needed.

{

  "type": "TextBlock",

  "text": "<at>youradress@mail.com</at>",

}

ianwuk
Post Partisan
Post Partisan

@Hellder Can you please share how you added that to your card and the complete syntax please?  I also want to achieve this.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (2,533)