diff --git a/docs/self-managed/concepts/multi-region/dual-region.md b/docs/self-managed/concepts/multi-region/dual-region.md
index 7e1d9097ae..d0a9bef03c 100644
--- a/docs/self-managed/concepts/multi-region/dual-region.md
+++ b/docs/self-managed/concepts/multi-region/dual-region.md
@@ -123,15 +123,16 @@ Customers are responsible for detecting regional failures and executing the [ope
### Camunda 8 dual-region limitations
-| **Aspect** | **Details** |
-| :----------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Installation methods |
- For **kubernetes** we recommend using a dual-region Kubernetes setup with the [Camunda Helm chart](/self-managed/setup/install.md) installed in two Kubernetes clusters.
- For **other platforms**, using alternative installation methods (for example, with docker-compose) is not covered in this guide.
|
-| Camunda Platform Configuration | The overall Camunda platform is **active-passive**, although some key components are active-active.
- **Active-Passive Traffic Handling:** One active and one passive region serve active user traffic.
- **Traffic to Both Regions:** Serving traffic to both regions will cause component detachment, potentially resulting in different data visibility in Operate and Tasklist.
|
-| Identity Support | Identity is not supported, multi-Tenancy and Role-Based Access Control (RBAC) does not work. |
-| Optimize Support | Not supported (requires Identity). |
-| Connectors Deployment | Connectors can be deployed in a dual-region setup, but attention to [idempotency](../../../components/connectors/use-connectors/inbound.md#creating-the-connector-event) is required to avoid event duplication. In a dual-region setup, you'll have two connector deployments and using message idempotency is of importance to not duplicate events. |
-| Zeebe Cluster Scaling | Not supported. |
-| Web-Modeler | Is a standalone component not covered in this guide. Modeling applications can operate independently outside of the automation clusters. |
+| **Aspect** | **Details** |
+| :----------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Installation methods | - For **kubernetes** we recommend using a dual-region Kubernetes setup with the [Camunda Helm chart](/self-managed/setup/install.md) installed in two Kubernetes clusters.
- For **other platforms**, using alternative installation methods (for example, with docker-compose) is not covered in this guide.
|
+| Camunda Platform Configuration | The overall Camunda platform is **active-passive**, although some key components are active-active.
- **Active-Passive Traffic Handling:** One active and one passive region serve active user traffic.
- **Traffic to Both Regions:** Serving traffic to both regions will cause component detachment, potentially resulting in different data visibility in Operate and Tasklist.
|
+| Identity Support | Identity is not supported, multi-Tenancy and Role-Based Access Control (RBAC) does not work. |
+| Optimize Support | Not supported (requires Identity). |
+| Connectors Deployment | Connectors can be deployed in a dual-region setup, but attention to [idempotency](../../../components/connectors/use-connectors/inbound.md#creating-the-connector-event) is required to avoid event duplication. In a dual-region setup, you'll have two connector deployments and using message idempotency is of importance to not duplicate events. |
+| Connectors | If you are running Connectors and have a process with an inbound connector deployed in a dual-region setup, consider the following: - when you want to delete the process deployment, delete it via Operate (not zbctl), otherwise the inbound connector won't deregister.
- if you have multiple Operate instances running, then perform the delete operation in both instances. This is a [known limitation](https://github.com/camunda/camunda/issues/17762).
|
+| Zeebe Cluster Scaling | Not supported. |
+| Web-Modeler | Is a standalone component not covered in this guide. Modeling applications can operate independently outside of the automation clusters. |
### Platform considerations
@@ -148,6 +149,12 @@ For example, consider the following complexities (not covered in our guides):
- Bursts of increased latency can already have an impact.
- Managing DNS and incoming traffic.
+### Upgrade considerations
+
+When upgrading a dual-region setup, it is crucial to follow a staged approach. Perform the upgrade in one region first before proceeding to the other.
+
+Simultaneously upgrading both regions can result in a loss of quorum for partitions, as two Zeebe brokers might be upgraded at the same time. To prevent this issue, it is recommended to upgrade one region at a time, ensuring that only one Zeebe broker is updated during each upgrade phase.
+
## Region loss
In a dual-region setup, a loss of a region will invariably affect Camunda 8, regardless of whether it's the active or passive region.
diff --git a/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md b/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md
index 322c6f5dd0..f2ccd04d18 100644
--- a/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md
+++ b/versioned_docs/version-8.5/self-managed/concepts/multi-region/dual-region.md
@@ -134,6 +134,9 @@ In the event of a total active region loss, the following data will be lost:
- This is due to Optimize depending on Identity to work.
- Connectors can be deployed alongside but ensure to understand idempotency based on [the described documentation](../../../components/connectors/use-connectors/inbound.md#creating-the-connector-event).
- in a dual-region setup, you'll have two connector deployments and using message idempotency is of importance to not duplicate events.
+- If you are running Connectors and have a process with an inbound connector deployed in a dual-region setup, consider the following:
+ - when you want to delete the process deployment, delete it via Operate (not zbctl), otherwise the inbound connector won't deregister.
+ - if you have multiple Operate instances running, then perform the delete operation in both instances. This is a [known limitation](https://github.com/camunda/camunda/issues/17762).
- During the failback procedure, there’s a small chance that some data will be lost in Elasticsearch affecting Operate and Tasklist.
- This **does not** affect the processing of process instances in any way. The impact is that some information about the affected instances might not be visible in Operate and Tasklist.
- This is further explained in the [operational procedure](./../../operational-guides/multi-region/dual-region-ops.md?failback=step2#failback) during the relevant step.
@@ -153,6 +156,12 @@ You should familiarize yourself with those before deciding to go for a dual-regi
- Bursts of increased latency can already have an impact
- Managing DNS and incoming traffic
+### Upgrade considerations
+
+When upgrading a dual-region setup, it is crucial to follow a staged approach. Perform the upgrade in one region first before proceeding to the other.
+
+Simultaneously upgrading both regions can result in a loss of quorum for partitions, as two Zeebe brokers might be upgraded at the same time. To prevent this issue, it is recommended to upgrade one region at a time, ensuring that only one Zeebe broker is updated during each upgrade phase.
+
## Region loss
In a dual-region setup, a loss of a region will invariably affect Camunda 8, regardless of whether it's the active or passive region.