specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Azure Event Hubs
providerId: microsoft-azure-event-hubs
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: true
tags:
  - FinOps
  - FOCUS
  - Event Streaming
  - Microsoft Azure
description: 'FOCUS-aligned FinOps for Azure Event Hubs: hourly per-TU (Basic/Standard), per-PU (Premium),
  and per-CU (Dedicated) billing plus per-million ingress events on Basic and Standard.'
sources:
  - https://azure.microsoft.com/en-us/pricing/details/event-hubs/
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
publisherName: Microsoft Corporation
serviceCategory: Messaging / Event Streaming
billingModel:
  pricingCategory: Pay-As-You-Go
  billingFrequency: Monthly
  billingCurrency: USD
  chargeCategories:
    - Usage
    - Purchase
    - Tax
    - Adjustment
    - Credit
focusColumns:
  ServiceName: Azure Event Hubs
  ServiceCategory: Messaging
  ProviderName: Microsoft
  PublisherName: Microsoft Corporation
  InvoiceIssuerName: Microsoft Corporation
  BillingCurrency: USD
  ChargeCategory: Usage
meters:
  - name: throughput_unit_hours
    unit: instance-hour
    aggregation: sum
    dimensions:
      - tier
      - region
      - namespace
  - name: processing_unit_hours
    unit: instance-hour
    aggregation: sum
    dimensions:
      - region
      - namespace
  - name: capacity_unit_hours
    unit: instance-hour
    aggregation: sum
    dimensions:
      - region
      - cluster
  - name: ingress_events
    unit: event
    aggregation: sum
    dimensions:
      - namespace
      - eventhub
  - name: capture_storage
    unit: GB
    aggregation: sum
    dimensions:
      - namespace
      - destination
principles:
  - name: Visibility
    description: Use Azure Monitor metrics (Incoming Messages, Throttled Requests, Successful Requests)
      and Cost Management cost analysis grouped by namespace.
  - name: Allocation
    description: Use namespace-per-team or per-product separation; tag namespaces with cost-center
      tags; route data through dedicated namespaces for chargeback.
  - name: Optimization
    description: Right-size TUs/PUs; enable Auto-Inflate on Standard to avoid over-provisioning;
      consolidate low-volume namespaces; move stable high-volume workloads to Dedicated CUs for unit
      cost savings; use Capture instead of consumer-side ETL.
  - name: Accountability
    description: Assign namespace owners; alert on Throttled Requests metric; review tier choice
      quarterly against ingress and retention needs.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com