Moving a bot from Draft to Production

You might want to consider a slightly different approach. Not sure changing the Scenario IDs is your best route. You might want to consider setting up a separate Free Health Bot instance to do your development work in which would allow you to keep the same Scenario ID in your development environment. When you are ready to promote your code, you could export the scenario and import it into the production environment. By doing this, you would not break any active connections to the bot and new bot connections would be based on the new code. Although dated, here is a post that talks about one method to manage code across multiple environments. https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/health-bot-instance-management-and-version-control-best/ba-p/1240487