Why does Microsof Teams webhook integration still not work after O365 connector change

[Scott Baierwalter]

The json payload (format) that is being sent from Statuspage is still not compatible with MS Teams after the O365 connector change.  I've recreated new webhooks and consistently receiving error message and Failed action inside of my workflows in MSFT.

Error messages contain:
 - Attachment is 'null'  

- Action 'Post_card_in_a_chat_or_channel_1' failed: Microsoft.Azure.ProcessSimple.Data.Entities.Exceptions.ProcessSimpleDataException: The specified Teams flowbot adaptive card request is missing or invalid. The tracking Id is '{0}'. ---> AdaptiveCards.AdaptiveSerializationException: Property 'type' must be 'AdaptiveCard'
at AdaptiveCards.AdaptiveCardConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at AdaptiveCards.AdaptiveCard.FromJson(String json)
at Microsoft.Azure.ProcessSimple.Data.Components.AdaptiveCards.AdaptiveCardBuilder.DeserializeAdaptiveCard(String serializedAdaptiveCard, RequestIdentity requestor, CultureInfo cultureInfo, BotAdaptiveCardAtMentions atMentions) in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data\Components\AdaptiveCards\AdaptiveCardBuilder.cs:line 930
--- End of inner exception stack trace ---
at Microsoft.Azure.ProcessSimple.Data.Components.AdaptiveCards.AdaptiveCardBuilder.DeserializeAdaptiveCard(String serializedAdaptiveCard, RequestIdentity requestor, CultureInfo cultureInfo, BotAdaptiveCardAtMentions atMentions) in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data\Components\AdaptiveCards\AdaptiveCardBuilder.cs:line 934
at Microsoft.Azure.ProcessSimple.Web.Common.Validation.BotAdaptiveCard(String card, RequestIdentity senderRequestIdentity) in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data\Common\Validation\BotValidation.cs:line 960

[Varad Wagh]

Hello Scott,

Welcome to the Atlassian community!

From the error message you shared, it appears that Microsoft Teams is rejecting the payload as an invalid Adaptive Card. The “Post card in a chat or channel” action expects a Teams message wrapper that includes a valid Adaptive Card with "type": "AdaptiveCard" inside attachments[0].content.

To resolve this, you’ll need to transform the incoming payload into the correct Teams message + Adaptive Card JSON schema before invoking the “Post card in a chat or channel” action.

Best regards,
Varad

[Scott Baierwalter]

Thanks for response Varad, but for the typical end user that simply wants to add a webhook to their teams channel, this seems like additional configuration perhaps beyond the level of the end user in order for this to work where in the past it just worked.  For more advanced users that know how to get to the edit workflow portal I understand but this should just work for the basic user out of the box (or create a MS Teams integration which is not in the manage section of the tools only accessible by the admins.   The subscribers want ease of use, turnkey solutions for this.