> For the complete documentation index, see [llms.txt](https://blog.rhinoautomator.com/brians-integration-and-automation-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.rhinoautomator.com/brians-integration-and-automation-notes/automations/teams-notifications-azure-bot/two-stage-message-process/formatting-the-message-update.md).

# Formatting the Message Update

{% hint style="danger" %}
I've migrated the entire blog over to my new website. Please go to [https://rhinoautomator.com](https://rhinoautomator.com/) for more as this will be deleted at some point.
{% endhint %}

When you send an update to the message, that gets handled differently. The format of the message JSON changes to the below:

{% code overflow="wrap" lineNumbers="true" fullWidth="false" %}

```json
{
  "type": "message",
  "summary": "Set this to a summary that you want to appear in the desktop/mobile notification in Teams",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "contentUrl": null,
      "content": {
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.5",
        "body": [
          // Here you will place all of the JSON for the various pieces of your message that you want to send to Teams. I recommend using the Adaptive Card Designer and Actionable Messages Designers to figure out the formatting. When formatting the message this time, do not forget to add the JSON for your action buttons. See the "Formatting Action Buttons" page for how I handled this.
        ],
        "padding": "None",
        "msteams": {
          "width": "Full"
        }
      }
    }
  ],
  "msteams": {
    "width": "Full"
  }
}
```

{% endcode %}

Additionally, the sub-workflow for updating the message will also need the "card\_id" and "card\_activity\_id" that you received in the response. Those are set as workflow inputs in Rewst for the sub-workflow as they are included in the URL for the PUT call.