You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking for troubleshooting resources for setting up the official Microsoft Teams / GitHub Integration for GHES (we are on 3.8 version of the server), as the bot seems to be active in our Teams instance, the bot is successfully deployed to Azure, and it is set up on the GitHub side as well. However, the bot will not respond to any messages from a Teams channel where it's installed on, or via a direct message to the bot within Teams.
Message sent within Teams (GHE Is the name of the integration, since this is different for the GHES custom app):
Looking for troubleshooting resources for setting up the official Microsoft Teams / GitHub Integration for GHES (we are on 3.8 version of the server), as the bot seems to be active in our Teams instance, the bot is successfully deployed to Azure, and it is set up on the GitHub side as well. However, the bot will not respond to any messages from a Teams channel where it's installed on, or via a direct message to the bot within Teams.
Message sent within Teams (GHE Is the name of the integration, since this is different for the GHES custom app):
Docs followed: https://github.com/integrations/microsoft-teams/blob/master/Readme.md#ghes-integration
I have completed these steps about 5 times now, just to ensure I wasn't messing up any of the IDs or Secrets.
The integration seems to have successfully integrated within our Github instance, as this website is available: https://our-ghe-instance-url/_msteams/
The Azure bot deployed without any failures or errors.
Sending a message via the direct line does seem to return a 200 OK, but not with a response I expected:
In addition, within Teams, the bot seems active:

Hoping I can get some direction on what I"m doing wrong, or any troubleshooting tips.
The text was updated successfully, but these errors were encountered: