Skip to content

Commit 8f26f71

Browse files
committed
Learn Editor: Update event-hubs-dedicated-overview.md
1 parent 001780e commit 8f26f71

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/event-hubs/event-hubs-dedicated-overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,8 +73,7 @@ Approximately one CU in a self-serve scalable cluster provides *ingress capacity
7373
With self-serve scalable clusters, you can purchase up to 10 CUs for a cluster in the Azure portal. In contrast to traditional clusters, these clusters can be scaled incrementally with CUs ranging from 1 to 10. If you need a cluster larger than 10 CUs, you can [submit a support request](event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request) to scale up your cluster after its creation.
7474

7575
> [!IMPORTANT]
76-
> You can deploy self-serve scalable dedicated clusters with [availability zones](../availability-zones/az-overview.md#azure-regions-with-availability-zones) that are enabled with three CUs. However, you can't use the self-serve scaling capability to scale the cluster. To create or scale an AZ-enabled self-serve cluster, you must [submit a support request](event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request).
77-
76+
> To create or scale an AZ-enabled self-serve cluster, you must [submit a support request](event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request) requesting three CUs or greater. A three CU (or greater) self-serve cluster created via Portal is NOT AZ-enabled.
7877
### Legacy clusters
7978

8079
Event Hubs dedicated clusters created before the availability of self-serve scalable clusters are referred to as legacy clusters.

0 commit comments

Comments
 (0)