# Microsoft Teams: Automations trigger not firing on new message in channel

**URL:** <https://forum.cursor.com/t/microsoft-teams-automations-trigger-not-firing-on-new-message-in-channel/175061>\
**Category:** Bug Reports\
**Tags:** ms-teams, autopilot, automations\
**Created:** [October 16, 2026, 9:42pm UTC](https://forum.cursor.com/t/microsoft-teams-automations-trigger-not-firing-on-new-message-in-channel/175061 "2026-10-16T21:42:42Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 17, 2026, 11:22am UTC](https://forum.cursor.com/t/microsoft-teams-automations-trigger-not-firing-on-new-message-in-channel/175061/12 "2026-10-17T11:22:20Z")

</div>

Hey @William_Crawford, thanks for the report, the screenshots, and all the troubleshooting steps.

Your automation setup looks right. Plain messages (without an @mention) in the watched channel are supposed to trigger “New message in Teams channel” automations. For that to work, Microsoft Teams has to deliver those messages to the Cursor app, and Teams only does that when the app has been granted permission to read that team’s channel messages. From what we can see, plain posts from your Teams organization aren’t reaching Cursor at all, so the trigger never gets a chance to match. Channel Created events and Run Test use a different path, which is why those work.

Reconnecting from [cursor.com](http://cursor.com) usually won’t fix this on its own, because the permission is granted inside Teams. Could you try this:

1. Ask your Microsoft 365 / Teams admin to confirm that resource-specific consent for Teams apps is allowed in your organization (the Teams admin center setting that lets team owners give apps access to their team’s data).
2. As an owner of the team that contains the Alerts (dev) channel, open the team in Teams, go to Manage team \> Apps, and remove the Cursor app.
3. Add the Cursor app back to that team and accept the permissions prompt (it should list reading the team’s channel messages).
4. In the watched channel, start a brand-new post (not a reply in an existing thread) without mentioning @Cursor.
5. Check the automation’s Run History on [cursor.com](http://cursor.com).

Two notes while you test:

- Replies inside an existing thread only trigger the automation if it has a “message contains” filter set, so test with a new top-level post first.
- In the meantime, mentioning @Cursor in the channel does fire the automation, but it also starts a separate Cloud Agent.

If plain posts still don’t trigger it after that, reply with the approximate time (and time zone) of your test post and we’ll dig in further.

---

_[View the full topic](https://forum.cursor.com/t/microsoft-teams-automations-trigger-not-firing-on-new-message-in-channel/175061)._