Additional team and channel-related features and issues within Microsoft Teams for business
Teams Workflows that use the When a Teams webhook request is received trigger post their messages through the Workflows (Power Automate) infrastructure. In this model, the activity feed and toast notifications show a generic "Workflows posted a new message" entry and don't surface a custom preview text from the incoming payload.
The available documentation for Workflows and Teams webhooks describes:
- Using workflow templates such as Send webhook alerts to a channel or building a flow from scratch with the When a Teams webhook request is received trigger to post messages to chats or channels.
- Support for Adaptive Cards and Message Card formats, with some limitations (for example, button rendering), but it does not expose any configuration to control the short preview text shown in the Teams activity feed or toast notifications.
- Known issues and limitations focus on posting identity (flow bot vs. user) and channel types, not on notification previews.
There is therefore no documented way in Workflows to restore the old Office 365 connector behavior where the Grafana alert summary appeared as the preview text in Teams notifications. The preview text is controlled by Teams for Workflows messages and is not configurable via the webhook payload or the workflow definition.
To get richer, more controllable notifications, the documented alternatives are:
- Build a notification bot (for example, using the Microsoft 365 Agents Toolkit) and send proactive messages, or
- Use other notification mechanisms such as the Teams notification APIs or activity feed notifications, which provide more control over how notifications appear.
However, these approaches require building a custom Teams app or bot; they do not change the behavior of the existing Teams Workflows webhook templates.
References: