Teams error 403 BotDisabledByAdmin: BotDisabledByAdmin - blocked by tenant admin

A Teams administrator has blocked the app, so the Connector refuses to deliver anything you send. The status table documents the code as BotDisabledByAdmin with the message "The tenant admin disabled this agent" (older doc versions phrase it as "bot") and the description "Admin blocked interactions between user and the agent app. Admin needs to allow the app for the user inside of app policies." The documented retry column is No, and the developer action is explicit: "Stop posting to conversation until interaction with agent is explicitly initiated by a user in the conversation indicating that the agent is no longer blocked."

Nothing is wrong with your credentials, your endpoint, or the conversation reference - this is pure tenant policy. In the Teams admin center an app can be blocked org-wide (Manage apps > Blocked) or removed from the app permission policy that applies to specific users, and either state produces this code. It is the counterpart to ConversationBlockedByUser: there a person blocked you, here an admin did, and only the admin can undo it. Custom apps face an additional gate - if the org's setup policies disallow custom app upload (sideloading), the app may never install in the first place, a scenario walked through in causes 5 and 6 of Teams bot not responding.

Handle it as a suppression signal, not a transient fault. Keeping a retry loop running against a policy block wastes your per-thread rate budget and fills logs with noise while changing nothing.

{
  "error": {
    "code": "BotDisabledByAdmin",
    "message": "The tenant admin disabled this agent"
  }
}

You cannot prevent an admin's decision, but you can make it less likely and cheap to survive: publish clear admin-facing documentation of what the bot sends and how often, respect notification frequency so the app never looks like spam, and build the suppression path into your sender from day one - a per-conversation kill switch that flips on 403 and off on the next inbound message. For proactive-heavy bots, reconcile suppressed conversations weekly rather than probing them continuously.