Log Analytics now supports workspace replication, a new capability that enhances resilience to regional incidents. When replication is enabled, a copy of your workspace is created on another region. From that moment on, new logs ingested to your primary workspace are also replicated to the secondary (existing logs are not copied over). Your secondary workspace can’t be directly managed or accessed, and only serves to create an active-passive setup: at any given time, your workspace has one active instance, and an inactive instance that is updated in the background.
If an outage impacts your primary workspace, you can switch to your secondary workspace by triggering failover. This operation reroutes all ingestion and query requests to your secondary workspace, so you can continue monitoring your resources and apps as needed. Your secondary workspace stores a copy of all logs ingested since you enabled replication, so you can switch over smoothly and continue using alerts, workbooks and even other services that access your logs, such as Sentinel. During that period, your secondary region also replicates incoming logs back to the primary workspace, so when your primary region is healthy again you can switch back to it and continue working as usual.
Workspace replication is billed per replicated GB. You can apply replication to a subset of your Data Collection Rules (DCRs) to limit the replication scope, and related costs. See the Azure Monitor pricing page for full pricing information.
To learn more, see the Workspace Replication documentation.
