Skip to main content
The Microsoft Teams integration delivers an Adaptive Card to the channel you choose, with the incident context and buttons that take you straight to the dashboard.

​
Setting it up

1

Create the webhook in Teams (Workflows)

In the target channel, select … → Workflows and choose the “Post to a channel when a webhook request is received” template. Pick the team and channel, finish the setup and copy the generated HTTP webhook URL.
2

Add the integration in aciona.me

Under Integrations → Microsoft Teams, paste the URL in Organization configuration. Optionally give it a display name so you can recognize the destination later. Owners and admins can do this.
3

Test it

Click Test and confirm the card arrives in the channel.
Microsoft is retiring the legacy Incoming Webhook (Office 365) connectors. If your tenant still offers them they keep working, but the recommended path going forward is the Workflows webhook.

​
One channel per team

The organization configuration is the default for every team. Under Team overrides, you can point a specific team to another channel (or disable it). Teams without an override keep using the organization webhook.

​
What arrives in the channel

An Adaptive Card in the organization’s language with severity, title, service, origin, current owner and the Open incident, Acknowledge and Assign to me buttons. As with Slack, the card follows the incident lifecycle — creation, acknowledgement, assignment, escalation and resolution.
Dates on Teams cards are shown in the paged schedule’s time zone, always with the zone shown, to avoid ambiguity between members in different time zones. Without a schedule, the time is in UTC.

​
Accepted addresses

For security, aciona.me only accepts https:// URLs from Microsoft providers: Workflows/Power Automate webhooks (*.logic.azure.com, *.api.powerplatform.com) and legacy connectors (*.webhook.office.com, outlook.office.com, outlook.office365.com). Any other address is rejected on save. Older integrations pointing at an address outside that list stop receiving notifications and show a warning on the integration screen. To fix it, save again with the official URL.

​
Best practices

Keeps the history readable and makes it easy to configure Teams’ own notifications for that channel.
A card in a channel is visibility, not paging. Whoever is on call needs push on their phone.
Teams limits the size of Adaptive Cards. Incidents with very long descriptions may be truncated on the card — the dashboard always has the full content.
Anyone holding the URL can post to the channel. If it leaks, delete the flow in Workflows and create a new one.

​
Troubleshooting