Availability and recovery of Security Copilot

This article describes the availability and recovery support in Microsoft Security Copilot experiences.

Availability zone support

Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. When a local zone fails, availability zones are designed so that if one zone is affected, regional services, capacity, and high availability are supported through the remaining two zones.

Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance for failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see Regions and availability zones.

Security Copilot makes commercially reasonable efforts to use zone-redundant availability resources; underlying resources automatically replicate across zones, without any need for you to set up or configure.

Note

Availability zones protect service uptime; they don’t determine where prompts are processed.

Availability zones

Availability zones are supported in various Geos as listed in the table:

Geo	Copilot Sessions
ANZ
Asia
Brazil
Canada
Europe
India	Not supported due to capacity constraints
Japan
Qatar
South Africa
Switzerland
UAE	Not supported due to capacity constraints
UK
US

Note

Processing location is unrelated to high availability location. It is determined dynamically per-user traffic.

Zonal outage recovery

During a zone-wide outage, no action is required during zone recovery. Copilots for Security capabilities in supported Geos self-heal and rebalance automatically to take advantage of the healthy zone. For more information, see What are Azure availability zones?.

Disaster recovery and business continuity

Disaster recovery (DR) is about recovering from high-impact events, such as natural disasters or failed deployments that result in downtime and data loss. Regardless of the cause, the best remedy for a disaster is a well-defined and tested DR plan and an application design that actively supports DR. Before you begin to think about creating your disaster recovery plan, see Recommendations for designing a disaster recovery strategy.

When it comes to DR, Microsoft uses the shared responsibility model. In a shared responsibility model, Microsoft ensures that the baseline infrastructure and platform services are available. At the same time, many Azure services don't automatically replicate data or fall back from a failed region to cross-replicate to another enabled region. There may be scenarios where a specific Geo does not support replication or services have system errors.

For Security Copilot, best effort is made to back up and restore your data if there is an outage. However, it's important to note that you should have a plan ready to deal with outages, even if it involves manual intervention. This means that you should have a disaster recovery plan in place that suits your workload.

Most services that run on Azure platform as a service (PaaS) offerings also provide features and guidance to support DR and you can use service-specific features to support fast recovery to help develop your DR plan.

Recovery time objective and Recovery point objective

The following table lists the supported geographies for Security Copilot. There is 72-hour Recovery Time Objective (RTO) and 15-minute Recovery Point Objective (RPO) commitment for regional outages within a geography. If a particular region experiences an outage, the RTO and RPO commitments are applied for that Geo.

Geo	Copilot Sessions
ANZ
Asia	Not replicated due to capacity constraints
Brazil	Not replicated due to capacity constraints
Canada
Europe
India	Not replicated due to capacity constraints
Japan
Qatar
South Africa	Not replicated due to capacity constraints
UAE
UK
US