Microsoft Azure EventHub2018PreviewManagementClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth226 Endpoints

Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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

GET STARTED

Start building with EventHub2018PreviewManagementClient API

Explore with Jentic

View OpenAPI Document

For Agents

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

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.

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 Jentic?

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

Credential isolation

Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The service principal secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Event Hubs cluster' or 'add an IP filter rule to a namespace', and Jentic returns the matching Clusters, Namespaces, or rule operation with its input schema so the agent calls the right endpoint without memorising the long ARM path layout.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Azure Event Hubs Management API?

Yes. Because you self-host Jentic One, your own rules decide which operations the agent may call and which Azure credentials it may use. Every path carries the subscription, resource group, and cluster or namespace name, so you can pin the agent to a single namespace and its IP filter and virtual network rules. You choose the operations it can run, so destructive ones like Clusters_Delete or IpFilterRules_Delete stay out of reach unless you explicitly add them.