matnav
commented
4 years ago This is apparently a known issue with manage multiple organizations with our Office 365 portal.
Resolved by checking the option in the App Registration "Accounts in any organizational directory (Any Azure AD directory - Multitenant)"
After multiple clean attempts to deploy PoshBot, I've come to the conclusion that something is wrong with the build or the documentation is out of date. I've followed everything outlined in https://poshbot.readthedocs.io/en/latest/guides/backends/setup-teams-backend/ to the T multiple times now. In total, I'm up to 3 times from scratch using unique names each time, and fresh App Manifest.
Expected Behavior
PoshBot is expected to run after execution of Start-PoshBot
Current Behavior
Currently when I attempt to start the PoshBot I get error messages
Steps to Reproduce (for bugs)
I followed the steps exactly as outline in Wiki
Your Environment
Module version used: 0.12.0
Operating System and PowerShell version: OS: Win10 1903 PS: 5.1.18362.145
Notable Errors:
"DataTime":"2020-04-23 05:26:52Z","Class":"Bot","Method":"Start","Severity":"Error","LogLevel":"Info","Message":"The remote server returned an error: (400) Bad Request.","Data":{"CommandName":"Invoke-RestMethod","Message":"The remote server returned an error: (400) Bad R equest."