> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Lower Over-Provisioned Event Hubs Throughput Units

> Lower Event Hubs Standard namespaces to the throughput units their traffic actually needs.

An Event Hubs Standard namespace is billed for each throughput unit (TU) every hour, whether or not it is used. Each TU carries up to 1 MB per second or 1,000 events per second of incoming traffic. nOps finds namespaces held at the same TU count every day whose busiest day needed fewer, and estimates the saving from lowering the count.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Integration |
| **Service** | Azure Event Hubs |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 14 days |
| **Source** | nOps |

## Why it matters

Auto-inflate raises throughput units when traffic grows but never lowers them again, so namespaces often stay at their highest count long after a spike.

## How nOps finds it

nOps reads the last 14 days of Event Hubs billing. A namespace is flagged when it was billed for the same whole number of TUs on all 14 days and is not mostly covered by reservations. The target is the busiest day's ingress events and operations, treated as if each were a 1 MB event, averaged over the day and rounded up to whole TUs (at least 1). The saving is the 7-day TU cost, scaled to a month, times the share of TUs removed. Services mostly paid with credits and savings under \$5 a month are left out.

## Before you start

Access to the namespace's metrics (incoming and outgoing bytes, throttled requests) to confirm the target.

## How to implement

1. In the Azure portal, check the namespace's **Metrics** for incoming and outgoing bytes and throttled requests at peak times, and how many consumer groups read the stream.
2. Go to **Scale**, set the throughput units to the target shown, keep **Auto-inflate** on, and set its maximum to the current count so bursts are still absorbed.
3. Or use `az eventhubs namespace update --resource-group RESOURCE_GROUP --name NAMESPACE --capacity TARGET_TUS --enable-auto-inflate true --maximum-throughput-units CURRENT_TUS`.
4. Update Terraform, Bicep or ARM templates (`capacity`) so a later deployment does not change it back.

## Risks and considerations

* Daily billing shows neither data size nor peaks within a day. Check the metrics: short bursts above the target would be throttled without auto-inflate.
* Each TU also limits outgoing traffic (2 MB per second), so many consumer groups can need more TUs than ingress suggests.
* To roll back, raise the throughput units again; the change is immediate.

## FAQs

> [accordion] Doesn't auto-inflate lower TUs by itself?
>
> No. Auto-inflate only scales up. You have to lower the count yourself.

## Related

* [Move Non-Production Service Bus Namespaces from Premium to Standard](https://help.nops.io/inform/supported-recommendations/move-non-production-service-bus-namespaces-from-premium-to-standard)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.