MS Teams Connection

Hi, I'm trying to implement a Bot into Teams using the instruction from github. I can't get it to work, as I always get a 400 Error with the message "The bot's Microsoft App ID or Microsoft App Password is incorrect". I checked it multiple times and I don't see a mistake from my side. Anyone else with the same issues and is there a solution for it?

Thanks

SSirBastion Hi, I'm trying to implement a Bot into Teams using the instruction from github. ...

Tico | Voiceflow Assistant•5/13/24, 5:35 PM

The error message you're receiving, "The bot's Microsoft App ID or Microsoft App Password is incorrect", typically indicates that there's an issue with the credentials you're using to authenticate your bot with Microsoft Teams. Here are a few steps you can take to troubleshoot this issue:

Double-check your Microsoft App ID and Password: Ensure that you have correctly copied the Microsoft App ID and Password from the Microsoft Azure portal into your bot's configuration. Make sure there are no extra spaces or characters.
Ensure your bot is correctly registered: Your bot needs to be registered with the Microsoft Bot Framework. You can do this through the Azure portal. Make sure the Microsoft App ID and Password you're using correspond to this registered bot.
Check your bot's configuration in Microsoft Teams: In Microsoft Teams, ensure that the bot's configuration is correct. This includes the bot's App ID, which should match the Microsoft App ID you're using.
Inspect your code: There might be an issue with how your bot's code is using the Microsoft App ID and Password. Ensure that these values are being correctly passed into the Microsoft Teams Bot Builder SDK.
Try regenerating your Microsoft App Password: In some cases, there might be an issue with the Microsoft App Password. You can try regenerating this password in the Azure portal and updating your bot's configuration with this new password.

Remember, when you make changes to your bot's configuration or code, you'll likely need to restart your bot for these changes to take effect. If you've tried these steps and are still encountering issues, it might be helpful to look at the specific code or configuration causing the error. This could involve adding logging to your bot's code to help identify where the issue is occurring.

unique-blue•5/20/24, 7:25 PM

@SirBastion did you manage to make it work?

dead-brownOP•5/22/24, 6:48 PM

@Omar Sadly not, still doesn't work. Do you have the same issue?