Troubleshooting - OfficeDev/microsoft-teams-apps-incidentreport GitHub Wiki

Generic possible issues

There are certain issues that can arise that are common to many of the app templates. Please check here for reference to these.

Problems deploying to Azure

1. Error when attempting to reuse a Microsoft Azure AD application ID for the bot registration

Description

Bot is not valid.

Errors: MsaAppId is already in use.
  • Creating the resource of type Microsoft.BotService/botServices failed with status "BadRequest"

This happens when the Microsoft Azure application ID entered during the setup of the deployment has already been used and registered for a bot.

Fix

Either register a new Microsoft Azure AD application or delete the bot registration that is currently using the attempted Microsoft Azure application ID.

2. Error while deploying the ARM Template

Description

This may happen because the two app services are sharing same set of physical code base. It happens because of conflict of process allocation of app service since they are trying to access same physical files, as a result both app service deployment fails for the first time when deployed from ARM template.

Error: The resource operation completed with terminal provisioning state 'Failed' or 'Conflict'

Fix

In case of such a scenario, user needs to navigate to deployment center section of failed/conflict resources and needs to redeploy each app one by one. By re-deploying one app service at a time the issue/conflict will get resolved.

Steps to re-deploy the app services:

  1. Navigate to the failed app service from ARM deployment page.
  2. Select "Deployment Center" in the left side navigation pane.
  3. Click on "Logs"
  4. Click on "Redeploy".It might take some time to reflect the status to deployment successful.

Problems related to Messaging Extension

1. SMEuser not receiving the ticket details

Description

This happens when the messages are not received by the SME team.

Fix

Make sure to enter correct team id.

Steps to get team Id:

  1. Select "More options" from General channel of the team to be selected as SME team.
  2. Select "Get link to channel".
  3. Add the mentioned link in the Team-id field in the arm template.

Didn't find your problem here?

Repeat the above steps for the second app service also.

Please, report the issue here