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.