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

In cursor:web Automations, I am unable to trigger a cursor automation from the Microsoft teams integration: New Message in Teams channel.

Debugging steps:

  • attempted running as service account and myself
  • switched from multi-repo → single → no repo
  • tried the Teams: Channel Created trigger
    • works fine in target team
  • tried trigger for new messages on the newly created channel
  • used the Run Test feature
    • automation was able to add a message to the target channel
  • Disconnected and reconnected cursor from Microsoft Teams account and also the Team for the target channel
  • Created a second, simpler automation with just the trigger and reply to teams channel
  • Sent messages from my own account and from a coworker in the channel
  • Tried channel in Posts and Threads modes

Recent changelog

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Where does the bug appear (feature/product)?

Cloud Agents & Automations (cursor.com/agents, scheduled/event)


Describe the Bug
A clear and concise description of what the bug is.

I am unable to trigger a cursor automation from the Microsoft teams integration: New Message in Teams channel.


Troubleshooting steps:

  • attempted running as service account and myself
  • switched from multi-repo → single → no repo
  • tried the Teams: Channel Created trigger
    • works fine in target team
  • tried trigger for new messages on the newly created channel
  • used the Run Test feature
    • automation was able to add a message to the target channel
  • Disconnected and reconnected cursor from Microsoft Teams account and also the Team for the target channel
  • Created a second, simpler automation with just the trigger and reply to teams channel
  • Sent messages from my own account and from a coworker in the channel
  • Tried channel in Posts and Threads modes

Expected Behavior
What is meant to happen here that isn’t working correctly?

On a new message in the target teams channel, the automation should trigger a run


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Additional Information
Add any other context about the problem here.

Related changelog:

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 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.

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.

I am also experiencing the same issue. Tried similar t/s steps and Cursor never responds to new chats in teams. Grok Bot also experiences the same issue. It can not detect/respond to new messages in Teams in real time. It does work if I set it to check every 5 minutes instead of real time in Grok Bot.. but the timer test did NOT work in Cursor automation.

Hi @Colin ,

Thank you for taking the time to look at this.

I got this back from my teams admin:

PS /Users/MyName> Get-MgBetaTeamRscConfiguration | Format-List State, ScopeType

State : ManagedByMicrosoft
ScopeType : Team

I’ve followed your steps, but maybe we’re still wrong from the Teams admin side.

  1. As a team owner, when I go to re-add the app to a team,
    I’m starting with + → Apps → Manage your apps → Get more apps → Search cursor → Add.
    And then I reach this point and after clicking go, I’m not seeing a permission request.

But if we scroll down on the generic appinfo page, it does list required permissions.

Hey @William_Crawford, thanks for running all of that and for the admin output and screenshots.

Your Teams setup looks right. The consent setting your admin shared is the default, the permissions are listed, and new Teams doesn’t show a separate permission prompt when you add an app, so you didn’t miss a step.

Your test messages did reach us, and we found the cause on our side: your team uses an older Microsoft ID format for its channels, and our trigger matching doesn’t recognize that format yet. Messages from those channels are skipped before the trigger is checked, which is why nothing runs. That includes @Cursor mentions, so the @mention workaround I suggested earlier won’t help in your case, sorry about that.

I’ve passed this to the team. There’s nothing more you need to change in Teams or your admin settings in the meantime.

@mosdef, your organization doesn’t appear to be affected by this specific issue, so we want to look at yours separately. It might be worth starting a new thread.

I believe that mentioning cursor was previously spinning up a new agent.

My issue is now resolved. I checked on it just now by creating a new post, and was able to get a run started with a response.

I am not surprised that incoming email messages to the channel don’t trigger the automation.

I am also having some trouble with the automation creating a new post instead of replying in the same thread, but it isn’t a big deal.

Hey @William_Crawford,
Quick update: the fix for channels that use the older ID format has been made on our side and will be rolled out soon if it hasn’t been already. You don’t need to change anything in Teams or in your automation.

Once it’s live, a new top-level post in the watched channel should start a run, and @Cursor mentions there will trigger it too.

Could you give it another try and let me know if nothing shows up in Run History? If it still doesn’t fire, the approximate time (and time zone) of your test post would help us dig in.

The run triggered successfully.