Skip to content

Commit b15e5b0

Browse files
committed
edit
1 parent e04626a commit b15e5b0

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/reliability/reliability-bot.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,12 +36,10 @@ For regional bots, Azure Bot Service supports zone redundancy by default. You d
3636

3737
During a zone-wide outage, the customer should expect a brief degradation of performance, until the service's self-healing re-balances underlying capacity to adjust to healthy zones. This is not dependent on zone restoration; it is expected that the Microsoft-managed service self-healing state will compensate for a lost zone, leveraging capacity from other zones.
3838

39-
4039
### Cross-region disaster recovery in multi-region geography
4140

4241
Azure Bot Service runs in active-active mode for both global and regional services. When an outage occurs, you don't need to detect errors or manage the service. Azure Bot Service automatically performs auto-failover and auto recovery in a multi-region geographical architecture. For the EU bot regional service, Azure Bot Service provides two full regions inside Europe with active/active replication to ensure redundancy. For the global bot service, all available regions/geographies can be served as the global footprint.
4342

44-
4543
## Next steps
4644

4745
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)