Microsoft Bot框架中的BotdisabledByAdmin错误
我们的客户将应用程序上传为具有机器人的自定义Microsoft Teams应用程序，并将其安装到团队中。从那时起，我们通过机器人直接在其Microsoft Teams应用程序上向用户发送通知。
很长一段时间以来一直有效。最近，当我们尝试向其中一个租户中的用户发布消息时，我们开始恢复BotdisabledByAdmin的响应。
我们意识到房客的管理员具有阻止自定义应用程序的设置策略。这使我们甚至可以卸载并将应用程序重新安装到租户中的任何团队中。
注意到这一点后，管理员已更改了策略以允许所有自定义应用程序。我们不得不等待3天才能生效，此后，我们能够卸载并重新安装该应用程序。
尽管我们能够使用Botframework API搜索用户以查找其ID等，但我们无法向任何用户发布消息。我们仍在收到botdisabledbyadmin错误。
我正在附上Microsoft Teams Admin Portal下的房客中设定的所有策略。在全球策略下使用的黑色应用程序是我们的应用程序。
是否还有其他政策，设置或限制我们可以仔细检查以解决此问题？
Our customers upload our app as a custom Microsoft Teams app that has a bot and install it into a Team. From then on, we send notifications to users directly on their Microsoft Teams app via the bot.
This has been working fine for a long time. Recently, we started getting back BotDisabledByAdmin response when we try to post messages to the users in one of the tenants.
We realised that the Tenant’s admin has setup policies to block custom apps. This prevented us to even uninstall and reinstall the app into any Team in the Tenant.
After noticing that, the Admin has changed the policies to allow all custom apps. We had to wait 3 days for the changes to take effect and after that, we were able to uninstall and reinstall the app freshly.
Although we are able to use Botframework APIs to search users to find their ID etc., we are unable to post messages to any of the users. We are still receiving BotDisabledByAdmin error.
I’m attaching all the policies that are set in the Tenant under Microsoft Teams admin portal. The blacked out app under Global policy is our app.
Are there any other policies, settings or restrictions that we could double check to resolve this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这些权限政策是越来越多的地狱，并停止每天可靠地工作。我经常看到给用户发送消息失败的尝试，然后工作，然后在一个小时内再次失败，而没有任何更改。然后突然一次会好几个月了。
您永远无法排除这不是微软的一部分瞬时中断，也不是在团队后端复制不完全复制的东西。
These permissions policies are buggy as all hell, and stop working reliably day-to-day. Frequently I've seen attempts to message users fail, then work, and then fail again within the space of an hour, with no changes made whatsoever. Then suddenly it'll be fine for months at a time.
You can never rule out that it's not some transient outage on Microsoft's part, or stuff clunking around replicating incompletely in the Teams back-end.