In my previous post I guided you through a list of steps required to build, send and handle response from Adaptive Cards as Actionable Messages in Outlook. Let me now tell you, how to secure the response.
It has been a while since I first thought about writing this post. Recently I had more questions around this topic and somehow realized, that indeed this is something about Adaptive Cards that I haven’t yet written about. So let me fix it with this ultimate guide.
I’ve been asked that question multiple times – how to assign a single Adaptive Card to multiple Microsoft Teams users and then collect responses. The point is, that action “Post an Adaptive Card to Teams user and wait for response” lets us to collect just a single response at a time. So how can we do it?
This topic has been continuously raised by multiple people I’ve been talking to. How can a user be mentioned in Microsoft Teams when a message is sent from Power Automate? This issue seemed to never been really possible for us, Power Users, until couple days ago Microsoft released new action in Microsoft Teams set in Power Automate called: “Get @mention token for a user”. It’s even cooler, because it works with Adaptive Cards too!
In the beginning of July Microsoft has added two new triggers for Power Automate to integrate better with Microsoft Teams: For a selected message and When a new team member is added. In this post I will go you in details through the first one from them.
With this new trigger you can add create a new level of governance for your Microsoft Teams. Especially when speaking about the on-boarding users or other automated processes for newly added Teams members.
Have you seen that huge warning, when trying to add a newly created Power Automate flow as a child flow, saying: “The workflow with id '<ID>', name <NAME> cannot be used as a child workflow because child workflows only support embedded connections.“? Looks scary! What does it mean? How to fix it? Let me show you!
Today Audrie Gordon Senior Program Manager for Power Automate organized webinar where she announced new changes to the integration between Power Automate and Microsoft Teams when talking about Adaptive Cards.
Features she was presenting are a long awaited functionalities we all were missing very much and which really fill the gap in business processes that are being created using Adaptive Cards and a no-code approach.
On 21st August 2019 Microsoft announced that actions in Microsoft Flow from Outlook stack, are going to be moved from using Outlook REST API v1.0 to Microsoft Graph v1.0. Along with that information there was also written, that current Outlook API 1.0 is going to be decommissioned in 1st of November 2019. So after that date all old actions in Microsoft Flow are going to be removed too.