# CockroachDB Advanced on Azure

This page provides information about CockroachDB Advanced clusters on Microsoft Azure, including frequently asked questions and limitations. To create a cluster, refer to Create a CockroachDB Advanced Cluster.

To express interest or request more information about a given limitation, contact your Cockroach Labs account team.

CockroachDB Advanced clusters on Azure have the following temporary limitations. To express interest or request more information about a given limitation, contact your Cockroach Labs account team.

- A cluster must have at minimum three nodes. A multi-region cluster must have at minimum three nodes per region. Single-node clusters are not supported on Azure.
- CockroachDB Advanced on Azure meets or exceeds the requirements of SOC 2 Type 2. (Refer to Regulatory Compliance in CockroachDB Advanced.) However, note that the following features needed for PCI-Ready and HIPAA compliance are in Preview for Azure:
  - Customer Managed Encryption Keys (CMEK)
  - Egress Perimeter Controls

You can configure IP allowlisting to limit the IP addresses or CIDR ranges that can access a CockroachDB Advanced cluster on Azure, and you can use Azure Private Link to connect your applications in Azure to your cluster and avoid exposing your cluster or applications to the public internet. Refer to Connect to your cluster.

## Change data capture

CockroachDB Advanced supports changefeeds, which allow your cluster to send data events in real-time to a downstream sink. Azure Event Hubs provides an Azure-native service that can be used with a Kafka endpoint as a sink.

## Disaster recovery

Managed backups automatically back up clusters in CockroachDB Cloud.

You can take and restore from manual backups to Azure (Blob Storage or ADLS Gen 2). Refer to the blog post CockroachDB locality-aware Backups for Azure Blob for an example. To encrypt manual backups using an RSA key, refer to the Azure Key Vault documentation.