Check When to Reconnect Microsoft Teams Credentials After Upgrading n8n

Can you use the new Teams operations right after upgrading?

No. For channel message deletion in 2.40, the release notes say existing credentials keep their original permissions, and for activity feed notifications in 2.42, they say you must reconnect existing OAuth2 credentials to get the new permission. The node documentation also lays out the same information by version.

Input (Teams operation in the workflow) → n8n version → permissions the credential holds → Microsoft admin consent

All four have to line up for the new operation to run. Upgrading the version alone does not fill in the last two.

Which permissions were added in which version?

This is the reconnection guide from the node documentation. It applies to Teams OAuth2 credentials created before the version in question. 2.40 came out on 2026-09-15, 2.41 on 2026-09-22, and 2.42 on 2026-09-29. The date checked is 2026-10-12.

The 2.43 release notes have no Teams entries. The documentation also says that to use user mentions you need User.Read.All as well.

How do you reconnect?

The steps differ depending on the type of credential.

1. For the default Teams OAuth2 credential, reconnect from the credential screen to get the new permission.
2. If you turned on Custom Scopes, first add the needed permission to Enabled Scopes, then reconnect.
3. For a Microsoft OAuth2 (Graph) credential, you need to add the permission directly in the Scope field.

Before reconnecting, count how many workflows use this credential. If several workflows share the same credential, a single reconnection affects all of them. These steps are general advice based on the documentation, and you should check the actual screen names in the version you use.

What happens if you cannot get admin consent?

The documentation explains that ChannelMessage.ReadWrite requires admin consent. Without consent, Microsoft stops at an "approval required" step and the credential cannot get a token. It says that when this happens, not only the delete operation but every operation using that credential fails.

So if you do not need deletion right away, it is safer not to rush to add the permission. If your team does need it, send the consent request to your Microsoft 365 admin first.

What else do activity feed notifications need?

Activity feed notifications appear in the recipient's Activity tab, not in a channel or chat. The permission alone is not enough, and the documentation lists more requirements.

• You need a paired Teams app whose manifest webApplicationInfo.id matches the credential's client ID.
• An admin has to publish that app to the organization catalog, and each recipient has to install it. It can take a few minutes for the installation to take effect.
• The Topic Link must be an https address on a Microsoft Teams domain.

Without the paired app, Microsoft Graph returns a 403. This operation works with OAuth2, Microsoft, and Service Principal credentials alike.

What should you test before adding it to a production workflow?

Before changing a production workflow, run it first on a copy with a single recipient. Check both that existing Teams operations still run as before right after reconnecting, and that the new operation finishes without a 403 or an approval-required error. If something goes wrong, leave the existing notification path alone and roll back only the new operation.

Sources: n8n Release notes, n8n Microsoft Teams node. Date checked: 2026-10-12.