Microsoft Teams Asymmetrical communication | Friends of the Crustacean 🦞🤝 | Page 1

lost grail Apr 28, 2026, 1:57 AM

#

After upgrading to v4.25.26 or v4.26.26 Agent no longer replies back Group or DM in Microsoft Teams. Agent is able to message into a group chat just fine. Does not respond back in DM even with @ mentions. Downgrading to v4.9.26 fixes the issues. Discord is fine in both directions.

glad rainBOT Apr 28, 2026, 1:57 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

slim wadiBOT Apr 28, 2026, 1:57 AM

#

Exec approval is required, but no interactive approval client is currently available.

Approve it from the Web UI or terminal UI, or enable a native chat approval client such as Discord. If those accounts already know your owner ID via allowFrom or owner config, OpenClaw can often infer approvers automatically. Then retry the command. You can usually leave execApprovals.approvers unset when owner config already identifies the approvers.

#

Exec approval is required, but native chat exec approvals are not configured on Discord.

Approve it from the Web UI or terminal UI for now. Discord supports native exec approvals for this account. Configure channels.discord.execApprovals.approvers or commands.ownerAllowFrom; set channels.discord.execApprovals.enabled to auto or true.

#

Automatic session resume failed, so sending the status directly.

Exec denied (gateway id=cae96c82-dcfc-4d02-b208-e559b7b7c622, approval-timeout (allowlist-miss)): find /home/krill/openclaw-ref/docs -maxdepth 3 -type f | sed 's#^#/##' | rg -i 'teams|msteams|microsoft'

#

That smells like a Teams inbound routing regression, especially since the exact same config works again after downgrading.

A couple of quick checks so we can pin it down:

Please paste exact output of:
```
openclaw --version
openclaw status
```
Small thing: versions are usually 2026.4.25 style, so I want to confirm whether you mean 2026.4.25 / 2026.4.26.
While sending a Teams DM and a group mention, watch gateway logs and look for whether Teams inbound is seen at all:
- if you see no msteams received/inbound log, likely plugin/webhook regression
- if you see ignored / pairing / allowlist, it’s access policy config
- if you see dispatching to agent but no reply, it’s reply-back/session routing

Relevant config gotchas: Teams DMs default to dmPolicy: "pairing" and group chats default to groupPolicy: "allowlist"; allowFrom / groupAllowFrom should ideally use stable AAD object IDs, not display names/UPNs. Groups/channels are mention-gated by default via requireMention. (docs.openclaw.ai)

#

Given rollback fixes it, I’d also file this as a GitHub regression with:

working version
broken version(s)
OS + Node version
install method
redacted channels.msteams config
gateway log excerpt for one DM + one group mention

Issue tracker: https://github.com/openclaw/openclaw/issues

#

Quick update: my local source/docs grep didn’t run — exec approval timed out/was denied — so I can’t confirm the exact code diff from here.

Current docs confirm the key Teams gates to test:

DMs default to channels.msteams.dmPolicy: "pairing".
Groups default to channels.msteams.groupPolicy: "allowlist" and need groupAllowFrom, or groupPolicy: "open" while still mention-gated.
Teams allowlists should use stable AAD object IDs; display-name/UPN matching is disabled by default. (docs.openclaw.ai)

Given 2026.4.9 works and 2026.4.25/2026.4.26 doesn’t, I’d treat this as a likely regression. Best next artifact is:

openclaw --version
openclaw status --all
openclaw logs --follow

Then send one Teams DM + one Teams group mention and file the redacted log/config in GitHub: https://github.com/openclaw/openclaw/issues

OpenClaw

Microsoft Teams - OpenClaw

lost grail Apr 28, 2026, 2:05 AM

#

OpenClaw 2026.4.26 (be8c246)

no movement in logs when sending test messages

slim wadiBOT Apr 28, 2026, 2:06 AM

#

If there’s zero movement in OpenClaw logs when Teams messages are sent, that’s useful: this is probably before agent routing. So not allowFrom, pairing, mentions, or model/session behavior — Teams traffic likely isn’t reaching the OpenClaw Teams webhook at all in 2026.4.26.

I’d check these in order:

openclaw status --all
openclaw gateway status
openclaw logs --follow

Then while logs are following, send a Teams DM. If still nothing:

Verify the Teams bot endpoint still points to:
```
https://<public-host>/api/messages
```
and that it forwards to the configured channels.msteams.webhook.port / path.

#

Run:
```
teams app doctor <teamsAppId>
```
That should catch Bot Framework / manifest / endpoint issues.
Locally test whether the webhook listener exists:
```
curl -i http://127.0.0.1:3978/api/messages
```
A non-404/connection-refused response is enough to prove something is listening. If it’s connection refused, the Teams plugin/webhook probably didn’t start.

Since 2026.4.9 works and 2026.4.26 (be8c246) has no inbound log movement, I’d file this as a regression: https://github.com/openclaw/openclaw/issues

Include:

working: 2026.4.9
broken: 2026.4.26 (be8c246) and 2026.4.25

#

“outbound Teams send works, inbound Teams webhook produces no OpenClaw logs”
redacted channels.msteams config
openclaw status --all
result of curl -i http://127.0.0.1:3978/api/messages

Docs for the Teams channel: https://docs.openclaw.ai/channels/msteams

#

Sorry — I was asking for the exact version because v4.25.26 looked like it might mean 2026.4.25. You confirmed later: OpenClaw 2026.4.26 (be8c246).

With no log movement at all when Teams messages arrive, this is almost certainly not pairing/allowlist/mention config. It means inbound Teams webhook traffic is probably not reaching OpenClaw or the Teams plugin listener didn’t start.

Best next checks:

openclaw status --all
openclaw logs --follow

Then send a Teams DM. If still nothing, check:

curl -i http://127.0.0.1:3978/api/messages

#

connection refused / 404 → webhook/plugin listener issue
any Bot Framework auth-ish response → listener exists, then the public endpoint/tunnel/Azure bot endpoint is the next suspect

Since 2026.4.9 works and 2026.4.26 doesn’t, please file it as a regression with logs/status here: https://github.com/openclaw/openclaw/issues

Teams docs: https://docs.openclaw.ai/channels/msteams

lost grail Apr 28, 2026, 2:10 AM

#

what should i write in the bug report

slim wadiBOT Apr 28, 2026, 2:10 AM

#

Use something like this:

## Summary
Microsoft Teams inbound messages stopped reaching OpenClaw after upgrading from 2026.4.9 to 2026.4.25/2026.4.26.

Outbound Teams sending still works, and Discord still works both directions. Downgrading to 2026.4.9 restores Teams replies.

## Versions
- Working: OpenClaw 2026.4.9
- Broken: OpenClaw 2026.4.25 and 2026.4.26
- Current broken build: OpenClaw 2026.4.26 (be8c246)
- OS:
- Node version:
- Install method: npm/source/other

#

## Channel
Microsoft Teams / `channels.msteams`

## Symptoms
- Agent can send messages into a Teams group chat.
- Agent does not respond to Teams DMs.
- Agent does not respond to Teams group messages, even with @mentions.
- `openclaw logs --follow` shows no movement at all when sending Teams test messages.
- Discord still works normally.
- Downgrading to 2026.4.9 fixes the issue with the same Teams setup/config.

## Expected behavior
Teams DMs and @mentioned group messages should be received by OpenClaw and routed to the agent.

## Actual behavior

#

Teams messages appear to never reach OpenClaw inbound handling/logging on 2026.4.25/2026.4.26.

## Reproduction steps
1. Run OpenClaw 2026.4.9 with Microsoft Teams configured.
2. Send a Teams DM or @mention the bot in a Teams group chat.
3. Confirm the agent replies.
4. Upgrade to OpenClaw 2026.4.26.
5. Send the same Teams DM or group @mention.
6. Observe no reply and no new OpenClaw log movement.
7. Downgrade to 2026.4.9.
8. Observe Teams replies working again.

## Diagnostics
Please attach/paste redacted output from:

```bash

#

openclaw status --all
openclaw gateway status


Also include any relevant `openclaw logs --follow` output around startup and around a Teams test message.

## Redacted config
Paste redacted `channels.msteams` config here:

```json5
{
  channels: {
    msteams: {
      enabled: true,
      appId: "<redacted>",
      appPassword: "<redacted>",
      tenantId: "<redacted>",

#Microsoft Teams Asymmetrical communication