I want to post message on Teams when a new Task is created in Planner.
I am able to do that using a Flow, but the problem is, it posts as my own user.
For Teams action, I have two options:
The second option keeps throwing 404 error.
{ "error": { "code": "BotRequestFailed", "message": "Request to the Bot framework failed with error: '{\"error\":{\"code\":\"BadArgument\",\"message\":\"Unknown cloud 'in-client-ss.msg'\"}}'." } }
Solved! Go to Solution.
me too
Request to the Bot framework failed with error: '{"error":{"code":"BotDisabledByAdmin","message":"The tenant admin disabled this bot"}}'.
Same here, everythign worked last week.
{ "error": { "code": "BotRequestFailed", "message": "Request to the Bot framework failed with error: '{\"error\":{\"code\":\"BotDisabledByAdmin\",\"message\":\"The tenant admin disabled this bot\"}}'." } }
Same Here
Worked fine on Aug 31st but broken on Sept 1st with no chnages made
Forbidden. The request failed. Error code: 'BotRequestFailed'. Error Message: 'Request to the Bot framework failed with error: '{"error":{"code":"BotDisabledByAdmin","message":"The tenant admin disabled this bot"}}'.'.
Everything was working fine. No Changes made.
Today get the following error:
Any update on this? We facilitate some standup type of meetings with this specific setup and they've been failing since Friday.
We too are having the same issue. Starting Friday 8/30/19 to present.
Error:
Request to the Bot framework failed with error: '{"error":{"code":"BotDisabledByAdmin","message":"The tenant admin disabled this bot"}}'.
Teams developers are currently investigating the issue. I'll post back here when they have an update.
Teams has identified the issue and is working on a mitigation now.
According to their oncalls, the fix has mostly rolled out already, and should be done by this evening.
We monitored this overnight and the problem appears to have been fully resolved. Please let me know if anyone is still seeing this where you *really* don't expect it to be blocked by an admin.
Hi,
I've tried today to use the Post a message as the Flow bot to a channel action and I am getting the same error:
Request to the Bot framework failed with error: '{"error":{"code":"BotDisabledByAdmin","message":"The tenant admin disabled this bot"}}'.
Can you advise on what was done to rollout the fix?
@dblyth wrote:We monitored this overnight and the problem appears to have been fully resolved. Please let me know if anyone is still seeing this where you *really* don't expect it to be blocked by an admin.
I'm getting mixed results I have a flow with 5 different routes. all same bot it just works on of the scenarios.
The other scenarios they fail
Here is the Fail Message.
I have a Power Automate workflow with posting the result to Teams via a Bot and it worked perfectly until right now. I get the same error message like the others:
"body":{"error":{"code":"BotRequestFailed","message":"Request to the Bot framework failed with error: '{\"error\":{\"code\":\"BotDisabledByAdmin\",\"message\":\"The tenant admin disabled this bot\"}}'."}}
Teams app policies are described here, though access to the settings may require a tenant administrator:
https://docs.microsoft.com/en-us/MicrosoftTeams/teams-app-permission-policies
Why would this have to do anything with the App Permission Policies?
Thanks in advance.
Apps and bots are tied together on the Teams platform. So there's a teams app underlying the Flow bot that lets it post messages to users. If apps (or the Flow app) is blocked by policy, the Flow bot actions will fail with this error.
"Post Message" sends as yourself, and you have full flexibility with an HTML editor to post styled messages, and @ mention users with <at>user@contoso.com</at> syntax. You can also reply to messages with this action.
Posting as the Flow bot lets you send custom adaptive cards as the Flow bot identity. Adaptive cards can't currently @ mention users, though this is something we are working with Teams on.
I am getting the same error message today (27/04/2020), I have tested this on two separate tenants and get the same error message.
Did anyone ever figure out what this issue is?
Join digitally, March 2ā4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
User | Count |
---|---|
85 | |
57 | |
42 | |
38 | |
33 |
User | Count |
---|---|
91 | |
73 | |
72 | |
60 | |
40 |