Microsoft Teams bot stops receiving events after updating app manifest with tab support until the app is reinstalled

Question

Microsoft Teams bot stops receiving events after updating app manifest with tab support until the app is reinstalled

Akshay Babar 45

We have an existing Microsoft Teams bot application that is already installed in a Teams channel (team scope) and is working correctly.

Recently, we added tab support to the existing bot by updating the Teams app manifest and increasing the manifest version. The updated app package was uploaded to the Microsoft Teams Admin Center.

After updating the app package:

The existing bot installation in the Teams channel stopped sending events to the bot endpoint.

The bot does not receive conversation events or messages.

When we manually remove and reinstall the app in the channel, the bot starts working again and events are received normally.

We want to understand why updating the app manifest causes the existing bot installation to stop sending events and why reinstallation is required.

Environment

Platform: Microsoft Teams
Bot Framework
App distributed via Teams Admin Center
App type: Teams Bot with Tab support
Hosting: Azure (Bot Service / API endpoint)

Steps to Reproduce:

Install the Teams bot in a Teams channel.
Verify that the bot receives events normally.
Update the Teams app manifest by adding configurable tab support.
Increase the app version and upload the new package in Teams Admin Center.
Observe that the existing bot installation stops receiving events.
Remove and reinstall the app in the channel.
After reinstalling, the bot starts receiving events again.

Could you please confirm whether this behavior is expected when updating the Teams app manifest with additional capabilities?

Also, please provide a response as soon as possible, as this issue is currently impacting our testing and deployment process.

Below is our manifest. Json

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.22/MicrosoftTeams.schema.json",
  "manifestVersion": "1.22",
  "version": "1.11.6",
  "id": "<APP_ID>",
  "developer": {
    "name": "<COMPANY_NAME>",
    "websiteUrl": "<COMPANY_WEBSITE>",
    "privacyUrl": "<PRIVACY_POLICY_URL>",
    "termsOfUseUrl": "<TERMS_URL>"
  },
  "name": {
    "short": "<NAME>",
    "full": "<NAME>"
  },
  "description": {
    "short": "<DESCRIPION>",
    "full": "<DESCRIPION>"
  },
  "icons": {
    "outline": "outline.png",
    "color": "color.png"
  },
  "accentColor": "#661DC2",
  "configurableTabs": [
    {
      "configurationUrl": "https://<TAB_DOMAIN>/?env=prod",
      "canUpdateConfiguration": true,
      "scopes": [
        "team"
      ],
      "context": [
        "channelTab"
      ]
    }
  ],
  "staticTabs": [],
  "bots": [
    {
      "botId": "<BOT_APP_ID>",
      "isNotificationOnly": false,
      "supportsFiles": false,
      "scopes": [
        "personal",
        "team",
        "groupChat"
      ],
      "commandLists": [
        {
          "scopes": [
            "personal",
            "team",
            "groupChat"
          ],
          "commands": [
            {
              "title": "loops",
              "description": "Invoke workflow/actions"
            },
            {
              "title": "ask",
              "description": "Ask bot questions"
            }
          ]
        }
      ]
    }
  ],
  "composeExtensions": [],
  "permissions": [
    "identity",
    "messageTeamMembers"
  ],
  "validDomains": [
    "token.botframework.com",
    "<BOT_SERVICE_DOMAIN>",
    "<TAB_DOMAIN>"
  ],
  "webApplicationInfo": {
    "id": "<BOT_APP_ID>",
    "resource": "api://<BOT_APP_ID>"
  },
  "authorization": {
    "permissions": {
      "resourceSpecific": [
        {
          "name": "ChannelMessage.Read.Group",
          "type": "Application"
        },
        {
          "name": "Member.Read.Group",
          "type": "Application"
        },
        {
          "name": "Team.Read.Group",
          "type": "Application"
        },
        {
          "name": "TeamsActivity.Send.Group",
          "type": "Application"
        },
        {
          "name": "TeamsTab.Create.Group",
          "type": "Application"
        },
        {
          "name": "TeamsTab.Read.Group",
          "type": "Application"
        },
        {
          "name": "TeamsTab.ReadWrite.Group",
          "type": "Application"
        }
      ]
    }
  }
}

Karnam Venkata Rajeswari 2,795 Reputation points Microsoft External Staff Moderator

2026-03-19T14:19:36.8966667+00:00

Hello Akshay Babar,

Glad to hear it’s working now! Thanks for confirming the solution.

Since I’ve converted my earlier comment into an answer, could you please take a moment to mark it as Accepted? This helps others in the community with the same question find the solution more easily.

Thank you!

2 answers

Your answer

Karnam Venkata Rajeswari 2,795 Reputation points Microsoft External Staff Moderator

2026-03-19T14:19:36.8966667+00:00

Hello Akshay Babar,

Glad to hear it’s working now! Thanks for confirming the solution.

Since I’ve converted my earlier comment into an answer, could you please take a moment to mark it as Accepted? This helps others in the community with the same question find the solution more easily.

Thank you!

Answer 1

Hello Akshay Babar,

Welcome to Microsoft Q&A .Thank you for reaching out.

Adding on to the inputs given by Kudos-Ng and Sayali-MSFT , please check if the following suggestion helps.

The observed behavior is caused by an invalid webApplicationInfo.resource configuration after adding Tab capability. For apps that include both a bot and a tab, Teams requires the Application ID URI to include a fully qualified domain name. When this requirement is not met, Teams initially grants permissions during installation but later revokes app‑level RSC permissions during background security synchronization, causing the bot to receive only @mention events.

As asked , this behavior is expected and can occur when a Teams app is updated to add tab capability without aligning the SSO configuration (webApplicationInfo). It is a known pattern related to how Teams revalidates permissions and authentication after such updates.

Please note that the existing installations are not always automatically upgraded to reflect new permission scopes, which is why reinstall temporarily resolves the issue.

After Tab support was added

The app became a Bot + Tab app.
Teams now treats webApplicationInfo.resource as the SSO authority for the tab.
For Tab SSO, Microsoft requires a fully qualified domain name (FQDN) in the Application ID URI.

Internally on reinstall, Teams temporarily grants RSC permissions. During the background security and token sync (24–48 hours),teams detects that webApplicationInfo.resource is invalid for Tab SSO and the platform revokes app‑level RSC permissions. Because of this the bot is no longer receives all channel messages and falls back to default behaviour

Please check if updating the Azure AD Application ID URI and manifest to use

api://<domain>/<app-id>

followed by a clean redeployment resolves the issue permanently.

To fix Azure AD (Entra ID) App Registration , please navigate to Azure AD → App Registration → Expose an API.Then set Application ID URI to

api://<your-domain>/<BOT_APP_ID>

Then update webApplicationInfo exactly to match the App ID URI as following –

"webApplicationInfo": {
  "id": "<BOT_APP_ID>",
  "resource": "api://<your-domain>/<BOT_APP_ID>"
}

Please consider redeploying to remove the app from Teams Admin Center Then please wait for tenant sync (background propagation) .Upload the corrected app package to reinstall the app into the team If prompted re‑grant consent.

References:

Thank you!

Answer 2

Kudos-Ng 15,050 Microsoft External Staff Moderator

Hi Akshay Babar,

Thank you for posting your question in the Microsoft Q&A forum.

After reviewing the official Teams developer documentation and similar community reports regarding manifest updates, it appears that this behavior is expected by design in Microsoft Teams.

While it can certainly be confusing the first time you encounter it, it perfectly aligns with how Teams handles Capability Updates and Re-consent flows for apps.

When you incremented the manifest version and added a new capability (the configurableTabs array), the existing app installation in the Teams channel entered a "Pending Update" state.

According to Microsoft's app update and permission framework, adding a Tab constitutes a change in app capabilities. Because your new tab requests specific contexts (like channelTab), Teams' security boundaries require strict consent. Therefore, Teams pauses routing conversation events to your bot endpoint to prevent state mismatches until the new manifest is explicitly accepted and "Re-consented" within that specific channel.

When you remove and reinstall the app, you bypass the "update" flow entirely. A fresh installation triggers a new installationUpdate event to your bot and forces the user to consent to the entire manifest (Bot + Tab) upfront, putting the app directly into a fully "Active" state where event routing resumes immediately.

Once you upload the new package to the Teams Admin Center, go to the Teams Channel where the bot is installed. Users (or Team Owners) should see an "Update" button/prompt next to the app in the Manage Team > Apps list. Clicking "Update" manually triggers the re-consent flow for the new Tab capability, and the Bot will legally resume receiving events.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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.

Akshay Babar 45 Reputation points

2026-03-06T18:00:41.6833333+00:00

Thanks for your response.
After uploading a new package version for the existing app in the Teams Admin Center, how long does it usually take for users to see the Update option in Teams? On our side, we uploaded the updated package but we are not seeing the Update option yet. Does it usually take some time for the update to propagate to users?
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-09T08:27:02.3133333+00:00
Hi Akshay Babar,

Thanks for follow up question.

As far as I know, app updates uploaded to the Teams Admin Center (TAC) typically take up to 24 hours to propagate across all users in a tenant.

Teams clients periodically poll the manifest store in the background. It usually waits for the application to be idle for a period or for a fresh session before staging and applying the update.

If the "Update" button hasn't appeared even after 24 hours, here are some ways to troubleshoot:

Verify Manifest Versioning: Ensure you have definitely incremented the version property in your manifest.json. Without a higher version number, the platform will not recognize it as an update.

Sign Out and Sign In: Signing back in forces the Teams client to re-authenticate and fetch the latest app policies and manifest data for your specific user account.

Clear Teams Cache.

Test in Teams Web Client: The web client usually reflects changes faster because it doesn't rely as heavily on local file-system caching as the desktop app.

I hope this helps.
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-10T09:27:18.89+00:00

Hi Akshay Babar,

Just checking in to see if you had a chance to review the previous response.

Your feedback would be very helpful in ensuring everything is on track.
Sayali-MSFT 5,686 Reputation points Microsoft External Staff Moderator

2026-03-12T05:48:29.2666667+00:00

Hello **Akshay Babar,
**Could you please confirm if your issue has resolved with provided suggestions or still looking for any help?
Akshay Babar 45 Reputation points

2026-03-12T11:55:39.9+00:00

Hi, I followed the approach given above, but I don’t see the Update button when I upload a new package in the Admin Center.

I uninstalled the app from the specific team and installed it again. After this, I started receiving events on our backend server. But, after 1–2 days it stopped, and now it only sends events when I mention the bot in the channel.

Earlier, I was receiving events for every message as per the above-mentioned manifest. Could you please help me with this
Akshay Babar 45 Reputation points

2026-03-12T12:05:31.33+00:00

Do we need to completely uninstall it through the Admin Center and then install it again?
Akshay Babar 45 Reputation points

2026-03-13T09:02:08.19+00:00

Hi, can you please help me as soon as possible. It's urgent from our side.
Sayali-MSFT 5,686 Reputation points Microsoft External Staff Moderator

2026-03-13T09:55:36.71+00:00

Hello Akshay Babar,
If you have any business-critical issue which need immediate attention, please raise a support request here:

[https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide&tabs=online](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Fget-help-support%3Fview%3Do365-worldwide%26tabs%3Donline&data=05%7C02%7Cv-sadange%40microsoft.com%7Ce6409d6fb19e404cb9a008dd0273146b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638669415623449723%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Icw%2FWY7zRdS8VFFvOIHFSzsbSPGZz9g1lc8hK3nmgwM%3D&reserved=0"Original URL: https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide&tabs=online. Click or tap if you trust this link.")
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-13T12:15:42.81+00:00
Hi Akshay Babar,

Looking closely at the manifest snippet you provided again, I noticed your webApplicationInfo configuration:

"webApplicationInfo": { "id": "<BOT_APP_ID>", "resource": "api://<BOT_APP_ID>" }

This is potentially the cause of your bot losing permissions after 1-2 days.

While "api://<BOT_APP_ID>" is totally acceptable for a Bot-only app (as the field doesn't do much for Bot RSC), the rules change completely the moment you add a Tab to your manifest.

When you introduce a Tab, Teams expects this resource string to be used for Tab Single Sign-On (SSO) token exchange. For Tab SSO, Microsoft documentation strictly requires this string to include your Fully Qualified Domain Name (FQDN).

It must follow this format: api://<Fully_Qualified_Domain_Name>/<BOT_APP_ID> (For example: api://bot.mydomain.com/1234abcd-1234-5678...)

Because your string is missing the domain, the initial installation forces a manual consent screen that temporarily grants your Bot the ChannelMessage.Read.Group permission. However, 24-48 hours later, when Microsoft 365 runs its routine background token and security sync, it detects the malformed webApplicationInfo configuration tied to your new Tab capabilities. To protect the tenant from misconfigured apps, it revokes the persistent App-level RSC scopes, dropping your bot back to basic @mention functionality.

You must update your Azure AD App Registration's "Application ID URI" to include your actual domain name, and then update this exact resource string in your manifest.json to match it perfectly. After you do this, completely remove the app from the Admin Center, wait an hour, and reinstall it.

If you have updated according to this final suggestion and the issue still persists, you can consider raising a support ticket either on the admin center as Sayali mentioned or on the Azure portal instead.

Reference: Get All Channel and Chat Messages for Bot and Agents - Teams | Microsoft Learn
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-16T08:38:41.7366667+00:00

Hi Akshay Babar,

I hope you're doing well. Just wanted to follow up and see if there's been any progress on the issue we discussed.

Let me know if there's anything I can assist you with further.
Akshay Babar 45 Reputation points

2026-03-19T13:01:32.8966667+00:00

After completely removing the existing app from the admin center and reinstalling it, the issue was resolved without any changes.

Is this expected?
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-19T13:37:24.0066667+00:00

Hi Akshay Babar,

I'm glad to hear the events are flowing again. And to answer your question: As far as I know, this behavior is expected.

It turns out the core roadblock all along was how Microsoft Teams handles App Manifest Updates, rather than the exact resource string itself.

Here is potentially what was happening behind the scenes:

When you originally tried to just update the existing manifest version to add a new Tab, Teams placed the app into a "Pending Update" state. Whenever new capabilities (like a Tab) are added to a manifest, Teams intentionally halts conversation events to the bot until a Team Owner explicitly clicks "Update" in the channel to grant re-consent for those new permissions. Because that button never appeared or wasn't clicked, your bot was stuck in limbo.

By completely uninstalling the app from the Admin Center and doing a fresh install, you entirely bypassed the "Update" workflow. A fresh installation forces a brand-new consent dialog for the entire package (Bot + Tab) right at the beginning.

Because the app entered the channel with full upfront consent rather than waiting for an update approval, Teams instantly registered it in an "Active" state and resumed routing events to your backend server immediately.

Since the bot has now remained stable for several days without dropping permissions, your configuration is solid. If you ever update the manifest with new capabilities again in the future, you can expect the same "Update" permission flow to occur.
Akshay Babar 45 Reputation points

2026-03-19T13:42:13.3+00:00

Thank you for clearing my doubts.
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-19T14:12:30.5166667+00:00

Hi Akshay Babar,

Thank you for your kind response.

I’m very glad that I could support you and help clarify your questions regarding the unusual behaviors encountered during the development and operation of your custom app.

Wishing you a wonderful day ahead.

Share via

Microsoft Teams bot stops receiving events after updating app manifest with tab support until the app is reinstalled

2 answers

Your answer