Azure Event Hub | How to stop the incurring Cost on my EventHub, while not in use
Case: In a situation, you observe your EventHub namespace is still incurring the cost, even though you are not doing any operations (read/write/management) on it and your EventHub namespace has no active EventHub instances present.
Root Cause of the behavior:
- At the time of creating the Azure EventHub namespace (Basic/Standard/Premium/Dedicated tier), you may have to give pre-purchased units of capacity in terms of Throughput units/Processing units/Capacity units based on the tier you choose. These pre-purchased units of capacity controls throughput capacity of the EventHub namespace.
- Among all the other pricing factors, cost will be incurred based on the number of pre-purchased units of capacity (Throughput units/Processing units/Capacity units) at the EventHub namespace level.
- Here I have attached a document, referring to the Azure EventHub pricing. Pricing - Event Hubs | Microsoft Azure
- As the pre-purchased units of capacity (Throughput units/Processing units/Capacity units) are defined at the EventHub namespace level, you will be charged per pre-purchased units of capacity configured hourly, even though there are no active EventHub instances present, and you are not performing any kind of operations on it.
How to mitigate this behavior:
- To stop the incurring cost while EventHub is not in use, you may have to delete the EventHub namespace, instead of disabling the EventHub instances.
- You can as well export the ARM template to create the same EventHub namespace in future, before deleting the existing EventHub namespace. Export template in Azure portal - Azure Resource Manager | Microsoft Learn
Published on:
Learn moreRelated posts
Setting up Power BI Version Control with Azure Dev Ops
In this blog post is a way set up version control for Power BI semantic models (and reports) using the PBIP (Power BI Project) format, Azure D...
Azure Developer CLI (azd) – March 2026: Run and Debug AI Agents Locally, GitHub Copilot Integration, & Container App Jobs
Run, invoke, and monitor AI agents locally or in Microsoft Foundry with the new azd AI agent extension commands. Plus GitHub Copilot-powered p...
Writing Azure service-related unit tests with Docker using Spring Cloud Azure
This post shows how to write Azure service-related unit tests with Docker using Spring Cloud Azure. The post Writing Azure service-related uni...
Azure SDK Release (March 2026)
Azure SDK releases every month. In this post, you find this month's highlights and release notes. The post Azure SDK Release (March 2026) appe...
Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed
The option to specify client ID and secret when creating Azure ACS principals will be removed. Users must adopt the system-generated client ID...
Azure Developer CLI (azd): Run and test AI agents locally with azd
New azd ai agent run and invoke commands let you start and test AI agents from your terminal—locally or in the cloud. The post Azure Developer...
Microsoft Purview compliance portal: Endpoint DLP classification support for Azure RMS–protected Office documents
Microsoft Purview Endpoint DLP will soon classify Azure RMS–protected Office documents, enabling consistent DLP policy enforcement on encrypte...
Introducing the Azure Cosmos DB Plugin for Cursor
We’re excited to announce the Cursor plugin for Azure Cosmos DB bringing AI-powered database expertise, best practices guidance, and liv...