/azmon-mirroredcatalogs-operations-cli

name: azmon-mirroredcatalogs-operations-cli
description: "Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it."

> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry > `x-ms-fabric-skill: azmon-mirroredcatalogs-operations-cli` (`az rest`: `--headers "x-ms-fabric-skill=azmon-mirroredcatalogs-operations-cli"`), > including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.

azmon-mirroredcatalogs-operations-cli

Guide a user end-to-end to (1) onboard Azure Monitor / Application Insights / Log Analytics observability data into Microsoft Fabric as a Mirrored Catalog (AzMon) item, and (2) turn that telemetry into **business-impact insights** by correlating observability signals with business data (bookings, orders, customers, flights, payments, revenue, tenants, accounts, subscriptions, usage KPIs, SLA/availability KPIs), ending in ready-to-paste **Operations Agent** instructions.

This is a **self-contained Skills-for-Fabric package**. It does **not** depend on any MCP server or tool controller as the execution mechanism. Product/API knowledge, supported flows, guardrails, and modeling rules live in this file and in `references/*.md`.

Prerequisite Knowledge

Before running this skill, read the shared common guidance:

• [Authentication & token acquisition](../../common/COMMON-CORE.md#authentication--token-acquisition)
• [Authentication recipes](../../common/COMMON-CLI.md#authentication-recipes)

Trigger phrases

• onboard Azure Monitor data into Fabric
• create Azure Monitor item in Fabric
• connect Application Insights to Fabric
• correlate App Insights telemetry with business data
• onboard my LA workspace to Fabric
• onboard Log Analytics workspace to Fabric
• connect Log Analytics workspace to Fabric
• understand if service availability impacted bookings
• understand if latency impacted conversion
• correlate exceptions with revenue or orders
• build Operations Agent for Azure Monitor business impact
• create business impact insights from Log Analytics data

When to use this skill (and related skills)

`azmon-mirroredcatalogs-operations-cli` is for onboarding Azure Monitor / Application Insights / Log Analytics telemetry into Microsoft Fabric (mirroredCatalogs endpoint), correlating that telemetry with business data, and generating Operations Agent instructions. For general Eventhouse / KQL querying unrelated to Azure Monitor onboarding, use `eventhouse-cli` consumption mode; for authoring Eventhouse items and databases, use its authoring mode.

Reference index

Read these when the corresponding stage needs product/API detail. Do not paste them wholesale into user responses — they are guidance for you, the agent.

| Reference | Use it for | |-----------|-----------| | [references/azmon-fabric-api-reference.md](references/azmon-fabric-api-reference.md) | Supported vs UI-only flows; connector modes; Fabric item/agent surfaces | | [references/workspace-identity-connection-reference.md](references/workspace-identity-connection-reference.md) | Mode B workspace-identity connection: provision/detect identity, user-granted LA RBAC, WorkspaceIdentity connection | | [references/workspace-discovery-policy-reference.md](references/workspace-discovery-policy-reference.md) | Stage 3 Fabric workspace discovery order, interpretation, user-supplied resolution, block-as-last-resort | | [references/oauth-connection-reference.md](references/oauth-connection-reference.md) | Mode B OAuth connection: read-only detection order, reuse rules, UI-guided creation steps | | [references/mirrored-catalog-reference.md](references/mirrored-catalog-reference.md) | Mirrored Catalog item CRUD, definition, discovery, monitoring, refresh | | [references/eventhouse-shortcuts-reference.md](references/eventhouse-shortcuts-reference.md) | Eventhouse/KQL, OneLake shortcuts, queryability requirement | | [references/operations-agent-reference.md](references/operations-agent-reference.md) | Operations Agent instruction template, validation, troubleshooting | | [references/telemetry-table-reference.md](references/telemetry-table-reference.md) | App Insights / OpenTelemetry / custom security telemetry tables and business meaning | | [references/app-insights-dynamic-fields-reference.md](references/app-insights-dynamic-fields-reference.md) | Dynamic fields (Properties/CustomDimensions) and hidden business keys | | [references/dashboard-reference.md](references/dashboard-reference.md) | Real-Time (KQL) Dashboard create/update mechanics; generic tile patterns | | [references/business-analysis-workflow.md](references/business-analysis-workflow.md) | Full detail for the business-analysis half — Stages 13–17 (incl. correlation patterns & modeling appendices); load at the Stage 12 handoff |

Secrecy & scope guardrails

• Do NOT expose Azure Log Analytics backend APIs to the user.
• Do NOT expose Fabric / DMTS / Gateway connection internals or internal

endpoints to the user.

• Do NOT request or disclose tokens, OAuth redirect codes, OAuth nonce values,

cookies, secrets, or internal implementation details.

• Do NOT mention MCP, MCP servers, or MCP connectivity/troubleshooting anywhere

in the user-facing flow. This Skill is self-contained.

• Do NOT present undocumented / browser-inspected / internal connector APIs as

supported public APIs.

• Do NOT claim OAuth Azure Monitor connector creation is available through a

public API — OAuth connector creation is **UI-guided only**.

• Do NOT fabricate workspace names, table names, schema, item IDs, connection

IDs, or query results. Use only values returned by real discovery/queries; use clearly-labelled placeholders otherwise.

• Do NOT ask the user for JOIN logic,