So, can you check whether you have any failed deployments by selecting the link next to deployments in your resource group? If that is the case, the next best step would be to redeploy, but to make sure you fill in the correct values in the custom deployment section.Įnsure that the bot ID matches the application ID from the app registration, and the password matches the bot secret manually created. Which means that the endpoint is available for sending messages. If you have a successful deployment and navigate to the app domain, it will throw a message like this: This could be due to an incorrect or failed deployment. It seems that the app domain is not receiving any messages, it is not available and so that is why it is throwing a 404 error, saying that the app domain is not available. Please let me know if you need additional information
#Microsoft teams app not working registration#
I checked and it is set to "app registration to accounts in any organization. "full": "Icebreaker is a cute little bot that randomly pairs team members up every week to help the team build trust and personal connections." "short": "Icebreaker is a bot that randomly pairs team members up to build team unity.", Also check if you have set the app registration to accounts in any organization. Could you please send a screenshot of your manifest file that was used to upload the icebreaker bot to teams? This way we can double check if you have the correct values there, such as the correct bot ID and the correct app domain values.
0 kommentar(er)
