canonical: https://jentic.com/apis/azure.com/monitor-management-event-types

# Microsoft Azure MonitorManagementClient

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.

## For AI 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.

## Scope

Does not return activity log records, metric values, or alert rule definitions - use for reading the catalog of management event type identifiers only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| Method | Path | Description |
| --- | --- | --- |
| GET | /subscriptions/{subscriptionId}/providers/microsoft.insights/eventtypes/management/values | List management event types for a subscription |

## Key resources

- **Management Event Types** — Catalog of activity log event type identifiers used in Azure Monitor alert rules and log queries, scoped to a subscription.

## Why Jentic

- **Setup:** Wiring this MonitorManagementClient endpoint by hand means implementing Azure AD OAuth 2.0, minting an ARM-scoped bearer token for management.azure.com, and handling ARM read throttling for a single event types read yourself. Through Jentic you install once, import Azure Monitor Management Event Types from the API Directory, store the Azure AD credential once, and your agent calls it.
- **Permission scoping:** The API puts the subscription in the URL path and exposes a single read that lists management event types, so a rule can pin your agent to reading event types for one subscription and nothing else. The operation is read-only, so the agent cannot change any resource.
- **Credential handling:** Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list Azure management event types', and Jentic returns the matching MonitorManagementClient operation with its input schema so the agent supplies the subscription and executes.

## Related APIs

- **Microsoft Insights** — Broader Azure Monitor surface for metrics, diagnostic settings, and activity log queries.
- **Application Insights** — Application telemetry and analytics that complements platform-level activity events.
- **Azure Resource Graph Query** — Query Azure resources and recent change events at scale using KQL.

## FAQ

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

### 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.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes only a single read that lists management event types for the subscription named in the request path. You can pin your agent to reading event types for one specific subscription and nothing else, since the subscription ID is part of the URL. The operation is read-only, so the agent can enumerate the event type catalog but cannot create, change, or delete any Azure resource.