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

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

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

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",
}

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"
          }
        }
      ]
    }
  ]
}

 

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?

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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,932)