@David Romero Thanks for the question. We would recommend to raise a Azure support desk ticket from Help+Support blade from Azure portal for your resource if you have a support plan for your subscription. This will help you to share the details securely and work with an engineer who can provide more insights about the issue that if it can be replicated.
Potential App Registration Migration and Bot Installation Implications
Recently we got a requirement to move our app registrations out of the Microsoft tenant into the AME one. This in turn means we’ll potentially need to create a new Bot Service resource in Azure and in turn update the bot manifest with the new MicrosoftAppId. Will our users have to re-install our bot or can they simply just go on using the bot as they were before? I'm looking into whether it'd be possible to get some sort of exemption for us.
In addition, our bot currently has the Group.Read.All permission enabled to support some business requirements that allow support engineers to meet certain SLAs. Would creating a new registration in the AME tenant allow us to continue reading messages in a conversation even when a bot isn't engaged from users that have an @microsoft account?
Thank you