MonitorManagementClient

Name: MonitorManagementClient API
Brand: Azure Monitor Management Event Types
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth21 EndpointsREST

For Agents

Read the catalog of Azure Monitor management event types available for a subscription. Single endpoint that returns activity log event type names used in alert rules and log queries.

Connect the MonitorManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MonitorManagementClient, 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 MonitorManagementClient API.

List the management event types available for a subscription

Retrieve the vocabulary used to filter Azure activity log queries

Surface the event type identifiers used by Azure alert rules

Use Cases

Patterns agents use MonitorManagementClient API for, with concrete tasks.

GET STARTED

Start building with MonitorManagementClient API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for this Azure Monitor management event types endpoint, keeping it validated and agent-ready. The MonitorManagementClient 2015-04-01 surface exposes a single read endpoint that returns the list of management event types available for an Azure subscription. Management events represent control-plane operations such as resource creation, deletion, and policy changes recorded in the Azure activity log. The returned event types form the vocabulary used to filter activity log queries and to construct alert rules that trigger on specific control-plane operations.

★ Activity log filter discovery

Engineers building activity log queries or alert rules need the exact event type identifier to filter on. This endpoint returns the management event type catalog scoped to a subscription, providing the canonical strings used by the Azure Monitor query and alert APIs. Pulling the list once and caching it locally avoids hard-coding event types that may differ across subscriptions or cloud environments.

Retrieve management event types for subscription abc and return the list of event type names that contain the substring Compute.

Alert rule construction tooling

Tooling that builds Azure Monitor alert rules programmatically needs to validate event type names before submitting a rule. Calling this endpoint at rule build time gives the tool an authoritative list to validate against, preventing alert deployments that fail at runtime because of a mistyped event type identifier.

Fetch management event types and verify that Microsoft.Network/networkSecurityGroups/write appears in the list before submitting an activity log alert rule for that operation.

Multi-subscription compliance scans

Compliance teams that scan many subscriptions for unusual control-plane activity can fetch the management event type list for each subscription as the first step of a scan. Differences in the returned vocabulary across subscriptions can flag preview features that have been enabled in only some environments, which is itself a useful compliance signal.

For each subscription in the tenant, retrieve management event types and return any event type identifier that does not appear in every subscription.

Agent-driven activity log exploration

AI agents can use Jentic to discover the MonitorManagementClient operation by intent, load the structured input schema, and execute the call against management.azure.com without browsing the Azure REST docs. An exploration agent answering a natural-language question about Azure activity can fetch the event type catalog as a first step and use it to guide subsequent activity log queries.

Search Jentic for list azure management event types, load the schema, and execute it for subscription abc, returning the count of event types per resource provider namespace.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for this azure monitor management event types endpoint, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/microsoft.insights/eventtypes/management/values

List management event types for a subscription

GET

/subscriptions/{subscriptionId}/providers/microsoft.insights/eventtypes/management/values

List management event types for a subscription

Why though Jentic?

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

Credential isolation

Azure AD OAuth credentials and service principals are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens for management.azure.com at execution time; client secrets and certificates never enter the agent context.

Intent-based discovery

Agents search by intent (for example list azure management event types) and Jentic returns the matching ARM operation with its full input schema, so the agent can call the correct path without browsing Microsoft Learn docs.

Time to first call

Direct integration with this single endpoint: a few hours including AAD auth setup. Through Jentic: a few minutes to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Microsoft Insights

Broader Azure Monitor surface for metrics, diagnostic settings, and activity log queries.

Use this when the agent needs to read or query activity log records, configure diagnostic settings, or work with metric definitions.

Complementary

Application Insights

Application telemetry and analytics that complements platform-level activity events.

Choose this when the agent needs in-process request, dependency, or exception telemetry rather than control-plane event types.

Alternative

Azure Resource Graph Query

Query Azure resources and recent change events at scale using KQL.

Choose this when the agent needs to query resource state across many subscriptions rather than enumerate event type identifiers.

FAQs

Specific to using MonitorManagementClient API through Jentic.

Why is there no official OpenAPI spec for MonitorManagementClient 2015-04-01?

Microsoft Azure does not publish an OpenAPI specification for this slice of the microsoft.insights resource provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call MonitorManagementClient 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 Azure Monitor Management Event Types API use?

The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and supplies scoped bearer tokens to agents at execution time without exposing the underlying credential.

What does this MonitorManagementClient endpoint actually return?

GET /subscriptions/{subscriptionId}/providers/microsoft.insights/eventtypes/management/values returns the list of management event type identifiers available for the subscription. These are the event type strings used by Azure activity log filters and Azure Monitor alert rules; the endpoint does not return event instances or counts.

What are the rate limits for this API?

It follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations are limited to 1200 requests per hour per subscription. The event type list is small and changes rarely, so callers should cache the response rather than poll.

How do I list Azure management event types through Jentic?

Search Jentic for list azure management event types, load the schema for GET /subscriptions/{subscriptionId}/providers/microsoft.insights/eventtypes/management/values, and execute it with the target subscription ID. Jentic handles the AAD token exchange and returns the event type catalog.

Can I query actual activity log entries with this API?

No. This endpoint only returns the catalog of event type identifiers. To query actual activity log records, use the Azure Monitor activity log query endpoint or Log Analytics, which accept the event type identifiers returned here as filter values.