Share via

Teams ParticipantJoinEvent only available for bot created in Teams Developer Portal

Eugene De Villiers 25 Reputation points
2024-06-03T23:25:41.6666667+00:00

Hi,

I have an existing bot with a set of features, and wanted to build further functionality when participants join or leave a meeting.

The OnTeamsMeetingParticipantsJoinAsync and OnTeamsMeetingParticipantsLeaveAsync are not raised for an Azure Bot.

I created a bot from the developer portal where the options are available, and that bot raises the events as expected. As per the Microsoft article here: https://learn.microsoft.com/en-us/microsoftteams/platform/apps-in-teams-meetings/meeting-apps-apis?branch=pr-en-us-8455&tabs=channel-meeting%2Cguest-user%2Cone-on-one-call%2Cdotnet%2Cparticipant-join-event%2Cparticipant-join-event1#receive-meeting-participant-events

The bot created in the teams developer portal is not available in Azure for any further configuration or setting features like SSO etc.

How would I configure my current Azure Bot to also raise these same participant events?

Or is there some other solution I should be pursuing?

Kind Regards,

Eugene

Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
2,974 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eugene De Villiers 25 Reputation points
    2024-06-07T19:30:46.6733333+00:00

    Update on issue:

    We have found a temporary workaround for this issue.

    If you create a bot in the development center and enable those events, they fire as mentioned. If from there you follow the link to the legacy Bot Framework Portal, at the top right corner there is a “Migrate” button, which migrates your bot to Azure Bot services. That new Azure bot services bot will continue to fire the events and work as expected. Comparing that bot settings and even manifest file to any other bot created, they are identical in configuration, yet other bot’s won’t fire those events.

    Internally there must be some settings that is NOT being exposed for engineers to setup.

    A further annoyance is that the migrated bots use the ApplicationId as their name and cannot be renamed, making a mess in our infrastructure and impossible to know at a glance what resource you are working with.

    Please advise on the plan to enable this feature or of any CLI tools to set this functionality.

    0 comments