Teams error 403 NotEnoughPermissions: NotEnoughPermissions - operation requires rights the bot lacks
Last verified against Microsoft Learn - Status codes from bot conversational APIs
*scenario specificWhat error 403 NotEnoughPermissions means
The bot authenticated correctly and the conversation exists, but the specific operation you attempted is above the bot's station. The status table documents NotEnoughPermissions as "Agent doesn't have required permissions to perform the requested action," with a scenario-specific message, no retry, and the action "Determine the required action from the error message."
Typical shapes in Teams: updating or deleting an activity the bot does not own, posting into a moderated channel where bot replies are restricted, or invoking member/roster operations in contexts where the app's resource-specific consent (RSC) permissions do not extend. Because the message text names the missing right, this is one of the codes where logging the full ErrorResponse body pays for itself - the fix is whatever the message says is missing, granted wherever that permission lives (channel moderation settings, RSC grants in the manifest, or app policy).
What it looks like
{
"error": {
"code": "NotEnoughPermissions",
"message": "...operation-specific detail..."
}
}Why it happens
- The bot attempted to update or delete a message it did not author.
- Channel moderation settings restrict who may post or reply, excluding bots.
- A roster or channel operation requires resource-specific consent the app's manifest never requested.
- The operation is valid in one scope (team) but was attempted in another (group chat) where the right does not exist.
How to fix Teams error 403 NotEnoughPermissions
- 1Read the scenario-specific message in the response body; it names the missing permission or restriction.
- 2For moderated channels, ask the team owner to adjust moderation settings or stop targeting that channel.
- 3For RSC-gated operations, add the required permission under webApplicationInfo/authorization in the app manifest and reinstall the app.
- 4Rerun the operation in the scope it is documented to support.
How to stop it recurring
Request every permission your features need in the manifest up front, and keep a matrix of operation-to-scope support so code paths cannot call channel-only APIs from chats. Wrap update/delete flows with an ownership check (only touch activities your bot sent, tracked by cached activity IDs). When a feature depends on moderation-compatible posting, document that requirement for the installing admin.
Official reference: Microsoft Learn - Status codes from bot conversational APIs. See all Teams error codes or the Teams limits and quotas.
Related codes
- 403 BotDisabledByAdmin: BotDisabledByAdmin - blocked by tenant adminThe tenant admin disabled this agent
- 403 BotNotInConversationRoster: BotNotInConversationRoster - bot removed from conversationThe agent isn't part of the conversation roster.
- 405 Method Not Allowed: 405 - operation not supported by the channelThe channel doesn't support the requested operation.
- 404 ActivityNotFoundInConversation: ActivityNotFoundInConversation - message missing or deletedConversation not found.
Error 403 NotEnoughPermissions - quick answers
What does Teams error 403 NotEnoughPermissions mean?
The bot authenticated correctly and the conversation exists, but the specific operation you attempted is above the bot's station.
How do I fix Teams error 403 NotEnoughPermissions?
1. Read the scenario-specific message in the response body; it names the missing permission or restriction. 2. For moderated channels, ask the team owner to adjust moderation settings or stop targeting that channel. 3. For RSC-gated operations, add the required permission under webApplicationInfo/authorization in the app manifest and reinstall the app. 4. Rerun the operation in the scope it is documented to support.
Stop debugging Teams by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.