I have a custom Teams app with a custom bot that is distributed in our organization through an organization-wide manifest import (not published in the public store).

The bot is used only for notifications and was working in production except that the original messaging endpoint URL was incorrect at the time we rolled out the app org-wide.

After discovering this, i corrected the bot’s messaging endpoint.

• New users (who install the app now) correctly trigger the bot’s onMembersAdded event and receive the welcome message.

• Existing users (who already had the app installed when the endpoint was wrong) do not trigger any activity or event in the bot after the fix, and therefore never receive the welcome/notification messages.

Our bot is hosted on Firebase Functions and stores user conversation references in Azure Blob Storage when a member is added (onMembersAdded event). Because the bot’s messaging endpoint was incorrect during the initial rollout, that event never triggered for existing users. As a result, only new users (added after the endpoint fix) are being recorded in Blob Storage, while earlier users are missing from it.

We cannot ask users across all tenants/companies to manually uninstall and reinstall the app.