Skip to content

Commit bf3d849

Browse files
committed
making pricing doc improvements
1 parent 1319c00 commit bf3d849

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

articles/event-hubs/geo-replication.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -196,20 +196,30 @@ Note the following considerations to keep in mind with this feature:
196196

197197
## Pricing
198198

199-
Geo-replication pricing has 2 parameters -
199+
The pricing varies based on the tier you pick, but generally has 2 parameters -
200200

201201
* The compute charge for the cluster or namespace.
202202
* The bandwidth charge for the data being replicated between the primary and secondary regions.
203203

204+
> [!NOTE]
205+
> Please refer to the pricing details listed at [Azure Event Hubs](https://azure.microsoft.com/products/event-hubs/) to determine the charges. The geo-replication charge depends on location of the primary region.
206+
>
207+
204208
### Dedicated clusters
205209

206210
Use of geo-replication with Event Hubs dedicated requires you to have at least two dedicated clusters in separate regions, which can be used to host namespaces other than the one being geo-replicated. These dedicated clusters are billed separately based on the number of Capacity Units (CUs) allocated to each.
207211

208-
Bandwidth is charged based on the data transferred between the primary and secondary regions.
212+
When geo-replication is enabled, the only additional charge is the bandwidth charge for the data replicated from primary to secondary. This charge depends on the location of the primary region.
209213

210214
### Premium namespaces
211215

212-
For Premium namespaces, enabling geo-replication provisions the same number of processing units (PUs) in the secondary region. Thus, enabling geo-replication on a premium namespace doubles the Processing Units (PUs) billed.
216+
For Premium namespaces, enabling geo-replication provisions the same number of processing units (PUs) in the secondary region. Thus, you pay for the **number of PUs** you are using and the **bandwidth for the data transferred between the primary and secondary region**.
217+
218+
For example, if you enable geo-replication on a Premium namespace which has been provisioned with **4 PU**, you will be billed for
219+
220+
* 4 PUs in the primary region,
221+
* 4 PUs in the secondary region,
222+
* Geo-replication charge per GB of data replicated.
213223

214224
Bandwidth is charged based on the data transferred between the primary and secondary regions.
215225

0 commit comments

Comments
 (0)