capabilities.work

Provision a Namespace with an Event Hub

A 3-step recipe with Azure Event Hubs. We can help you get access.

Recipe · 3 steps

Provision a Namespace with an Event Hub

with Azure Event Hubs · IT Infrastructure Management

Create a namespace, wait for provisioning, and add an event hub.

  1. Create or update the Event Hubs namespace with the supplied location and SKU. ARM accepts the request immediately and provisions asynchronously.
  2. Poll the namespace until Azure reports the provisioning state as Succeeded so dependent resources can be created safely.
  3. Create the event hub inside the provisioned namespace with the requested partition count and message retention.
What you'll need to have ready
  • subscriptionId: Azure subscription identifier that scopes the resource.
  • resourceGroupName: Name of the resource group that will contain the namespace.
  • namespaceName: The Event Hubs namespace name (6-50 chars, must be globally unique).
  • location: Azure region for the namespace (e.g. eastus).
  • skuName: The namespace SKU name.
  • eventHubName: The event hub name to create within the namespace.
  • partitionCount: Number of partitions for the event hub (1-32).
  • messageRetentionInDays: Days to retain events on the event hub (1-7).
  • apiVersion: Client API version for the management plane.
For your developer

Arazzo workflow microsoft-azure-event-hubs:provision-namespace-with-event-hub, 3 operations: Namespaces_CreateOrUpdate → Namespaces_Get → EventHubs_CreateOrUpdate. Specs on APIs.io.

More recipes with Azure Event Hubs

Microsoft Azure Event Hubs Configure Geo-Disaster Recovery PairingMicrosoft Azure Event Hubs Configure Event Hub Capture to Blob StorageMicrosoft Azure Event Hubs Create an Event Hub with a Consumer GroupMicrosoft Azure Event Hubs Lock Down a Namespace NetworkMicrosoft Azure Event Hubs Provision an Authorization Rule and Retrieve KeysMicrosoft Azure Event Hubs Register a Schema Registry GroupMicrosoft Azure Event Hubs Rotate Namespace Keys