Microsoft Teams troubleshooting

Use this page when you cannot create a Teams workflow, AppReviewBot rejects the webhook URL, or reviews do not arrive in the expected channel.

Workflows is missing from Teams

Select View more apps (···) in the Teams sidebar and search for Workflows. If it is not available, your organization's Teams administrator may have disabled the app or restricted workflow creation. Ask them to enable Workflows for your account and team. Microsoft also documents that Workflows is unavailable in Microsoft 365 Government tenants.

See Microsoft's guide to getting started with Workflows.

The webhook template is missing

Open the Workflows app and search its home or templates page for Send webhook alerts to a channel. If the template does not appear, check with your administrator whether Power Automate workflows or webhook triggers are restricted in your organization.

AppReviewBot says the webhook URL is invalid

• Copy the complete URL from the workflow details page, including its query string. Do not remove or edit any part of it.
• Use the HTTPS URL generated by the Teams Workflows template. Current workflow URLs can use hosts ending in .logic.azure.com or .environment.api.powerplatform.com.
• Create a new workflow URL if the original was revoked, regenerated, or exposed. Treat the URL like a password because it allows its holder to send messages to the configured channel.

For Microsoft's current steps, see Send messages in Teams using incoming webhooks.

The destination was not created or selected

For quick setup, submit the Teams page after entering your email and webhook URL, then follow the success message. For dashboard setup, save the Teams destination in the destination window, return to the Create App flow, and select that destination before finishing the app subscription. See quick setup or dashboard setup.

The workflow is saved but reviews do not appear

1. Confirm the workflow is enabled and points to the intended team and channel.
2. In AppReviewBot, confirm the app subscription is active and uses that Teams destination.
3. Check the subscription's rating and country filters; a review outside those filters will not be sent.
4. Verify that the workflow owner still has access to the channel and its required Microsoft connections.

Reviews are sent when AppReviewBot fetches matching reviews. A newly saved workflow does not backfill older reviews.

Messages still use an old connector

Microsoft is retiring legacy Office 365 Incoming Webhook connectors. If your saved URL contains webhook.office.com, replace it with a Workflows webhook. AppReviewBot still accepts connector URLs and sends them a legacy message card, but they may stop working at any time.

Replacing a retired connector URL

1. Create a Workflows webhook for the channel by following quick setup and copy its URL.
2. In AppReviewBot, open Destinations and edit the existing Microsoft Teams destination.
3. Paste the new URL in place of the old one, then save. Use the test option if it is available to confirm a message arrives in the channel.
4. Optionally remove the old Incoming Webhook connector from the channel in Teams.

Messages are posted by "Workflows", not AppReviewBot

Workflows webhooks post as the workflow owner or the Workflows bot, so the sender is not shown as "AppReviewBot". This is a Microsoft limitation and the sender name cannot be changed. The message content is unchanged.

Still stuck? Contact AppReviewBot support.