Merge pull request #212529 from kasun04/main

Updating AZ support in dedicated and premium SKUs

Author: 19BMG00

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

@@ -35,6 +35,13 @@ The Event Hubs dedicated offering is billed at a fixed monthly price, with a **m
 
 For more information about quotas and limits, see [Event Hubs quotas and limits](event-hubs-quotas.md)
 
+## High availability with Azure Availability Zones 
+Event Hubs dedicated clusters offer [availability zones](../availability-zones/az-overview.md#availability-zones) support where you can run event streaming workloads in physically separate locations within each Azure region that are tolerant to local failures. 
+
+> [!IMPORTANT] 
+> Event Hubs dedicated clusters require at least 8 Capacity Units(CUs) to enable availability zones. Clusters with self-serve scaling does not support availability zones yet. Availability zone support is only available in [Azure regions with availability zones](https://learn.microsoft.com/azure/availability-zones/az-overview#azure-regions-with-availability-zones). 
+
+
 ## How to onboard
 Event Hubs dedicated tier is generally available (GA). The self-serve experience to create an Event Hubs cluster through the [Azure portal](event-hubs-dedicated-cluster-create-portal.md) is currently in Preview. You can also request for the cluster to be created by contacting the [Event Hubs team](mailto:[email protected]). 
 

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

@@ -16,6 +16,16 @@ In addition to these storage-related features and all capabilities and protocol
 > [!NOTE]
 > Event Hubs Premium supports TLS 1.2 or greater. 
 
+You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
+
+* Number of producers and consumers
+* Payload size 
+* Partition count
+* Egress request rate 
+* Usage of Event Hubs Capture, Schema Registry, and other advanced features
+
+For more information, see [comparison between Event Hubs SKUs](event-hubs-quotas.md).
+
 ## Why premium?
 The premium tier offers three compelling benefits for customers who require better isolation in a multitenant environment with low latency and high throughput data ingestion needs.
 
@@ -30,28 +40,6 @@ It implements a *cluster in cluster* model in its multitenant clusters to provid
 ### Cost savings and scalability
 As the premium tier is a multitenant offering, it can dynamically scale more flexibly and very quickly. Capacity is allocated in processing units (PUs) that allocate isolated pods of CPU/memory inside the cluster. The number of those pods can be scaled up/down per namespace. Therefore, the premium tier is a low-cost option for messaging scenarios with the overall throughput range that is less than 120 MB/s but higher than what you can achieve with the standard SKU.  
 
-## Premium vs. dedicated tiers
-In comparison to the dedicated offering, the premium tier provides the following benefits:
-
-- Isolation inside a very large multi-tenant environment that can shift resources quickly
-- Scale far more elastically and quicker
-- PUs can be dynamically adjusted
-
-Therefore, the premium tier is often a more cost effective option for event streaming workloads up to 160 MB/sec (per namespace), especially with changing loads throughout the day or week, when compared to the dedicated tier. 
-
-> [!NOTE]
-> For the extra robustness gained by **availability-zone** support, the minimal deployment scale for the dedicated tier is **8 capacity units (CU)**, but you'll have availability zone support in the premium tier from the first PU in all availability zone regions. 
-
-You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
-
-* Number of producers and consumers
-* Payload size 
-* Partition count
-* Egress request rate 
-* Usage of Event Hubs Capture, Schema Registry, and other advanced features
-
-For more information, see [comparison between Event Hubs SKUs](event-hubs-quotas.md).
-
 ## Encryption of events
 Azure Event Hubs provides encryption of data at rest with Azure Storage Service Encryption (Azure SSE). The Event Hubs service uses Azure Storage to store the data. All the data that's stored with Azure Storage is encrypted using Microsoft-managed keys. If you use your own key (also referred to as Bring Your Own Key (BYOK) or customer-managed key), the data is still encrypted using the Microsoft-managed key, but in addition the Microsoft-managed key will be encrypted using the customer-managed key. This feature enables you to create, rotate, disable, and revoke access to customer-managed keys that are used for encrypting Microsoft-managed keys. Enabling the BYOK feature is a one time setup process on your namespace. For more information, see [Configure customer-managed keys for encrypting Azure Event Hubs data at rest](configure-customer-managed-key.md).
 
@@ -63,6 +51,25 @@ Azure Event Hubs provides encryption of data at rest with Azure Storage Service
 The premium tier offers all the features of the standard plan, but with better performance, isolation and more generous quotas. 
 For more quotas and limits, see [Event Hubs quotas and limits](event-hubs-quotas.md)
 
+## High availability with Azure Availability Zones 
+Event Hubs premium offers [availability zones](../availability-zones/az-overview.md#availability-zones) support with no extra cost. Using availability zones, you can run event streaming workloads in physically separate locations within each Azure region that are tolerant to local failures. 
+
+> [!IMPORTANT] 
+> Availability zone support is only available in [Azure regions with availability zones](https://learn.microsoft.com/azure/availability-zones/az-overview#azure-regions-with-availability-zones). 
+
+
+## Premium vs. dedicated tiers
+In comparison to the dedicated offering, the premium tier provides the following benefits:
+
+- Isolation inside a large multi-tenant environment that can shift resources quickly
+- Scale far more elastically and quicker
+- PUs can be dynamically adjusted
+
+Therefore, the premium tier is often a more cost effective option for event streaming workloads up to 160 MB/sec (per namespace), especially with changing loads throughout the day or week, when compared to the dedicated tier. 
+
+> [!NOTE]
+> For the extra robustness gained by **availability-zone** support, the minimal deployment scale for the dedicated tier is **8 capacity units (CU)**, but you'll have availability zone support in the premium tier from the first PU in all availability zone regions. 
+
 ## Pricing
 
 The Premium offering is billed by [Processing Units (PUs)](event-hubs-scalability.md#processing-units) which correspond to a share of isolated resources (CPU, Memory, and Storage) in the underlying infrastructure.