Regionalization in Azure Bot Service

APPLIES TO: SDK v4

Azure Bot Service is a global Azure service that allows bot developers in all regions to register their bot and connect it to different channels. This also lets developers meet compliance obligations, especially following the Schrems II decision.

Use an Azure Bot resource to register a bot with regional Azure Bot services. Adding regional settings to a bot ensures user personal data is preserved, stored, and processed within certain geographic boundaries (like EU boundaries). This article explains the areas of bot development impacted by regionalization and where to update settings to maintain compliance.

Deploy locally developed regional Azure bots

Your bot can be hosted anywhere, even if you have a regional Azure Bot resource. To maintain complete end-to-end data residency, however, you should host your bot code in the same locality as your Azure Bot resource. For example, developers hosting bots in the European Union will want to ensure their bots are deployed in a region within EU geographical boundaries.

For more information about deploying regionalized bots, see Provision and publish a bot.

Register regional Azure bots

When you create a bot in Azure, you can set its region to maintain data compliance. When you create a bot, make sure to create your resource in a geographically compliant region. For more information, see Create an Azure Bot resource.

Note

Bot data may go beyond geographical boundaries as bot end-to-end scenarios may depend on many services. The regional Azure Bot service only supports data in Azure Bot services. Other Azure services—such as Azure Cognitive Services—and third-party channels may not align with compliance obligation and run the risk of data leaving the geographical region.

Add authentication to a regional Azure bot

Sometimes a bot must access secured online resources on behalf of the user. OAuth is used to authenticate the user and authorize the bot.