Azure Event Hubs quotas and limits
This section lists basic quotas and limits in Azure Event Hubs.
|Number of Event Hubs namespaces per subscription||Subscription||-||1000|
|Number of event hubs per namespace||Namespace||Subsequent requests for creation of a new event hub will be rejected.||10|
|Number of partitions per event hub||Entity||-||32|
|Number of consumer groups per event hub||Entity||-||20|
|Number of AMQP connections per namespace||Namespace||Subsequent requests for additional connections will be rejected and an exception is received by the calling code.||5,000|
|Maximum size of Event Hubs event||Entity||-||1 MB|
|Maximum size of an event hub name||Entity||-||50 characters|
|Number of non-epoch receivers per consumer group||Entity||-||5|
|Maximum retention period of event data||Entity||-||1-7 days|
|Maximum throughput units||Namespace||Exceeding the throughput unit limit causes your data to be throttled and generates a ServerBusyException. You can request a larger number of throughput units for a Standard tier by filing a support request. Additional throughput units are available in blocks of 20 on a committed purchase basis.||20|
|Number of authorization rules per namespace||Namespace||Subsequent requests for authorization rule creation will be rejected.||12|
You can learn more about Event Hubs by visiting the following links:
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.