When I install my Teams app to a team, no webhook is fired to my messaging endpoint

Question

When I install my Teams app to a team, no webhook is fired to my messaging endpoint

Ryan Jones 0

I have developed a bot that is on the Microsoft App store, need to deploy very similar ones for particular customers with a different endpoint.

Steps to reproduce:

Create an Azure bot (single tenant)
Add a messaging endpoint
Add Microsoft Teams as a channel
Create an App Registration (single tenant)
create a teams app with manifest templated as below
Install the Teams app to the same tenant as the resources created above. Success shown
Add the app to a team from admin.teams.microsoft.com. It says that it was added to the team
No webhook is fired to my endpoint of the installation

Troubleshooting steps attempted

Have verified from the Azure bot page if I use the test webchat my endpoint is hit and accessible (I am not interested in the chat feature -- I need to know if a user or team installs my app)
Have verified my tenant allows custom apps
Have verified permission policies do not restrict custom apps, including my app
Have verified that the app is not blocked, is available to all
All of the Teams/users I try to install it to do not have anything unique about them -- they can be brand new teams that are public, etc.
Have attempted similar steps with the app registration as multi-tenant
Have confirmed that my app registrations have a client secret added
Have tried using the bot ID in the same place as the app-registration-id
Have tried creating the bot from dev.teams.microsoft.com and using it from there
Have tried creating a brand new tenant (different email, credit card, etc.) and going through the same steps My web application that should receive the webhook is not deployed on any Microsoft resource, it is a Rails application.
Have verified in the Teams app when I go to Manage Team and click on Apps my app is shown as installed.
Have added my messaging endpoint as a valid domain, which is also a verified domain for my tenant.

{
    "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.12/MicrosoftTeams.schema.json",
    "version": "3.0.0",
    "manifestVersion": "1.12",
    "id": "<PII removed>",
    "packageName": "com.package.name",
    "name": {
        "short": "May 26",
        "full": ""
    },
    "developer": {
        "name": "Example co",
        "mpnId": "my-mpn-id",
        "websiteUrl": "https://example.com",
        "privacyUrl": "https://example.com/policies/privacy",
        "termsOfUseUrl": "https://example.com/policies/terms"
    },
    "description": {
        "short": "short message",
        "full": "full message"
    },
    "icons": {
        "outline": "outline.png",
        "color": "color.png"
    },
    "accentColor": "#2151FF",
    "bots": [
        {
            "botId": "azure-bot-id",
            "scopes": [
                "personal",
                "team"
            ],
            "isNotificationOnly": true,
            "supportsCalling": false,
            "supportsVideo": false,
            "supportsFiles": false
        }
    ],
    "validDomains": [],
    "webApplicationInfo": {
        "id": "app-registration-id",
        "resource": "api://example.com/app-registration-id"
    },
    "devicePermissions": [
        "notifications"
    ],
    "authorization": {
        "permissions": {
            "orgWide": [],
            "resourceSpecific": [
                {
                    "name": "TeamMember.Read.Group",
                    "type": "Application"
                }
            ]
        }
    }
}

0 comments

2 answers

Your answer

Answer 1

Nivedipa-MSFT 4,246 Microsoft External Staff Moderator

Hello @Ryan Jones
The install webhook isn't firing because your manifest has "isNotificationOnly": true. Notification-only bots are outbound-only — Teams suppresses conversationUpdate (install/member-added) events for them, which is exactly the event you're waiting for.

Fix:

Set "isNotificationOnly": false (or remove the field) in the manifest, bump the version, and repackage.
Reinstall the app to a team from the Teams client as a team owner (not via Teams Admin Center — admin-pushed installs don't reliably fire the install activity).
Watch /api/messages for a conversationUpdate with membersAdded containing your bot ID.

If you still see nothing after that, check: (a) Azure Bot → Channels → Teams → Issues for delivery failures, and (b) that your Rails endpoint isn't 401-ing the JWT (single-tenant bots must validate against https://login.microsoftonline.com/{tenantId}/v2.0/.well-known/openid-configuration with audience = your bot's App ID).

If you found the information above helpful, I would appreciate it if you could share your feedback.
Your feedback is important to us. Please rate us: 🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor

Ryan Jones 0 Reputation points

2026-06-01T22:26:16.0566667+00:00

Hi @Nivedipa-MSFT I changed two things: what you suggested and set the value for isNotificationOnly to false. I also decided to try a different endpoint. Using the new endpoint seems to work and send the webhook; using the endpoint for staging I have been trying does not. Whether I use isNotificationOnly true or not does not make a difference. Also have not detected an issue with whether I upload it in the Admin center vs the Teams client app. But have tried both just to be sure.

I need to validate that I can use any endpoint as we want to implement this solution for customers with on-premise setups, so if it is limited to just our production instance, that is not a viable solution for us.

I changed my messaging endpoint from

app.MYCOMPANY-STAGING.com/microsoft/bot

to

app.MYCOMPANY.com/microsoft/bot

I am confident there is no firewall issue because the webchat messages get through to the staging environment fine as mentioned above.

Answer 2

Teddie-D 16,800 Microsoft External Staff Moderator

Hi @Ryan Jones

Thanks for the detailed information.

Based on your setup, the most likely explanation is related to the bot being configured as notification-only.

In your manifest: "isNotificationOnly": true

With a notification-only bot, Microsoft Teams treats the bot differently from a standard conversational bot. Users typically cannot @mention the bot in a channel or start a normal chat with it. The bot is designed primarily for proactive messaging. Because of that, Teams may show the app as installed in the team, but may not create a conversation context with the bot.

Reference: Notification-only bots - Teams | Microsoft Learn

If no conversation is created, Teams may not send lifecycle activities such as conversationUpdate to your messaging endpoint.

Reference: Conversation events - Teams | Microsoft Learn

So, the behavior you’re seeing, app appears successfully installed, but no webhook reaches your endpoint, is consistent with a notification-only bot configuration

Here are some recommended steps you may try:

1.Change the manifest from: "isNotificationOnly": true to: "isNotificationOnly": false

2.Repackage and upload the updated manifest.

3.Reinstall the app in Teams.

4.Once installed, trigger interaction:

@mention the bot in a channel or
open it directly and send a message.

This helps trigger Teams to add the bot to the team conversation and establish the conversation context.

5.Capture and log all incoming activity payloads at your endpoint, especially:

message
conversationUpdate

Please try these steps and let me know how it goes.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Teddie-D 16,800 Reputation points Microsoft External Staff Moderator

2026-05-28T00:09:37.1433333+00:00

Hi @Ryan Jones
Just checking in to see if the information above was useful to you. If you have any additional updates or need further assistance, don't hesitate to reach out. Warm thanks!
Ryan Jones 0 Reputation points

2026-06-01T21:16:30.49+00:00

Hey @Teddie-D thanks for following up.

I followed the prescribed steps. Right now I am finding that about 75% of the time that it works IFF I am using a particular hostname as my endpoint. I've made 4 separate Azure Bots doing this step using my production endpoint and using the same manifest template and changing out the bot ID and updating the UUID of the app.

When I do app.MYCOMPANYNAME.com/microsoft/bot as the endpoint, it has worked on 3 out of 4 of the Azure Bot Teams apps (that is the production endpoint). When I do app.MYCOMPANYNAME-STAGE.com/microsoft/bot as the endpoint it has yet to work. Both of those domains are verified for my tenant. I've also tried updating the messaging endpoint for my Azure Bot and that is not working either to get it to go from the prod one to staging. I know that Microsoft can hit my staging endpoint because I have seen traffic come in to my staging endpoint when I open the webchat test as mentioned above.
Ryan Jones 0 Reputation points

2026-06-01T22:27:09.5333333+00:00

As an additional follow up, I've been able to prove that even with isNotificationOnly as true and using the production URL I am getting the webhook; but doing it with staging in either state I am not getting the webhook.
Teddie-D 16,800 Reputation points Microsoft External Staff Moderator

2026-06-02T08:27:30.55+00:00
Hi @Ryan Jones

Please note that we're not Microsoft support, this is a user-to-user support forum. Moderators here don’t have backend access to Microsoft systems, so we can only provide technical guidance based on the public resources.
In Microsoft Teams, messages are not sent directly to your endpoint. They are first processed by the Bot Framework service and then forwarded to your messaging endpoint. If anything in that flow fails validation, the request may never reach your service.

Based on the behavior you described, common causes in this type of scenario include:

Differences in TLS/SSL configuration between production and staging (for example certificate chain, trust, or hostname validation)

DNS or network resolution differences (public vs internal routing, IPv4/IPv6 behavior, etc.)

Endpoint response behavior

Channel-level validation or caching when switching the messaging endpoint

One important point is that Teams channel validation is stricter than Web Chat, so it is possible for Web Chat to work while Teams traffic is blocked before it reaches your endpoint.

Recommended checks:

-Verify your staging endpoint SSL certificate:

full chain (including intermediates)

trusted public CA

hostname matches exactly

-Compare production vs staging:

TLS versions supported

response time and status codes

-Capture network logs on staging to confirm whether any requests from Bot Framework reach your service

-If possible, create a new bot registration pointing only to staging, instead of switching endpoints on an existing bot.

Share via

When I install my Teams app to a team, no webhook is fired to my messaging endpoint

2 answers

Your answer