EventHub2018PreviewManagementClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth226 EndpointsREST

For Agents

Provision Azure Event Hubs dedicated clusters and namespaces and lock down namespace network access with IP filter rules and virtual network rules.

Connect the EventHub2018PreviewManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EventHub2018PreviewManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EventHub2018PreviewManagementClient API.

Provision and delete dedicated Event Hubs clusters in a resource group

List Event Hubs namespaces hosted on a dedicated cluster

Read and patch the per-cluster quota configuration

Create or update Event Hubs namespaces with a chosen SKU and capacity

GET STARTED

Start building with EventHub2018PreviewManagementClient API

Explore with Jentic

View OpenAPI Document

Use for: Provision a dedicated Event Hubs cluster in resource group prod-rg in eastus, List all Event Hubs namespaces in subscription 1111-2222-3333-4444, Add an IP filter rule allowing 10.0.0.0/16 on namespace eh-prod, Bind namespace eh-prod to the data subnet via a virtual network rule

Not supported: Does not publish or consume events, manage consumer groups, or read messages from event streams — use only to provision and configure Event Hubs clusters, namespaces, and namespace network rules.

Jentic publishes the only available OpenAPI document for EventHub2018PreviewManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for EventHub2018PreviewManagementClient, keeping it validated and agent-ready. This Azure Event Hubs management API provisions and configures dedicated Event Hubs clusters along with the namespaces hosted on them. It also exposes per-namespace network controls including IP filter rules and virtual network rules so platform teams can restrict ingress to known networks and address ranges.

Use Cases

Patterns agents use EventHub2018PreviewManagementClient API for, with concrete tasks.

★ Provision a Dedicated Event Hubs Cluster

Platform teams running high-throughput streaming workloads provision dedicated Event Hubs clusters to isolate capacity from the multi-tenant tier. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName} creates the cluster, and the matching list and get endpoints expose its provisioning state so an automation can wait until the cluster is ready before creating namespaces.

Create an Event Hubs dedicated cluster named ehc-prod in resource group platform-rg in region eastus2 and poll Clusters_Get until provisioningState is Succeeded

Lock Down Namespace Ingress with IP Filter Rules

Security engineers restrict which networks can reach an Event Hubs namespace by attaching IP filter rules with explicit accept or reject actions. The ipfilterrules endpoints under a namespace allow listing existing rules, creating new CIDR-based rules, and deleting outdated entries during quarterly access reviews.

Create an IP filter rule named office-cidr on namespace eh-prod that accepts traffic from 203.0.113.0/24 and remove the previous wide-open rule

Bind Namespaces to Private Subnets

Teams operating Event Hubs from a private virtual network use virtual network rules to permit traffic only from specific subnets. The virtualnetworkrules endpoints create, list, and remove these subnet bindings on a namespace so streaming traffic is contained inside the VNet without traversing the public internet.

Add a virtual network rule on namespace eh-prod for subnet /subscriptions/1111/resourceGroups/net/providers/Microsoft.Network/virtualNetworks/vnet-prod/subnets/data

Agent-Driven Streaming Capacity Provisioning

An AI agent provisioning streaming infrastructure can stand up a dedicated cluster, create the namespaces tenants will use, and apply IP and VNet rules in one workflow through Jentic. Intent search returns the cluster, namespace, and rule operations with their schemas, while the Azure OAuth credential is held in the vault so the service principal secret never enters the agent context.

Search Jentic for 'create an Event Hubs cluster', execute Clusters_Put for ehc-prod, then create namespace eh-prod on the cluster and attach IP and VNet rules

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for eventhub2018previewmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName}

Create or update an Event Hubs cluster

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName}/namespaces

List namespaces on a cluster

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}

Create or update an Event Hubs namespace

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/ipfilterrules/{ipFilterRuleName}

Create or update an IP filter rule

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/ipfilterrules

List IP filter rules on a namespace

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName}/quotaConfiguration/default

Patch cluster quota configuration

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName}

Create or update an Event Hubs cluster

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName}/namespaces

List namespaces on a cluster

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}

Create or update an Event Hubs namespace

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/ipfilterrules/{ipFilterRuleName}

Create or update an IP filter rule

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/ipfilterrules

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure Active Directory OAuth 2.0 tokens are minted and rotated inside the Jentic vault (MAXsystem). Service principal client secrets stay encrypted; agents call Microsoft.EventHub with a short-lived scoped token only.

Intent-based discovery

Agents search by intent (e.g., 'create an Event Hubs cluster') and Jentic returns the matching Microsoft.EventHub operation with its input schema, so the agent does not need to memorise the long ARM path layout.

Time to first call

Direct ARM integration: 1-3 days for AAD app registration, token acquisition, async polling, and throttling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon Kinesis Analytics

AWS streaming analytics service used as an alternative to Event Hubs in AWS-native stacks.

Choose Kinesis Analytics for AWS pipelines. Stay with Event Hubs when streaming inside Azure.

Complementary

Azure Monitor Management Client

Collects metrics and diagnostic logs emitted by Event Hubs namespaces and clusters.

Use Monitor to set throughput alerts on the Event Hubs namespaces this API provisions.

Complementary

Azure Network Management Client

Manages the virtual networks and subnets referenced by Event Hubs virtual network rules.

Use the network client to create the subnets that this API then binds to namespaces.

FAQs

Specific to using EventHub2018PreviewManagementClient API through Jentic.

Why is there no official OpenAPI spec for EventHub2018PreviewManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EventHub2018PreviewManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Event Hubs Management API use?

The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Through Jentic, the AAD service principal secret is stored in the MAXsystem vault and exchanged for a short-lived bearer token per call.

Can I provision a dedicated Event Hubs cluster with this API?

Yes. Call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/clusters/{clusterName} with the cluster body, then poll Clusters_Get until provisioningState is Succeeded before creating namespaces on it.

How do I restrict an Event Hubs namespace to specific IP ranges?

Use the ipfilterrules endpoints under the namespace. PUT a rule with a CIDR mask and an accept or reject action, then list the rules to confirm. To bind to a private subnet instead, use the virtualnetworkrules endpoints to attach a subnet resource id.

What are the rate limits for the Azure Event Hubs Management API?

Azure Resource Manager applies subscription-level throttling. Mutation calls (PUT, PATCH, DELETE) are throttled more strictly than reads; on HTTP 429 back off using the Retry-After header. Cluster provisioning is asynchronous, so wait on the operation result rather than retrying the PUT.

How do I provision an Event Hubs cluster and namespace through Jentic?

Run pip install jentic, then search Jentic with 'create an Event Hubs cluster'. Load and execute Clusters_Put against your resource group, then chain a second call to Namespaces_CreateOrUpdate for the namespace. The AAD token is sourced from the vault on every call so the agent never sees the service principal secret.