[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699QPEJH5KWQ1VPD28EABXQ":3,"skill-same:01M699QPEJH5KWQ1VPD28EABXQ":121},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M699QPEJH5KWQ1VPD28EABXQ","azmon-mirroredcatalogs-operations-cli",null,"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.","microsoft\u002Fskills-for-fabric","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699NAPJKS2WBHHDN86Q5MM6",1353,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[35,36,37,38],"cli","azmon mirroredcatalogs operations cli","dashboard","telemetry","2026-11-10 10:12:30",false,"---\nname: azmon-mirroredcatalogs-operations-cli\ndescription: \"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.\"\n---\n\n> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: azmon-mirroredcatalogs-operations-cli` (`az rest`: `--headers \"x-ms-fabric-skill=azmon-mirroredcatalogs-operations-cli\"`),\n> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.\n\n# azmon-mirroredcatalogs-operations-cli\n\nGuide a user end-to-end to (1) onboard Azure Monitor \u002F Application Insights \u002F\nLog Analytics observability data into Microsoft Fabric as a Mirrored Catalog\n(AzMon) item, and (2) turn that telemetry into **business-impact insights** by\ncorrelating observability signals with business data (bookings, orders,\ncustomers, flights, payments, revenue, tenants, accounts, subscriptions, usage\nKPIs, SLA\u002Favailability KPIs), ending in ready-to-paste **Operations Agent**\ninstructions.\n\nThis is a **self-contained Skills-for-Fabric package**. It does **not** depend on\nany MCP server or tool controller as the execution mechanism. Product\u002FAPI\nknowledge, supported flows, guardrails, and modeling rules live in this file and\nin `references\u002F*.md`.\n\n## Prerequisite Knowledge\n\nBefore running this skill, read the shared common guidance:\n\n- [Authentication & token acquisition](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#authentication--token-acquisition)\n- [Authentication recipes](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#authentication-recipes)\n\n## Trigger phrases\n\n- onboard Azure Monitor data into Fabric\n- create Azure Monitor item in Fabric\n- connect Application Insights to Fabric\n- correlate App Insights telemetry with business data\n- onboard my LA workspace to Fabric\n- onboard Log Analytics workspace to Fabric\n- connect Log Analytics workspace to Fabric\n- understand if service availability impacted bookings\n- understand if latency impacted conversion\n- correlate exceptions with revenue or orders\n- build Operations Agent for Azure Monitor business impact\n- create business impact insights from Log Analytics data\n\n## When to use this skill (and related skills)\n\n`azmon-mirroredcatalogs-operations-cli` is for onboarding Azure Monitor \u002F\nApplication Insights \u002F Log Analytics telemetry into Microsoft Fabric\n(mirroredCatalogs endpoint), correlating that telemetry with business data, and\ngenerating Operations Agent instructions. For general Eventhouse \u002F KQL querying\nunrelated to Azure Monitor onboarding, use `eventhouse-cli` consumption mode;\nfor authoring Eventhouse items and databases, use its authoring mode.\n\n## Reference index\n\nRead these when the corresponding stage needs product\u002FAPI detail. Do not paste\nthem wholesale into user responses — they are guidance for you, the agent.\n\n| Reference | Use it for |\n|-----------|-----------|\n| [references\u002Fazmon-fabric-api-reference.md](references\u002Fazmon-fabric-api-reference.md) | Supported vs UI-only flows; connector modes; Fabric item\u002Fagent surfaces |\n| [references\u002Fworkspace-identity-connection-reference.md](references\u002Fworkspace-identity-connection-reference.md) | Mode B workspace-identity connection: provision\u002Fdetect identity, user-granted LA RBAC, WorkspaceIdentity connection |\n| [references\u002Fworkspace-discovery-policy-reference.md](references\u002Fworkspace-discovery-policy-reference.md) | Stage 3 Fabric workspace discovery order, interpretation, user-supplied resolution, block-as-last-resort |\n| [references\u002Foauth-connection-reference.md](references\u002Foauth-connection-reference.md) | Mode B OAuth connection: read-only detection order, reuse rules, UI-guided creation steps |\n| [references\u002Fmirrored-catalog-reference.md](references\u002Fmirrored-catalog-reference.md) | Mirrored Catalog item CRUD, definition, discovery, monitoring, refresh |\n| [references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md) | Eventhouse\u002FKQL, OneLake shortcuts, queryability requirement |\n| [references\u002Foperations-agent-reference.md](references\u002Foperations-agent-reference.md) | Operations Agent instruction template, validation, troubleshooting |\n| [references\u002Ftelemetry-table-reference.md](references\u002Ftelemetry-table-reference.md) | App Insights \u002F OpenTelemetry \u002F custom security telemetry tables and business meaning |\n| [references\u002Fapp-insights-dynamic-fields-reference.md](references\u002Fapp-insights-dynamic-fields-reference.md) | Dynamic fields (Properties\u002FCustomDimensions) and hidden business keys |\n| [references\u002Fdashboard-reference.md](references\u002Fdashboard-reference.md) | Real-Time (KQL) Dashboard create\u002Fupdate mechanics; generic tile patterns |\n| [references\u002Fbusiness-analysis-workflow.md](references\u002Fbusiness-analysis-workflow.md) | Full detail for the business-analysis half — Stages 13–17 (incl. correlation patterns & modeling appendices); load at the Stage 12 handoff |\n\n## Secrecy & scope guardrails\n\n- Do NOT expose Azure Log Analytics backend APIs to the user.\n- Do NOT expose Fabric \u002F DMTS \u002F Gateway connection internals or internal\n  endpoints to the user.\n- Do NOT request or disclose tokens, OAuth redirect codes, OAuth nonce values,\n  cookies, secrets, or internal implementation details.\n- Do NOT mention MCP, MCP servers, or MCP connectivity\u002Ftroubleshooting anywhere\n  in the user-facing flow. This Skill is self-contained.\n- Do NOT present undocumented \u002F browser-inspected \u002F internal connector APIs as\n  supported public APIs.\n- Do NOT claim OAuth Azure Monitor connector creation is available through a\n  public API — OAuth connector creation is **UI-guided only**.\n- Do NOT fabricate workspace names, table names, schema, item IDs, connection\n  IDs, or query results. Use only values returned by real discovery\u002Fqueries; use\n  clearly-labelled placeholders otherwise.\n- Do NOT ask the user for JOIN logic, KQL, bins, or thresholds upfront.\n- If the request is about SQL \u002F Data Warehouse or Lakehouse ingestion, warehouse\n  performance, or general Fabric DW best practices **unrelated** to Azure Monitor \u002F\n  Application Insights \u002F Log Analytics onboarding, state that it is **out of scope**\n  for this Azure Monitor skill and point the user to the appropriate warehouse\n  skill; do NOT act on it, run queries, or create resources.\n\n### Domain-agnostic rule\n\nBusiness entities named anywhere in this Skill or its references — bookings,\norders, customers, flights, revenue, tenants, payments, and similar — are\n**EXAMPLES ONLY**. The Skill MUST NOT infer the user's business domain from these\nexamples. The user's actual business entities MUST be discovered from real Fabric\ndata (Eventhouse \u002F KQL database \u002F Warehouse \u002F Lakehouse \u002F shortcuts) and confirmed\nwith the user before use.\n\nTo be explicit:\n\n- **Examples are illustrative only.** Every business-entity name in this Skill\n  and its references (e.g. bookings, orders, customers, revenue, flights,\n  tenants, payments) is a non-normative illustration, not a required or expected\n  entity.\n- **The Skill is domain-agnostic.** It applies to any business domain and assumes\n  none.\n- **The Skill MUST NOT infer or assume the user's business domain** from the\n  illustrative examples, from table or column names that happen to resemble an\n  example, or from any prior context.\n- **Business entities MUST be discovered from the user's actual data** and, until\n  discovered and confirmed, MUST be referred to generically — as *business\n  entities*, *business datasets*, *business KPIs*, or *business outcomes* — rather\n  than by any assumed domain-specific name.\n\n## EXECUTION CAPABILITY POLICY\n\nThe Skill is a guided staged workflow.\n\nActual execution depends on capabilities available in the current environment.\n\nPortal-guided instructions are allowed ONLY for OAuth Azure Monitor connector creation.\n\nThe Skill MUST NOT switch the entire onboarding flow to portal-guided instructions as a generic fallback.\n\nFor all non-OAuth stages, the Skill MUST first attempt to discover whether a supported execution path exists in the current environment.\n\nSupported execution paths may include:\n\n- Fabric REST APIs\n- Azure REST APIs\n- Fabric Actions\n- Azure CLI\n- Azure Resource Graph\n- Fabric REST **read-only** discovery via authenticated `az rest --method get`\n  against `https:\u002F\u002Fapi.fabric.microsoft.com\u002F...` (discovery\u002Fread-only only)\n- Other documented supported capabilities available to the agent\n\n**Log Analytics REST API reference (agent-facing).** When the Skill needs to perform or validate Azure Log Analytics operations, it may consult the official [Log Analytics REST APIs](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Floganalytics\u002F) reference to identify supported Log Analytics management, workspace, table, ingestion, and query APIs. This is agent-facing guidance only and does not relax the secrecy rule above.\n\nThese execution paths are distinct and MUST NOT be conflated:\n\n1. **Kusto \u002F KQL data-plane execution** — telemetry queries; optional, and MUST\n   NOT be used when disabled.\n2. **Azure ARM control-plane discovery** — resource\u002Fmetadata enumeration.\n3. **Fabric REST control-plane discovery** — a surfaced Fabric REST \u002F Fabric\n   Actions capability.\n4. **Arbitrary shell \u002F CLI execution** — out of scope (see Out-of-scope\n   constraints).\n5. **Fabric REST read-only discovery via authenticated `az rest --method get`** —\n   a narrow, permitted exception used ONLY for Fabric discovery\u002Fread against\n   `https:\u002F\u002Fapi.fabric.microsoft.com\u002F...`. It is GET-only, never creates,\n   updates, deletes, or modifies anything, and never exposes tokens, secrets,\n   auth headers, or sensitive payloads. This is NOT general shell\u002FCLI access.\n\nMCP unavailability alone does NOT mean execution capability is unavailable.\n\nUnavailability of any single execution path does NOT automatically imply the\ncapability is unavailable. Before declaring a capability unavailable, the Skill\nMUST evaluate ALL supported execution paths listed above and confirm that none is\navailable. Capability unavailable may be reported only after every supported\nexecution path has been evaluated.\n\nIf no supported execution path exists, the Skill MUST:\n\n1. Stop.\n2. Identify the missing capability.\n3. Explain why it is required.\n4. Identify which stage is blocked.\n5. Wait for user confirmation.\n\nThe Skill MUST NOT:\n\n- Replace validation with portal guidance.\n- Replace Mirrored Catalog creation with portal guidance.\n- Replace discovery, monitoring, refresh, shortcut creation, schema verification, or Operations Agent creation with portal guidance.\n- Claim an action completed when execution capability is unavailable.\n\n\n## PORTAL GUIDANCE POLICY\n\nThe Skill SHOULD prefer automated execution paths over UI-guided instructions:\n\n- Fabric REST APIs\n- Azure REST APIs\n- Fabric Actions\n- Azure CLI\n- Other supported automation mechanisms\n\nBefore providing UI-guided instructions the Skill MUST:\n\n1. Evaluate the available execution paths.\n2. Attempt supported execution paths where available.\n3. Explain which execution paths were evaluated.\n4. Explain why they cannot be used.\n\nOnly after those steps may the Skill provide UI-guided guidance.\n\nOAuth Azure Monitor connector creation remains an explicitly supported UI-guided\nscenario and does not require the above evaluation.\n\n\n## STRICT STAGED WORKFLOW CONTROLLER (ENFORCED)\n\nThe Skill MUST operate as a strict staged workflow controller.\n\n### Stages\n\n1. Intent and scope\n2. Log Analytics workspace selection\n3. Fabric workspace selection\n4. Identity selection and validation\n5. Connection resolution\n6. AzMon \u002F Mirrored Catalog item creation or reuse\n7. **Business Insight Capture** (optional here; may be deferred — intent MUST be\n   captured\u002Fconfirmed before schema verification, Stage 12)\n8. Azure Monitor table discovery\n9. Eventhouse \u002F KQL database **target** selection (default auto endpoint vs a\n   specific\u002Fnew Eventhouse)\n10. External Delta table registration planning\n11. External Delta table registration\n12. Schema and data verification\n13. Business data discovery and scoring\n14. Correlation planning\n15. Optional dashboard suggestion and creation\n16. Operations Agent instruction generation (optional — gated: only if the user\n    wants an agent)\n17. Optional Operations Agent creation \u002F validation\n\n### Execution rules\n\n- The Skill MUST track and enforce the current stage.\n- The Skill MUST NOT skip stages.\n- The Skill MUST NOT move to the next stage without completing the current one.\n\n### Stage visibility (REQUIRED in every user-facing response)\n\nBegin every response with this structure, written as **normal chat text (not a\ncode block)**:\n\n- **Current stage:** \u003Cstage name>\n- **What I found:** \u003Cshort summary>\n- **Next step:** \u003Cone clear action>\n\nThen close with a line inviting the user to confirm before continuing (e.g.\n*“Waiting for your confirmation to continue.”*).\n\nIf the current stage is unclear → **STOP** and ask the user where to resume.\n\n### Hard stop behavior\n\nAfter presenting any step that requires confirmation:\n\n- **STOP.**\n- **WAIT** for explicit user confirmation.\n- Do **not** continue automatically.\n\n### Confirmation gates (explicit confirmation REQUIRED before)\n\n- Selecting the identity for the flow (Stage 4) — recommend Service Principal,\n  but WAIT for the user's choice before validating.\n- Creating or reusing any resource that modifies Fabric.\n- Provisioning the Fabric workspace identity and assigning its Log Analytics\n  role (Stage 5, Mode B workspace-identity option) — WAIT before each write.\n- Selecting the Eventhouse target (a specific existing Eventhouse, or a new one).\n- Creating shortcuts in the chosen \u002F new Eventhouse — explicitly show the target\n  Eventhouse and exactly what will be created.\n- Proceeding from schema verification (Stage 12) to correlation planning\n  (Stage 14).\n- Creating or modifying a dashboard (present suggestions and WAIT for approval\n  first).\n- Building an Operations Agent at all (Stage 16) — explicitly ask whether the\n  user wants an agent before generating any instructions. If they do not, skip\n  Stages 16–17; the flow may end after the dashboard.\n- Generating final Operations Agent instructions if the correlation model has\n  not been confirmed.\n- Creating or modifying an Operations Agent.\n\n### Stage guardrails\n\n- External Delta table registration planning (Stage 10) MUST occur before schema verification or join\n  logic. If schema\u002Fjoin is attempted early → STOP and return to Stage 10.\n- External Delta table registration (Stage 11) MUST complete before schema verification.\n- Schema verification (Stage 12) MUST complete before correlation planning\n  (Stage 14).\n- If data is not queryable in Eventhouse via the registered external delta tables\n  → STOP → return to Stage 10\u002F11.\n- Correlation planning MUST NOT begin until external-table queryability is\n  confirmed.\n- Business Insight Capture (Stage 7) MAY be answered early or **deferred** so the\n  user can explore their data first, but intent MUST be captured\u002Fconfirmed\n  (intent provided OR a suggested direction explicitly selected) **before schema\n  verification (Stage 12)** and correlation planning. Never assume intent.\n\n### Out-of-scope constraints\n\nThe Skill MUST NOT run arbitrary shell\u002FCLI\u002Faz\u002FPowerShell commands, perform network\ndebugging, investigate server connectivity, or execute infrastructure\ntroubleshooting. These are out of scope unless explicitly part of the current\nstage.\n\n**Narrow exception — Fabric REST read-only discovery.** The Skill MAY use an\nauthenticated `az rest --method get` call ONLY for Fabric REST read-only\ndiscovery, and ONLY when ALL of the following hold:\n\n- The endpoint is `https:\u002F\u002Fapi.fabric.microsoft.com\u002F...`.\n- The HTTP method is **GET** only.\n- The operation is discovery \u002F read-only only.\n- Nothing is created, updated, deleted, or modified (no Fabric items, shortcuts,\n  mirrored catalog items, or connectors via CLI).\n- No tokens, secrets, raw auth headers, or sensitive payloads are exposed.\n- The Skill clearly states the capability path used.\n\nThis exception does NOT permit arbitrary shell\u002FCLI execution, non-GET `az rest`\ncalls, or use of the Kusto \u002F KQL data-plane when disabled.\n\n**Narrow exception — Fabric workspace-identity provisioning + LA role assignment\n(Mode B only).** In the Mode B workspace-identity option, the Skill MAY use\nauthenticated `az` calls to detect\u002Fprovision the workspace identity and, when the\ncaller is permitted, assign its Log Analytics role, limited to:\n\n- `GET https:\u002F\u002Fapi.fabric.microsoft.com\u002Fv1\u002Fworkspaces\u002F{id}` (detect), and\n- `POST https:\u002F\u002Fapi.fabric.microsoft.com\u002Fv1\u002Fworkspaces\u002F{id}\u002FprovisionIdentity`\n  (provision) plus GET polling of its long-running operation, and\n- `az role assignment list` (check) and `az role assignment create` at the Log\n  Analytics workspace scope to grant the identity **Owner**, but ONLY when the\n  caller holds `Microsoft.Authorization\u002FroleAssignments\u002Fwrite` there.\n\nEach write is confirmation-gated (Stage 5), touches only the workspace identity\nand its LA role (nothing else), exposes no tokens\u002Fsecrets\u002Fauth headers, and\nthe Skill states the capability path used. If the caller lacks role-assignment\npermission, the Skill MUST NOT force it — it instructs the user \u002F an admin to run\nthe assignment instead. This does NOT permit any other non-GET `az rest` calls or\nany broader `az` usage.\n\n### Response style (ENFORCED)\n\nBehave like a **guided product experience**, not a backend debugger.\n\n- Use concise, business-friendly language.\n- Never show internal implementation steps (CLI, REST, tokens, API calls) unless\n  the user explicitly asks and the API is documented\u002Fsupported.\n- Never expose internal limitations (\"public API limitation\", \"CredentialType\n  not supported\", \"headless OAuth failure\") in user-facing output.\n- Never ask for secrets, OAuth codes, cookies, redirect URLs, tokens, or nonce\n  values.\n- Summarize findings. Do NOT expose endpoint experimentation, API probing,\n  OpenAPI \u002F schema exploration, retry investigations, or low-level debugging\n  details in user-facing output unless the user explicitly asks for them.\n- After each stage: present a short summary, ask for explicit confirmation,\n  STOP and WAIT.\n\n---\n\n## Stage 1 — Intent and scope\n\nConfirm what the user wants: onboard observability data into Fabric, explore a\nbusiness insight, or both. Capture (in plain language) any workspace names or\nbusiness outcome they already mention — but do not yet drive correlation.\n\n## Stage 2 — Log Analytics workspace selection\n\nApplication Insights telemetry is queried through its backing Log Analytics\nworkspace (workspace-based Application Insights). Help the user pick the correct\nLog Analytics \u002F Application Insights-backed workspace.\n\n- If the user did not provide a workspace, ask for the subscription, then present\n  a concise list of supported workspaces (name + resource group + location).\n  Never expose raw API responses.\n- Prefer a case-insensitive name filter over listing everything when the\n  subscription has many workspaces.\n\n### Exact-name-not-found fallback (REQUIRED)\n\nWhen the user names a workspace and no **exact** match exists, the Skill MUST NOT\nfail. Instead:\n\n1. Ask for the subscription if not provided (do not guess).\n2. Offer similar workspaces (names that **contain** the term or are a close\n   case-insensitive\u002Fpartial match). Broaden the search if a narrow filter returns\n   nothing.\n3. Present candidates as a concise numbered list (name + resource group +\n   location), then STOP and wait for the user to pick.\n4. If exactly one similar workspace is found, still confirm before proceeding.\n5. If none is found, say so plainly and ask for a different subscription or term.\n\nNever fabricate a workspace name or GUID — only offer real discovered\nworkspaces.\n\n## Stage 3 — Fabric workspace selection\n\nHelp the user choose the target Fabric workspace (display name + id). Use a\ncase-insensitive substring filter when helpful. Read-only; nothing is created\nhere. Never expose raw API responses or tokens.\n\n### Fabric Workspace Discovery & Capability Resolution Policy (REQUIRED)\n\nFabric workspaces are **not** Azure Resource Manager resources, so absence of an\nautomatic enumeration path does NOT mean no Fabric workspace exists. **Never\nterminate the workflow early**: if automatic discovery fails, ask the user for a\nFabric Workspace **Name**, **ID**, or **URL**, validate it as far as the available\ncapabilities allow, and continue. Never auto-select a workspace, never fabricate a\nworkspace or a validation result, and mark Stage 3 BLOCKED only after every\ndiscovery mechanism AND every user-supplied resolution path has been exhausted.\n\nFollow the full discovery order, the interpretation rules, and the UI-guided\nlast-resort boundary in\n[references\u002Fworkspace-discovery-policy-reference.md](references\u002Fworkspace-discovery-policy-reference.md).\n\n## Stage 4 — Identity selection and validation\n\n### Identity selection (REQUIRED first — WAIT for the user)\n\nValidation MUST run against the **identity that will actually perform the flow**,\nso the identity is chosen **before** any validation check — not deferred to\nStage 5. Do NOT silently reuse whatever `az` happens to be signed in as.\n\nPresent the choice and STOP — ask this as **normal chat text (a plain numbered\nlist, not a code block)**:\n\nWhich identity should I use for this onboarding?\n\n1. **Service Principal (recommended)** — automated, non-interactive; best for\n   repeatable runs and CI. Requires tenant id, app\u002Fclient id, and a securely\n   provided secret\u002Fcertificate.\n2. **Your user account (interactive sign-in)** — if you prefer to run as\n   yourself, or a Service Principal is not available.\n\nInvite the user to reply **1** or **2**; note that Service Principal is\nrecommended.\n\n- **Recommend Service Principal**, but let the user choose. If the user asks to\n  sign in as themselves, allow interactive user login and continue as the user.\n- After the choice, confirm the effective identity (e.g. `az account show`) so\n  validation runs against the right principal. If it does not match the chosen\n  identity, stop and resolve the sign-in before validating.\n- Carry the chosen identity forward: Stage 5 connection resolution and all later\n  Fabric-modifying actions use this same identity.\n\n### Validate against the chosen identity\n\nBefore any creation, verify **for that identity**:\n\n- The workspace exists.\n- The **chosen identity** has the required Log Analytics access.\n- The **chosen identity** has sufficient Fabric workspace permission to operate\n  (and, for a Service Principal, that the tenant setting *\"Service principals can\n  use Fabric APIs\"* is enabled).\n- Surface early that connection detection\u002Freuse will later need the chosen\n  identity to hold **a role** on the Azure Monitor connection (a **User** role is\n  enough; **Owner** is not required), so a permission gap is caught here rather\n  than at Stage 5.\n- For the Mode B **workspace-identity** connection option (Stage 5), the chosen\n  identity must be a workspace **Admin** (required to provision the workspace\n  identity). The Skill can assign the identity's Log Analytics role itself\n  when the caller holds role-assignment permission (**Owner** \u002F **User Access\n  Administrator**) on the LA scope; otherwise it instructs the user. Surface both\n  early.\n\nIf validation fails, summarize which checks passed\u002Ffailed in user terms, explain\nthe missing capability, and offer to try another workspace, grant the missing\npermission, or switch identity. See\n`references\u002Fazmon-fabric-api-reference.md` for supported-scope rules.\n\n### Validation capability discovery (REQUIRED)\n\nBefore declaring validation capability unavailable, the Skill MUST determine whether the environment provides one of the following:\n\n- Fabric REST APIs\n- Azure REST APIs\n- Fabric Actions\n- Azure CLI\n- Azure Resource Graph\n\nMCP availability is only one possible execution path.\n\nThe Skill MUST report validation capability unavailable only after evaluating all supported execution paths and finding none.\n\nBefore declaring validation capability unavailable, the Skill MUST:\n\n1. Determine whether another supported execution path exists.\n2. Attempt capability discovery using all supported mechanisms available\n   in the current environment.\n3. Only after all supported mechanisms have been evaluated and none are\n   available may the Skill declare the capability unavailable.\n\n## Stage 5 — Connection resolution\n\nTwo connection modes are supported. **Prefer Service Principal (Mode A)** — the\nautomated, non-interactive path — as the default. Fall back to **OAuth (Mode B)**\nonly when Service Principal is unavailable or the user explicitly requests it.\nKeep the two modes **separate**. Never route OAuth through Service Principal\nlogic, and never route Service Principal through OAuth \u002F interactive sign-in\nlogic. See\n[references\u002Fazmon-fabric-api-reference.md](references\u002Fazmon-fabric-api-reference.md)\nfor the authoritative connector rules **and the exact documented connection API\nendpoints and payload shapes** (List \u002F Get \u002F Create Connection + List Supported\nConnection Types). Use those documented shapes — do **not** guess a connection\npayload or go searching general docs. When the Azure Monitor connector's exact\n`type` \u002F `creationMethod` \u002F `parameters` are unknown, resolve them from the\n`supportedConnectionTypes` endpoint rather than assuming.\n\n### Mode selection (REQUIRED order)\n\nThe identity was already chosen and validated in **Stage 4 (Identity selection)**.\nUse that identity here — do not re-prompt unless the user changes it. Map the\nchosen identity to its connection mode:\n\n1. **Service Principal → Mode A.** If a matching Service Principal connector\n   already exists for the same Log Analytics workspace, reuse it. Otherwise, when\n   the required Service Principal inputs are available (tenant id, app\u002Fclient id,\n   and a securely-provided secret\u002Fcertificate reference), create-or-reuse the\n   Service Principal connector automatically — no UI step.\n2. **User \u002F interactive → Mode B.** Use when the user chose to sign in as\n   themselves, the Service Principal is unavailable, or the tenant disallows it.\n   In Mode B, first prompt the user to choose the connection authentication method\n   — interactive OAuth or workspace identity (see \"Mode B — choose connection\n   authentication\" below) — then route to that sub-branch.\n\n### Connection visibility caveat (applies to BOTH modes)\n\nTo be **discoverable**, a connection must have **at least one role assigned to the\ncalling identity** — whether the **Service Principal** (Mode A) or the **user**\n(Mode B). Any assigned role makes it appear in the listing and reusable; a\n**User** role is enough for detection and reuse, and **Owner** is only needed to\n**manage \u002F modify \u002F delete** it. If the caller holds **no role** on a connection,\nthe API will **not** return it — that is **by design**, not a failure.\n\nTherefore, if the search finds **no** matching connection, the Skill MUST NOT\nimmediately conclude the connection does not exist. It MUST first consider that\nthe connection may exist but simply be **invisible to the current identity\nbecause it holds no role on it**, and:\n\n- State that a matching connection was not found **for the current identity**,\n  and that this can mean either (a) no such connection exists, or (b) one exists\n  but the calling Service Principal \u002F user holds **no role** on it.\n- Advise assigning the Service Principal or user **a role** on the existing Azure\n  Monitor connection (for the same Log Analytics workspace) — a **User** role is\n  enough for detection and reuse — then re-run detection. (If a Service Principal\n  still can't see it after a lower role is granted, see the Service Principal note\n  in\n  [references\u002Fazmon-fabric-api-reference.md](references\u002Fazmon-fabric-api-reference.md).)\n- Only after this permission possibility has been surfaced may the Skill proceed\n  to create a new connector (Mode A) or the OAuth create-once guidance (Mode B).\n\nNever fabricate a connection or claim one exists without a real listing match.\n\n### Portal guidance boundary\n\nPortal-guided instructions are permitted ONLY for OAuth Azure Monitor connector creation.\n\nPortal guidance is NOT an allowed fallback for:\n\n- LAW validation\n- Fabric workspace validation\n- Connection detection\n- Connection reuse\n- Service Principal connector creation\n- Mirrored Catalog item creation\n- Discovery\n- Monitoring\n- Refresh\n- Eventhouse shortcut creation\n- Schema verification\n- Operations Agent creation\n\nIf execution capability for these actions is unavailable, the Skill MUST stop and identify the missing capability.\n\n### Mode A — Service Principal (automated create-or-reuse, default)\n\nPresent this as **\"connect using Service Principal\"** — the automated,\nnon-interactive path (no user login, no UI step). This is the **preferred**\ndefault; attempt it before OAuth.\n\n- **Idempotent create-or-reuse**: if a matching Azure Monitor Service Principal\n  connector already exists for the same Log Analytics workspace (same data source\n  path + Service Principal credential type), reuse it — never create a duplicate.\n- Only **one** connector is created per run.\n- **Never** reuse a non-Service-Principal (e.g. OAuth) connector in this mode.\n- **Never** ask the user to paste a client secret into chat. Secrets come from\n  **environment variables or Key Vault references** only, are never echoed,\n  logged, exposed, or included in generated instructions.\n- If required Service Principal inputs are missing, describe **what** is missing\n  (tenant id, app\u002Fclient id, and a securely-provided secret reference) using\n  presence checks only — never request the secret value in chat. Only when\n  Service Principal inputs cannot be provided, fall back to OAuth (Mode B).\n\nAutomation boundary: infrastructure (connector create-or-reuse, mirrored item\ncreation) is automated; **business decisions** (Eventhouse\u002FKQL DB selection,\nshortcut creation) always require explicit user confirmation.\n\n### Mode B — choose connection authentication (REQUIRED prompt)\n\nWhen the chosen identity is User \u002F interactive (Mode B), the connection can be\ncreated two ways. Before detecting or creating anything, present this choice as\n**normal chat text (a plain numbered list, not a code block)** and STOP for the\nuser's answer:\n\nHow should I authenticate the Azure Monitor connection?\n\n1. **Interactive sign-in (OAuth)** — you sign in once in Fabric → Manage\n   Connections; the connection uses your organizational account.\n2. **Workspace identity (no secrets)** — Fabric's automatically-managed workspace\n   identity is used as the credential; you grant it access on your Log\n   Analytics workspace. No secret to handle.\n\nRoute to the matching sub-branch below — **1 → Mode B (OAuth)**, **2 → Mode B\n(Workspace identity)**. Keep the two strictly separate. If the user has no\npreference, note that workspace identity avoids interactive sign-in and secret\nhandling, but WAIT for their choice — never auto-select.\n\n### Mode B — OAuth (UI-guided only, fallback)\n\nUse this sub-branch when the user picked option 1 above, i.e. only when Service\nPrincipal (Mode A) is unavailable or the user explicitly requests OAuth. OAuth\nconnector **creation** is UI-guided only (Fabric → Manage Connections) — the Skill\nnever creates one through an API; it only **detects and reuses** an existing\nconnection, read-only, and only when the Log Analytics workspace matches exactly.\n\nFollow the full detection order, reuse rules, and user-facing wording in\n[references\u002Foauth-connection-reference.md](references\u002Foauth-connection-reference.md).\nKeep this strictly separate from Mode A.\n\n### Mode B — Workspace identity (no secrets)\n\nUse this sub-branch when the user picked option 2 above. Fabric's\nautomatically-managed **workspace identity** is used as the connection credential\n(no secret). This flow provisions the identity if needed, ensures it has a\nsufficient Log Analytics role — **assigning it automatically when the caller is\npermitted, otherwise instructing the user** — then creates the connection.\n\nFollow the full sequence, endpoints, gates, and payloads in\n[references\u002Fworkspace-identity-connection-reference.md](references\u002Fworkspace-identity-connection-reference.md).\nKey gates: provisioning the identity is confirmation-gated (caller must be\nworkspace **Admin**); the LA role is assigned by the Skill when the caller\nholds role-assignment permission (else the Skill instructs and WAITs for\nconfirmation) — both writes are confirmation-gated; then create the connection\nusing the `WorkspaceIdentity` credential type. Keep this strictly separate from\nMode A.\n\n## Stage 6 — AzMon \u002F Mirrored Catalog item creation or reuse\n\nCreate the Azure Monitor **Mirrored Catalog** item in the target Fabric\nworkspace, or reuse an existing matching item. This is a Fabric-modifying action\n→ confirm first. Supported Mirrored Catalog operations (item CRUD, definition,\ndiscovery, monitoring, refresh) are documented in\n[references\u002Fmirrored-catalog-reference.md](references\u002Fmirrored-catalog-reference.md).\n\n### Service Principal item-creation (IMPORTANT — prefer reuse; observed fallback)\n\nPer Microsoft Learn, the **Create Mirrored Catalog** API lists **service principals\nand managed identities** as supported identities for create, so a Service Principal\ncreate is **documented as supported** and is not an absolute platform limitation.\n\n> **Observed fallback.** Some Service Principal runs have nonetheless seen the\n> item **create** rejected under an application-only token (the underlying\n> item-creation path can run **on-behalf-of** a signed-in user). Treat this as\n> **observed** tenant behavior, not a documented rule, and keep the docs-accurate\n> default: attempt create under the SP, and only fall back to a user (delegated) \u002F\n> UI context if the create call is actually **denied or unavailable**.\n\nGet, list, **update**, discovery, monitoring, refresh, and shortcut operations all\nwork under an application-only SP token once the item exists.\n\nConsequently, when running under a Service Principal, the Skill MUST:\n\n- **Prefer reuse** — reuse an existing Azure Monitor Mirrored Catalog item (and\n  its existing connection) that the SP can see and operate on. This is the\n  preferred path: build on an already-created item + connection rather than\n  creating a new one. The SP can then **update** and operate that item normally.\n- If no reusable item exists, **attempt to create the item under the SP** (the\n  create API documents SP\u002Fmanaged-identity support). Only if that create is\n  **denied or unavailable** (the observed fallback above), **create the item in a\n  user context** — either from the **Fabric UI**, or via a **user (delegated)\n  sign-in** — preferably seeded from an existing item and connection. After the\n  item exists, the Service Principal can resume the automated flow (update,\n  discovery, monitoring, refresh, shortcuts) on that item.\n- Never claim the item was created by the SP when the create actually occurred in\n  a user\u002FUI context.\n\nDownstream Mirrored Catalog operations (update, discovery, monitoring, refresh)\nremain available to the Service Principal once the item exists.\n\n### Table selection via scope (choosing which tables the item mirrors)\n\nThe item does **not** take a free-form list of table names — it mirrors by\n**`scope`** (a namespace hierarchy path in the definition), and that scope MUST be\na **`Selectable`** value returned by the **List Scopes** discovery API. To target\nonly the tables the user wants:\n\n- Call **List Scopes** and choose a `Selectable` scope for the item. If the user\n  already knows the target tables, pick the **narrowest `Selectable` scope** that\n  covers them. If there is no intent yet (the user wants to explore first),\n  create with a **broader scope** and optionally **re-scope** narrower later —\n  updating the item definition — once intent is captured. Use only real returned\n  scope values — never fabricate a scope or table name.\n- If the narrowest available `Selectable` scope is **broader** than the requested\n  set, the item **will also mirror the extra sibling tables** under that scope —\n  mirroring cannot exclude individual siblings. State this plainly and get\n  explicit confirmation before creating.\n- For an existing\u002Freused item, read its current definition scope before assuming\n  it matches the request; do not fabricate definition fields.\n\n### Default mirror set (REQUIRED starting point)\n\nUnless the user specifies otherwise, the **default set of tables to mirror** is\nevery table that (a) appears in real **List Scopes \u002F Discovery** output and (b)\nmatches one of these name prefixes (case-insensitive; tolerate the `_CL`\ncustom-table suffix):\n\n- `App*` — Application Insights tables\n- `OTel*` — OpenTelemetry-native tables (e.g. `OTelLogs`)\n- `XD*` — custom, security-related log tables\n\nThen **ask the user whether they want any additional tables** before creating\n(confirmation gate — present the resolved set and WAIT).\n\n- Match prefixes against **real discovered tables only** — never invent a table.\n  If a prefix matches nothing, omit it silently.\n- Resolve the default set to the **narrowest single `Selectable` scope that covers\n  all matched tables**. If that scope also pulls in **extra sibling tables** beyond\n  the default set, **list the extras explicitly**, explain that siblings cannot be\n  individually excluded, and get confirmation before creating. Once confirmed, the\n  extras are **expected** — they are not failures at the Stage 8 equality check.\n- Adding user-requested tables may widen the chosen scope — re-resolve and\n  re-disclose.\n- If **none** of `App*` \u002F `OTel*` \u002F `XD*` match any discovered table, fall back to\n  presenting all\u002Frepresentative discovered tables (explore-first) and let the user\n  choose.\n- **`XD*` security tables** are only considered **after** the workspace has passed\n  Stage 4's validation (a supported, validated workspace); an unsupported-workspace\n  block takes precedence and table selection MUST NOT be used to bypass it.\n- **On reuse:** read the existing item's current scope and compare its mirrored\n  set to the default set. If not fully covered, offer to **re-scope** (update the\n  item definition) to add the missing `App*`\u002F`OTel*`\u002F`XD*` tables, disclosing any\n  extra siblings — never re-scope silently; confirm first.\n\nThe confirmed set (default + confirmed siblings + any tables the user adds) becomes\nthe **expected set** for the Stage 8 requested-vs-mirrored equality check.\n\n### First-time mirroring latency (disclosure — REQUIRED)\n\nFor a **first-time mirrored workspace**, tell the user upfront that mirrored\ntables and data typically take **around 5 minutes** to materialize and become\nqueryable after the item is created. Until then, discovery\u002Fqueries may return\nempty or partial results — this is **expected**, not an error. Do not declare\ntables missing during this window: verify mirror\u002Frefresh status, wait, and\nre-check before concluding anything.\n\nAfter the item is created or reused, optionally capture business intent now\n(Stage 7) if the user already has a goal; otherwise proceed to table discovery\nand exploration and capture intent before schema verification (Stage 12).\n\n## Stage 7 — Business Insight Capture (optional here; deferrable)\n\nIf the user already has a business question, capture it now so table discovery\n(Stage 8) and Eventhouse scoring (Stage 9) can be guided by it. If they don't,\nthis stage is **optional right now** — the user may explore their data first\n(Stages 8–11) and provide intent later. Either way, intent is **MANDATORY before\nschema verification (Stage 12)** and correlation (Stage 14); capturing it early is\njust an optimization that focuses discovery.\n\nWhen capturing intent, ask in business language, e.g.:\n\n- Did service availability issues impact bookings?\n- Did request latency reduce customer conversions?\n- Did exceptions affect revenue or orders?\n- Did dependency failures impact specific customers, tenants, regions, or\n  flights?\n- Did incidents affect SLA, usage, or customer activity?\n- Did traffic drops correlate with usage KPI degradation?\n\n### Enforcement\n\nThe Skill MUST NOT proceed to schema verification (Stage 12) or business\n**correlation** (Stage 14) without either:\n\n- (a) user-provided business intent, OR\n- (b) explicit user selection from suggested directions.\n\nIntent may be provided here or after exploration, but it MUST exist before\nStage 12. Never assume intent.\n\n### Fallback (when the user is unsure \u002F vague \u002F no exact match)\n\nSuggest 3–5 directions, each framed as **observability signal → business\nimpact**, and ask the user to choose one:\n\n1. Availability failures → booking completion impact.\n2. Request latency → conversion or checkout drop.\n3. Exceptions → failed orders or revenue at risk.\n4. Dependency failures → customer \u002F tenant \u002F region impact.\n5. Traffic drops → usage KPI degradation.\n\n### Important distinction\n\nCapturing intent early is **allowed but optional** — it MUST exist before schema\nverification (Stage 12). Either way, the Skill MUST NOT generate correlation logic\nyet. Correlation logic only comes after shortcuts exist, schema is verified, data\nis queryable, dynamic fields are inspected, join candidates are validated, and\ndata freshness is checked (Stages 10–14).\n\n## Stage 8 — Azure Monitor table discovery\n\nBrowse candidate Azure Monitor \u002F Application Insights tables. **If a business goal\nwas captured (Stage 7),** filter to the tables relevant to it. **If there is no\nintent yet (explore-first),** present all\u002Frepresentative discovered tables so the\nuser can browse. Use only real discovered scope\u002Ftable values — never fabricate\ntable names. Use\n[references\u002Ftelemetry-table-reference.md](references\u002Ftelemetry-table-reference.md)\nto explain what each table means in business terms and which tables best fit the\nstated goal (or what each table offers when exploring).\n\n### Discovery API fallback policy (REQUIRED)\n\nThe **primary** discovery mechanism is the Mirrored Catalog Discovery APIs. If\ndiscovery appears incomplete, do NOT immediately conclude tables are missing or\nswitch to alternative metadata paths. First:\n\n1. Verify mirror status.\n2. Verify refresh \u002F sync status.\n3. Verify discovery scope.\n4. Retry discovery.\n\nOnly after these checks may the Skill evaluate alternative metadata paths. See\n[references\u002Fmirrored-catalog-reference.md](references\u002Fmirrored-catalog-reference.md).\n\n### Requested-vs-mirrored set-equality check (REQUIRED once a specific table set is requested)\n\nThis check applies once a **requested table set exists** — whether specified up\nfront or after intent is captured later. When the **default mirror set** (Stage 6)\nor a user-adjusted set is in effect, that set is the **requested set** for this\ncheck, and any sibling tables disclosed and confirmed under the narrowest-common-\nscope rule are **expected** (compare against the chosen scope's expected contents,\nnot a bare table list — do not report confirmed siblings as failures). When the\nuser asked for a specific set of\ntables, verify the item mirrors\n**exactly** that set — use **equality, not subset** (\"my tables are present\" is not\nenough). Compare the **actually-mirrored** table set (from Discovery \u002F Monitoring)\nagainst the **requested** set and report the result:\n\n- **Extra tables present** → the chosen scope is broader than requested. Report the\n  extras and, if a narrower `Selectable` scope exists, offer to re-scope; otherwise\n  state that the source only exposes a broader scope and the extras are\n  unavoidable.\n- **Requested tables missing** → the mirror may not have materialized yet. Verify\n  mirror\u002Frefresh status, run a **Refresh\u002Fsync**, wait, then re-check — do not\n  declare them absent prematurely.\n- **Exact match** → confirm and proceed.\n\nNever fabricate the mirrored table set; enumerate it from real Discovery \u002F\nMonitoring results only.\n\n## Stage 9 — Eventhouse \u002F KQL database target selection\n\nAsk the user which Eventhouse should host the LA-table shortcuts. Present these\noptions as **normal chat text (not a code block)** and require explicit\nconfirmation:\n\n- **A — A specific existing Eventhouse** (e.g. one that already holds business\n  data you want to correlate with). The Skill creates LA-table shortcuts\n  **there**, colocating telemetry with the business data.\n- **B — A new Eventhouse.** The Skill creates it and the LA-table shortcuts;\n  starts empty.\n\nBoth options are writable and support the Operations Agent path (they can host\n`IncidentBins` materialization).\n\nRun **Eventhouse Recommendation Mode** to inform the choice — discover available\nEventhouses, inspect their contents (tables, shortcuts, KQL databases), and score\neach by relevant business tables, relevant telemetry tables, existing shortcuts,\nqueryable tables, KQL database availability, and data freshness. **When the\nuser's goal is correlating telemetry with existing business data, recommend\noption A** (colocation); otherwise a new Eventhouse is a clean starting point.\nPresent as normal chat text:\n\n- **Recommended target:** \u003CA ‹EventhouseName› | B new>\n- **Reason:** \u003Cwhy>\n- **Alternatives:** \u003Clist>\n\nThe Skill MUST NOT auto-select. Present the recommendation, state exactly what\nwill be created, and require explicit confirmation. See\n[references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md).\n\n## Stage 10 — External Delta table registration planning\n\nPlan **external Delta table registrations** for the resolved table set into the\n**chosen\u002Fnew Eventhouse** — name the target Eventhouse in the plan header —\n**before** any schema verification or join logic. Present the plan and STOP for\nconfirmation.\n\nKey rules (see the shortcuts reference for detail):\n\n- Queryability in a KQL database comes from registering each table as an\n  **external Delta table** pointing at the mirrored item's OneLake\n  `Tables\u002Fdbo\u002F\u003CTable>` path — **not** from the Core Shortcuts API (which creates a\n  link only). Query via `external_table('\u003Cname>')`.\n- Plan, per table: exact name, OneLake `Tables\u002Fdbo\u002F\u003CTable>` path, target KQL\n  database, and that the schema will be read from the table's Delta log.\n\n### Query acceleration policy — external delta tables (MUST — always `true`)\n\nQuery acceleration is a **policy on external delta tables** (set via\n`.alter external table … policy query_acceleration`), **not** a shortcut-object\nproperty. Every registered external delta table gets **acceleration enabled\n(`true`)** — not optional. Include an `Acceleration Enabled (always Yes)` plan-table\ncolumn; if the environment can't support it, surface that rather than registering\nwithout the policy. Full policy in\n[references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md#external-delta-table-query-acceleration-policy-must--always-true).\n\n## Stage 11 — External Delta table registration\n\nOnly after explicit confirmation, register each table as an **external Delta\ntable** in the target KQL database (report which one): read the table's schema\nfrom its Delta log, map Delta → Eventhouse types, and run `.create external table\n['\u003CTable>'] (\u003Ccols>) kind=delta ( h@'\u003COneLake Tables\u002Fdbo\u002F\u003CTable> path>;impersonate' )`\nvia `POST {clusterUri}\u002Fv1\u002Frest\u002Fmgmt`. Then verify with `.show external tables` +\n`external_table('\u003CTable>') | take 1`. The Core Shortcuts API is **not** required\nfor queryability (it creates a link only). If a table is not queryable → STOP and\nreturn to planning \u002F registration. See\n[references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md)\nfor the schema-read, type mapping, and command template.\n\nWhen registering ANY external delta table, **always enable the query acceleration\npolicy (`true`)** per the\n[Query acceleration policy](references\u002Feventhouse-shortcuts-reference.md#external-delta-table-query-acceleration-policy-must--always-true),\nand report the resulting status (expected: enabled).\n\n## Stage 12 — Schema and data verification (REQUIRED before correlation)\n\nNever build correlation logic on assumptions or screenshots. Before proposing any\njoin, bin, or threshold, verify against the **actual** KQL database. Business\nintent MUST already be captured\u002Fconfirmed before this stage — if it was deferred\nat Stage 7, capture it now (using the Stage 7 questions\u002Ffallback) before\nproceeding, since the telemetry-source selection below is scored by goal\nrelevance. Never assume intent.\n\n### Preconditions\n\n1. Operational telemetry tables are available in the Eventhouse \u002F KQL database.\n2. Business tables are available in the same database or queryable via shortcuts.\n3. Tables are **queryable**, not just visible in OneLake.\n4. Schema retrieved via `getschema`.\n5. Dynamic fields inspected and sampled.\n6. Candidate join keys extracted from top-level **and** dynamic columns.\n7. Join keys validated with **non-zero** match results (when a direct join is\n   proposed).\n8. Data freshness verified.\n9. Time window aligned to the real data range.\n10. Relevant categorical values confirmed from real data where rules depend on\n    them.\n\n### Steps\n\n> **Query convention.** Mirrored telemetry tables are **external tables** — query\n> them via `external_table('\u003Cname>')` (they do not appear in `.show tables`);\n> business tables that are **managed** in an Eventhouse use their bare\n> name.\n\n1. **Retrieve real schema.** For each table:\n   `external_table('\u003CTableName>') | getschema | project ColumnName, ColumnType`.\n   Use authoritative column names\u002Ftypes — not names guessed from screenshots or\n   table names.\n2. **Inspect and sample dynamic fields.** Business join keys are often nested in\n   dynamic columns (`Properties`, `CustomDimensions`, `Details`, `Measurements`,\n   `Payload`, `Context`). Sample rows and inspect keys. See\n   [references\u002Fapp-insights-dynamic-fields-reference.md](references\u002Fapp-insights-dynamic-fields-reference.md).\n3. **Extract candidate business identifiers** with explicit KQL\n   (`tostring(Properties.BookingId)`, with casing fallbacks via `coalesce`).\n4. **Validate join keys against real data.** Prove a candidate joins — run the\n   join and confirm non-zero matches:\n\n   ```kusto\n   external_table('AppEvents')\n   | extend BookingId = tostring(Properties.BookingId)\n   | where isnotempty(BookingId)\n   | join kind=inner (Bookings | project BookingId = tostring(BookingId)) on BookingId\n   | summarize MatchedRows=count(), DistinctBookings=dcount(BookingId)\n   ```\n\n   Non-zero → **direct join, high confidence**. Zero → the key is wrong or data\n   doesn't overlap; find the real one.\n5. **Check freshness and align the window.**\n   `external_table('\u003CTableName>') | summarize Rows=count(), MinTime=min(TimeGenerated), MaxTime=max(TimeGenerated)`.\n   Do not assume `ago(1h)`; use a window covering the actual data range and\n   explain it in user terms.\n6. **Confirm categorical values** used by rules\n   (`external_table('\u003CTable>') | summarize count() by \u003Cfield>`) so impact rules\n   use real categories.\n\n### Telemetry source selection framework (REQUIRED)\n\nTelemetry source selection MUST be **data-driven**. Before selecting a correlation\nmodel, the Skill MUST inspect ALL candidate telemetry sources discovered (e.g.\nAppEvents, AppExceptions, AppRequests, AppDependencies, AppTraces, AppPageViews,\nAppBrowserTimings, AvailabilityResults, and any other telemetry source present) —\nnot just one.\n\nScore each candidate telemetry source by:\n\n1. Business identifiers discovered.\n2. Dynamic-field richness.\n3. Direct-join confidence.\n4. Validated match count.\n5. Business-process context.\n6. Relevance to the selected business goal.\n\nSelect the highest-scoring telemetry source. The Skill MUST NOT automatically\nprioritize AppExceptions, and MUST NOT automatically prioritize AppEvents — the\nwinner is whichever source scores highest against real data.\n\n### Exit criteria (MANDATORY)\n\nBefore Stage 14, ALL must hold: schema retrieved via `getschema`; join keys\nvalidated with non-zero matches (when a direct join is used); freshness verified\nand window aligned; relevant categorical values confirmed. If any fails → STOP,\ndo not proceed.\n\n### Handoff (MANDATORY)\n\nPresent a concise summary (verified join keys, match results, business impact if\nany, data time window). Then ask: \"Do you want to continue to business analysis\n(impact modeling, a dashboard, and optionally an Operations Agent) based on this\nverified model?\" HARD STOP and wait. On confirmation, continue with Stages 13–17\nas defined in\n[references\u002Fbusiness-analysis-workflow.md](references\u002Fbusiness-analysis-workflow.md).\n\n## Stages 13–17 — Business-oriented analysis (defined in the reference)\n\nThe business-oriented analysis half (business data discovery\u002Fscoring, correlation\nplanning, an optional Real-Time KQL dashboard, and an optional gated Operations\nAgent) is defined authoritatively in\n[references\u002Fbusiness-analysis-workflow.md](references\u002Fbusiness-analysis-workflow.md)\n(with Appendices A–B) and loaded only when the user opts in at the Stage 12\nhandoff. On opt-in, **do not work from memory** — open that file and follow\nStages 13–17 exactly; the controller still tracks and enforces these stages, their\norder, hard stops, and confirmation gates (including dashboard-before-agent and\nthe Stage 16 \"do we even want an agent?\" gate).\n\n## Troubleshooting (user-facing)\n\n- **\"No playbook generated\" \u002F cannot compute a field** → the instructions\n  described fields conceptually. Add the explicit KQL materialization query, add\n  per-field KQL definitions, ensure alert rules reference actual output columns,\n  add dynamic-field extraction, and clarify join keys\u002Fidentifiers. Do not just\n  reword prose.\n- **Start succeeds but no Teams alert arrives** → likely no data matched the\n  rule. Switch to POC\u002Fdebug thresholds; explain no data may have matched. Do not\n  imply platform failure without evidence.\n\n## Must \u002F Prefer \u002F Avoid\n\n### Must\n- Enforce stages, hard stops, and confirmation gates.\n- Keep OAuth (UI-guided) and Service Principal (automated create-or-reuse)\n  strictly separate.\n- Validate permissions before creation.\n- Verify schema, dynamic fields, join matches, and freshness before correlation.\n- Provide explicit KQL in Operations Agent instructions.\n\n### Prefer\n- Service Principal (automated) over OAuth (UI-guided) for connection\n  resolution; fall back to OAuth only when Service Principal is unavailable.\n- Direct joins over time-window correlation.\n- Real discovered values over anything guessed.\n- Business-language confirmation over technical questions.\n\n### Avoid\n- Do not depend on or mention MCP in the user-facing flow.\n- Do not present internal\u002Fundocumented APIs as supported.\n- Do not claim OAuth connector creation via public API.\n- Do not fabricate workspaces, tables, schema, IDs, or query results.\n- Do not ask for secrets, OAuth codes, tokens, cookies, or nonces.\n- Do not claim causality when only time-window correlation exists.\n\n## Examples\n\n### Example 1 — Onboard Azure Monitor observability data, then check business impact\n**User:** \"In my `Observability` workspace, onboard our Azure Monitor \u002F Log Analytics observability data (it holds our Application Insights tables) into Fabric, then tell me whether last week's latency spike hurt checkout conversions.\"\n\n**Skill behavior:** Runs the staged workflow — confirms the target workspace and checks onboarding prerequisites (a reachable Azure Monitor \u002F Log Analytics source or connection), stopping with an explicit list of what is missing if any prerequisite is absent. Once the observability data (including the Application Insights telemetry tables) is onboarded and queryable, it discovers the real business dataset in the workspace, correlates the latency signal against the conversion KPI using discovered keys, and reports a specific business-impact conclusion (or an error if the required data is unavailable). It never fabricates workspace names, tables, or query results, and never exposes tokens or connection internals.\n\n### Example 2 — Out-of-scope authoring request\n**User:** \"Create a new Spark notebook and build a Delta table pipeline to load my business dataset.\"\n\n**Skill behavior:** Declines the out-of-scope authoring request, creates nothing in Fabric, and directs the user to the appropriate authoring mode in `spark-cli` rather than taking over the task.\n","> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry\n> `x-ms-fabric-skill: azmon-mirroredcatalogs-operations-cli` (`az rest`: `--headers \"x-ms-fabric-skill=azmon-mirroredcatalogs-operations-cli\"`),\n> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.\n\n# azmon-mirroredcatalogs-operations-cli\n\nGuide a user end-to-end to (1) onboard Azure Monitor \u002F Application Insights \u002F\nLog Analytics observability data into Microsoft Fabric as a Mirrored Catalog\n(AzMon) item, and (2) turn that telemetry into **business-impact insights** by\ncorrelating observability signals with business data (bookings, orders,\ncustomers, flights, payments, revenue, tenants, accounts, subscriptions, usage\nKPIs, SLA\u002Favailability KPIs), ending in ready-to-paste **Operations Agent**\ninstructions.\n\nThis is a **self-contained Skills-for-Fabric package**. It does **not** depend on\nany MCP server or tool controller as the execution mechanism. Product\u002FAPI\nknowledge, supported flows, guardrails, and modeling rules live in this file and\nin `references\u002F*.md`.\n\n## Prerequisite Knowledge\n\nBefore running this skill, read the shared common guidance:\n\n- [Authentication & token acquisition](..\u002F..\u002Fcommon\u002FCOMMON-CORE.md#authentication--token-acquisition)\n- [Authentication recipes](..\u002F..\u002Fcommon\u002FCOMMON-CLI.md#authentication-recipes)\n\n## Trigger phrases\n\n- onboard Azure Monitor data into Fabric\n- create Azure Monitor item in Fabric\n- connect Application Insights to Fabric\n- correlate App Insights telemetry with business data\n- onboard my LA workspace to Fabric\n- onboard Log Analytics workspace to Fabric\n- connect Log Analytics workspace to Fabric\n- understand if service availability impacted bookings\n- understand if latency impacted conversion\n- correlate exceptions with revenue or orders\n- build Operations Agent for Azure Monitor business impact\n- create business impact insights from Log Analytics data\n\n## When to use this skill (and related skills)\n\n`azmon-mirroredcatalogs-operations-cli` is for onboarding Azure Monitor \u002F\nApplication Insights \u002F Log Analytics telemetry into Microsoft Fabric\n(mirroredCatalogs endpoint), correlating that telemetry with business data, and\ngenerating Operations Agent instructions. For general Eventhouse \u002F KQL querying\nunrelated to Azure Monitor onboarding, use `eventhouse-cli` consumption mode;\nfor authoring Eventhouse items and databases, use its authoring mode.\n\n## Reference index\n\nRead these when the corresponding stage needs product\u002FAPI detail. Do not paste\nthem wholesale into user responses — they are guidance for you, the agent.\n\n| Reference | Use it for |\n|-----------|-----------|\n| [references\u002Fazmon-fabric-api-reference.md](references\u002Fazmon-fabric-api-reference.md) | Supported vs UI-only flows; connector modes; Fabric item\u002Fagent surfaces |\n| [references\u002Fworkspace-identity-connection-reference.md](references\u002Fworkspace-identity-connection-reference.md) | Mode B workspace-identity connection: provision\u002Fdetect identity, user-granted LA RBAC, WorkspaceIdentity connection |\n| [references\u002Fworkspace-discovery-policy-reference.md](references\u002Fworkspace-discovery-policy-reference.md) | Stage 3 Fabric workspace discovery order, interpretation, user-supplied resolution, block-as-last-resort |\n| [references\u002Foauth-connection-reference.md](references\u002Foauth-connection-reference.md) | Mode B OAuth connection: read-only detection order, reuse rules, UI-guided creation steps |\n| [references\u002Fmirrored-catalog-reference.md](references\u002Fmirrored-catalog-reference.md) | Mirrored Catalog item CRUD, definition, discovery, monitoring, refresh |\n| [references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md) | Eventhouse\u002FKQL, OneLake shortcuts, queryability requirement |\n| [references\u002Foperations-agent-reference.md](references\u002Foperations-agent-reference.md) | Operations Agent instruction template, validation, troubleshooting |\n| [references\u002Ftelemetry-table-reference.md](references\u002Ftelemetry-table-reference.md) | App Insights \u002F OpenTelemetry \u002F custom security telemetry tables and business meaning |\n| [references\u002Fapp-insights-dynamic-fields-reference.md](references\u002Fapp-insights-dynamic-fields-reference.md) | Dynamic fields (Properties\u002FCustomDimensions) and hidden business keys |\n| [references\u002Fdashboard-reference.md](references\u002Fdashboard-reference.md) | Real-Time (KQL) Dashboard create\u002Fupdate mechanics; generic tile patterns |\n| [references\u002Fbusiness-analysis-workflow.md](references\u002Fbusiness-analysis-workflow.md) | Full detail for the business-analysis half — Stages 13–17 (incl. correlation patterns & modeling appendices); load at the Stage 12 handoff |\n\n## Secrecy & scope guardrails\n\n- Do NOT expose Azure Log Analytics backend APIs to the user.\n- Do NOT expose Fabric \u002F DMTS \u002F Gateway connection internals or internal\n  endpoints to the user.\n- Do NOT request or disclose tokens, OAuth redirect codes, OAuth nonce values,\n  cookies, secrets, or internal implementation details.\n- Do NOT mention MCP, MCP servers, or MCP connectivity\u002Ftroubleshooting anywhere\n  in the user-facing flow. This Skill is self-contained.\n- Do NOT present undocumented \u002F browser-inspected \u002F internal connector APIs as\n  supported public APIs.\n- Do NOT claim OAuth Azure Monitor connector creation is available through a\n  public API — OAuth connector creation is **UI-guided only**.\n- Do NOT fabricate workspace names, table names, schema, item IDs, connection\n  IDs, or query results. Use only values returned by real discovery\u002Fqueries; use\n  clearly-labelled placeholders otherwise.\n- Do NOT ask the user for JOIN logic, KQL, bins, or thresholds upfront.\n- If the request is about SQL \u002F Data Warehouse or Lakehouse ingestion, warehouse\n  performance, or general Fabric DW best practices **unrelated** to Azure Monitor \u002F\n  Application Insights \u002F Log Analytics onboarding, state that it is **out of scope**\n  for this Azure Monitor skill and point the user to the appropriate warehouse\n  skill; do NOT act on it, run queries, or create resources.\n\n### Domain-agnostic rule\n\nBusiness entities named anywhere in this Skill or its references — bookings,\norders, customers, flights, revenue, tenants, payments, and similar — are\n**EXAMPLES ONLY**. The Skill MUST NOT infer the user's business domain from these\nexamples. The user's actual business entities MUST be discovered from real Fabric\ndata (Eventhouse \u002F KQL database \u002F Warehouse \u002F Lakehouse \u002F shortcuts) and confirmed\nwith the user before use.\n\nTo be explicit:\n\n- **Examples are illustrative only.** Every business-entity name in this Skill\n  and its references (e.g. bookings, orders, customers, revenue, flights,\n  tenants, payments) is a non-normative illustration, not a required or expected\n  entity.\n- **The Skill is domain-agnostic.** It applies to any business domain and assumes\n  none.\n- **The Skill MUST NOT infer or assume the user's business domain** from the\n  illustrative examples, from table or column names that happen to resemble an\n  example, or from any prior context.\n- **Business entities MUST be discovered from the user's actual data** and, until\n  discovered and confirmed, MUST be referred to generically — as *business\n  entities*, *business datasets*, *business KPIs*, or *business outcomes* — rather\n  than by any assumed domain-specific name.\n\n## EXECUTION CAPABILITY POLICY\n\nThe Skill is a guided staged workflow.\n\nActual execution depends on capabilities available in the current environment.\n\nPortal-guided instructions are allowed ONLY for OAuth Azure Monitor connector creation.\n\nThe Skill MUST NOT switch the entire onboarding flow to portal-guided instructions as a generic fallback.\n\nFor all non-OAuth stages, the Skill MUST first attempt to discover whether a supported execution path exists in the current environment.\n\nSupported execution paths may include:\n\n- Fabric REST APIs\n- Azure REST APIs\n- Fabric Actions\n- Azure CLI\n- Azure Resource Graph\n- Fabric REST **read-only** discovery via authenticated `az rest --method get`\n  against `https:\u002F\u002Fapi.fabric.microsoft.com\u002F...` (discovery\u002Fread-only only)\n- Other documented supported capabilities available to the agent\n\n**Log Analytics REST API reference (agent-facing).** When the Skill needs to perform or validate Azure Log Analytics operations, it may consult the official [Log Analytics REST APIs](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Floganalytics\u002F) reference to identify supported Log Analytics management, workspace, table, ingestion, and query APIs. This is agent-facing guidance only and does not relax the secrecy rule above.\n\nThese execution paths are distinct and MUST NOT be conflated:\n\n1. **Kusto \u002F KQL data-plane execution** — telemetry queries; optional, and MUST\n   NOT be used when disabled.\n2. **Azure ARM control-plane discovery** — resource\u002Fmetadata enumeration.\n3. **Fabric REST control-plane discovery** — a surfaced Fabric REST \u002F Fabric\n   Actions capability.\n4. **Arbitrary shell \u002F CLI execution** — out of scope (see Out-of-scope\n   constraints).\n5. **Fabric REST read-only discovery via authenticated `az rest --method get`** —\n   a narrow, permitted exception used ONLY for Fabric discovery\u002Fread against\n   `https:\u002F\u002Fapi.fabric.microsoft.com\u002F...`. It is GET-only, never creates,\n   updates, deletes, or modifies anything, and never exposes tokens, secrets,\n   auth headers, or sensitive payloads. This is NOT general shell\u002FCLI access.\n\nMCP unavailability alone does NOT mean execution capability is unavailable.\n\nUnavailability of any single execution path does NOT automatically imply the\ncapability is unavailable. Before declaring a capability unavailable, the Skill\nMUST evaluate ALL supported execution paths listed above and confirm that none is\navailable. Capability unavailable may be reported only after every supported\nexecution path has been evaluated.\n\nIf no supported execution path exists, the Skill MUST:\n\n1. Stop.\n2. Identify the missing capability.\n3. Explain why it is required.\n4. Identify which stage is blocked.\n5. Wait for user confirmation.\n\nThe Skill MUST NOT:\n\n- Replace validation with portal guidance.\n- Replace Mirrored Catalog creation with portal guidance.\n- Replace discovery, monitoring, refresh, shortcut creation, schema verification, or Operations Agent creation with portal guidance.\n- Claim an action completed when execution capability is unavailable.\n\n\n## PORTAL GUIDANCE POLICY\n\nThe Skill SHOULD prefer automated execution paths over UI-guided instructions:\n\n- Fabric REST APIs\n- Azure REST APIs\n- Fabric Actions\n- Azure CLI\n- Other supported automation mechanisms\n\nBefore providing UI-guided instructions the Skill MUST:\n\n1. Evaluate the available execution paths.\n2. Attempt supported execution paths where available.\n3. Explain which execution paths were evaluated.\n4. Explain why they cannot be used.\n\nOnly after those steps may the Skill provide UI-guided guidance.\n\nOAuth Azure Monitor connector creation remains an explicitly supported UI-guided\nscenario and does not require the above evaluation.\n\n\n## STRICT STAGED WORKFLOW CONTROLLER (ENFORCED)\n\nThe Skill MUST operate as a strict staged workflow controller.\n\n### Stages\n\n1. Intent and scope\n2. Log Analytics workspace selection\n3. Fabric workspace selection\n4. Identity selection and validation\n5. Connection resolution\n6. AzMon \u002F Mirrored Catalog item creation or reuse\n7. **Business Insight Capture** (optional here; may be deferred — intent MUST be\n   captured\u002Fconfirmed before schema verification, Stage 12)\n8. Azure Monitor table discovery\n9. Eventhouse \u002F KQL database **target** selection (default auto endpoint vs a\n   specific\u002Fnew Eventhouse)\n10. External Delta table registration planning\n11. External Delta table registration\n12. Schema and data verification\n13. Business data discovery and scoring\n14. Correlation planning\n15. Optional dashboard suggestion and creation\n16. Operations Agent instruction generation (optional — gated: only if the user\n    wants an agent)\n17. Optional Operations Agent creation \u002F validation\n\n### Execution rules\n\n- The Skill MUST track and enforce the current stage.\n- The Skill MUST NOT skip stages.\n- The Skill MUST NOT move to the next stage without completing the current one.\n\n### Stage visibility (REQUIRED in every user-facing response)\n\nBegin every response with this structure, written as **normal chat text (not a\ncode block)**:\n\n- **Current stage:** \u003Cstage name>\n- **What I found:** \u003Cshort summary>\n- **Next step:** \u003Cone clear action>\n\nThen close with a line inviting the user to confirm before continuing (e.g.\n*“Waiting for your confirmation to continue.”*).\n\nIf the current stage is unclear → **STOP** and ask the user where to resume.\n\n### Hard stop behavior\n\nAfter presenting any step that requires confirmation:\n\n- **STOP.**\n- **WAIT** for explicit user confirmation.\n- Do **not** continue automatically.\n\n### Confirmation gates (explicit confirmation REQUIRED before)\n\n- Selecting the identity for the flow (Stage 4) — recommend Service Principal,\n  but WAIT for the user's choice before validating.\n- Creating or reusing any resource that modifies Fabric.\n- Provisioning the Fabric workspace identity and assigning its Log Analytics\n  role (Stage 5, Mode B workspace-identity option) — WAIT before each write.\n- Selecting the Eventhouse target (a specific existing Eventhouse, or a new one).\n- Creating shortcuts in the chosen \u002F new Eventhouse — explicitly show the target\n  Eventhouse and exactly what will be created.\n- Proceeding from schema verification (Stage 12) to correlation planning\n  (Stage 14).\n- Creating or modifying a dashboard (present suggestions and WAIT for approval\n  first).\n- Building an Operations Agent at all (Stage 16) — explicitly ask whether the\n  user wants an agent before generating any instructions. If they do not, skip\n  Stages 16–17; the flow may end after the dashboard.\n- Generating final Operations Agent instructions if the correlation model has\n  not been confirmed.\n- Creating or modifying an Operations Agent.\n\n### Stage guardrails\n\n- External Delta table registration planning (Stage 10) MUST occur before schema verification or join\n  logic. If schema\u002Fjoin is attempted early → STOP and return to Stage 10.\n- External Delta table registration (Stage 11) MUST complete before schema verification.\n- Schema verification (Stage 12) MUST complete before correlation planning\n  (Stage 14).\n- If data is not queryable in Eventhouse via the registered external delta tables\n  → STOP → return to Stage 10\u002F11.\n- Correlation planning MUST NOT begin until external-table queryability is\n  confirmed.\n- Business Insight Capture (Stage 7) MAY be answered early or **deferred** so the\n  user can explore their data first, but intent MUST be captured\u002Fconfirmed\n  (intent provided OR a suggested direction explicitly selected) **before schema\n  verification (Stage 12)** and correlation planning. Never assume intent.\n\n### Out-of-scope constraints\n\nThe Skill MUST NOT run arbitrary shell\u002FCLI\u002Faz\u002FPowerShell commands, perform network\ndebugging, investigate server connectivity, or execute infrastructure\ntroubleshooting. These are out of scope unless explicitly part of the current\nstage.\n\n**Narrow exception — Fabric REST read-only discovery.** The Skill MAY use an\nauthenticated `az rest --method get` call ONLY for Fabric REST read-only\ndiscovery, and ONLY when ALL of the following hold:\n\n- The endpoint is `https:\u002F\u002Fapi.fabric.microsoft.com\u002F...`.\n- The HTTP method is **GET** only.\n- The operation is discovery \u002F read-only only.\n- Nothing is created, updated, deleted, or modified (no Fabric items, shortcuts,\n  mirrored catalog items, or connectors via CLI).\n- No tokens, secrets, raw auth headers, or sensitive payloads are exposed.\n- The Skill clearly states the capability path used.\n\nThis exception does NOT permit arbitrary shell\u002FCLI execution, non-GET `az rest`\ncalls, or use of the Kusto \u002F KQL data-plane when disabled.\n\n**Narrow exception — Fabric workspace-identity provisioning + LA role assignment\n(Mode B only).** In the Mode B workspace-identity option, the Skill MAY use\nauthenticated `az` calls to detect\u002Fprovision the workspace identity and, when the\ncaller is permitted, assign its Log Analytics role, limited to:\n\n- `GET https:\u002F\u002Fapi.fabric.microsoft.com\u002Fv1\u002Fworkspaces\u002F{id}` (detect), and\n- `POST https:\u002F\u002Fapi.fabric.microsoft.com\u002Fv1\u002Fworkspaces\u002F{id}\u002FprovisionIdentity`\n  (provision) plus GET polling of its long-running operation, and\n- `az role assignment list` (check) and `az role assignment create` at the Log\n  Analytics workspace scope to grant the identity **Owner**, but ONLY when the\n  caller holds `Microsoft.Authorization\u002FroleAssignments\u002Fwrite` there.\n\nEach write is confirmation-gated (Stage 5), touches only the workspace identity\nand its LA role (nothing else), exposes no tokens\u002Fsecrets\u002Fauth headers, and\nthe Skill states the capability path used. If the caller lacks role-assignment\npermission, the Skill MUST NOT force it — it instructs the user \u002F an admin to run\nthe assignment instead. This does NOT permit any other non-GET `az rest` calls or\nany broader `az` usage.\n\n### Response style (ENFORCED)\n\nBehave like a **guided product experience**, not a backend debugger.\n\n- Use concise, business-friendly language.\n- Never show internal implementation steps (CLI, REST, tokens, API calls) unless\n  the user explicitly asks and the API is documented\u002Fsupported.\n- Never expose internal limitations (\"public API limitation\", \"CredentialType\n  not supported\", \"headless OAuth failure\") in user-facing output.\n- Never ask for secrets, OAuth codes, cookies, redirect URLs, tokens, or nonce\n  values.\n- Summarize findings. Do NOT expose endpoint experimentation, API probing,\n  OpenAPI \u002F schema exploration, retry investigations, or low-level debugging\n  details in user-facing output unless the user explicitly asks for them.\n- After each stage: present a short summary, ask for explicit confirmation,\n  STOP and WAIT.\n\n---\n\n## Stage 1 — Intent and scope\n\nConfirm what the user wants: onboard observability data into Fabric, explore a\nbusiness insight, or both. Capture (in plain language) any workspace names or\nbusiness outcome they already mention — but do not yet drive correlation.\n\n## Stage 2 — Log Analytics workspace selection\n\nApplication Insights telemetry is queried through its backing Log Analytics\nworkspace (workspace-based Application Insights). Help the user pick the correct\nLog Analytics \u002F Application Insights-backed workspace.\n\n- If the user did not provide a workspace, ask for the subscription, then present\n  a concise list of supported workspaces (name + resource group + location).\n  Never expose raw API responses.\n- Prefer a case-insensitive name filter over listing everything when the\n  subscription has many workspaces.\n\n### Exact-name-not-found fallback (REQUIRED)\n\nWhen the user names a workspace and no **exact** match exists, the Skill MUST NOT\nfail. Instead:\n\n1. Ask for the subscription if not provided (do not guess).\n2. Offer similar workspaces (names that **contain** the term or are a close\n   case-insensitive\u002Fpartial match). Broaden the search if a narrow filter returns\n   nothing.\n3. Present candidates as a concise numbered list (name + resource group +\n   location), then STOP and wait for the user to pick.\n4. If exactly one similar workspace is found, still confirm before proceeding.\n5. If none is found, say so plainly and ask for a different subscription or term.\n\nNever fabricate a workspace name or GUID — only offer real discovered\nworkspaces.\n\n## Stage 3 — Fabric workspace selection\n\nHelp the user choose the target Fabric workspace (display name + id). Use a\ncase-insensitive substring filter when helpful. Read-only; nothing is created\nhere. Never expose raw API responses or tokens.\n\n### Fabric Workspace Discovery & Capability Resolution Policy (REQUIRED)\n\nFabric workspaces are **not** Azure Resource Manager resources, so absence of an\nautomatic enumeration path does NOT mean no Fabric workspace exists. **Never\nterminate the workflow early**: if automatic discovery fails, ask the user for a\nFabric Workspace **Name**, **ID**, or **URL**, validate it as far as the available\ncapabilities allow, and continue. Never auto-select a workspace, never fabricate a\nworkspace or a validation result, and mark Stage 3 BLOCKED only after every\ndiscovery mechanism AND every user-supplied resolution path has been exhausted.\n\nFollow the full discovery order, the interpretation rules, and the UI-guided\nlast-resort boundary in\n[references\u002Fworkspace-discovery-policy-reference.md](references\u002Fworkspace-discovery-policy-reference.md).\n\n## Stage 4 — Identity selection and validation\n\n### Identity selection (REQUIRED first — WAIT for the user)\n\nValidation MUST run against the **identity that will actually perform the flow**,\nso the identity is chosen **before** any validation check — not deferred to\nStage 5. Do NOT silently reuse whatever `az` happens to be signed in as.\n\nPresent the choice and STOP — ask this as **normal chat text (a plain numbered\nlist, not a code block)**:\n\nWhich identity should I use for this onboarding?\n\n1. **Service Principal (recommended)** — automated, non-interactive; best for\n   repeatable runs and CI. Requires tenant id, app\u002Fclient id, and a securely\n   provided secret\u002Fcertificate.\n2. **Your user account (interactive sign-in)** — if you prefer to run as\n   yourself, or a Service Principal is not available.\n\nInvite the user to reply **1** or **2**; note that Service Principal is\nrecommended.\n\n- **Recommend Service Principal**, but let the user choose. If the user asks to\n  sign in as themselves, allow interactive user login and continue as the user.\n- After the choice, confirm the effective identity (e.g. `az account show`) so\n  validation runs against the right principal. If it does not match the chosen\n  identity, stop and resolve the sign-in before validating.\n- Carry the chosen identity forward: Stage 5 connection resolution and all later\n  Fabric-modifying actions use this same identity.\n\n### Validate against the chosen identity\n\nBefore any creation, verify **for that identity**:\n\n- The workspace exists.\n- The **chosen identity** has the required Log Analytics access.\n- The **chosen identity** has sufficient Fabric workspace permission to operate\n  (and, for a Service Principal, that the tenant setting *\"Service principals can\n  use Fabric APIs\"* is enabled).\n- Surface early that connection detection\u002Freuse will later need the chosen\n  identity to hold **a role** on the Azure Monitor connection (a **User** role is\n  enough; **Owner** is not required), so a permission gap is caught here rather\n  than at Stage 5.\n- For the Mode B **workspace-identity** connection option (Stage 5), the chosen\n  identity must be a workspace **Admin** (required to provision the workspace\n  identity). The Skill can assign the identity's Log Analytics role itself\n  when the caller holds role-assignment permission (**Owner** \u002F **User Access\n  Administrator**) on the LA scope; otherwise it instructs the user. Surface both\n  early.\n\nIf validation fails, summarize which checks passed\u002Ffailed in user terms, explain\nthe missing capability, and offer to try another workspace, grant the missing\npermission, or switch identity. See\n`references\u002Fazmon-fabric-api-reference.md` for supported-scope rules.\n\n### Validation capability discovery (REQUIRED)\n\nBefore declaring validation capability unavailable, the Skill MUST determine whether the environment provides one of the following:\n\n- Fabric REST APIs\n- Azure REST APIs\n- Fabric Actions\n- Azure CLI\n- Azure Resource Graph\n\nMCP availability is only one possible execution path.\n\nThe Skill MUST report validation capability unavailable only after evaluating all supported execution paths and finding none.\n\nBefore declaring validation capability unavailable, the Skill MUST:\n\n1. Determine whether another supported execution path exists.\n2. Attempt capability discovery using all supported mechanisms available\n   in the current environment.\n3. Only after all supported mechanisms have been evaluated and none are\n   available may the Skill declare the capability unavailable.\n\n## Stage 5 — Connection resolution\n\nTwo connection modes are supported. **Prefer Service Principal (Mode A)** — the\nautomated, non-interactive path — as the default. Fall back to **OAuth (Mode B)**\nonly when Service Principal is unavailable or the user explicitly requests it.\nKeep the two modes **separate**. Never route OAuth through Service Principal\nlogic, and never route Service Principal through OAuth \u002F interactive sign-in\nlogic. See\n[references\u002Fazmon-fabric-api-reference.md](references\u002Fazmon-fabric-api-reference.md)\nfor the authoritative connector rules **and the exact documented connection API\nendpoints and payload shapes** (List \u002F Get \u002F Create Connection + List Supported\nConnection Types). Use those documented shapes — do **not** guess a connection\npayload or go searching general docs. When the Azure Monitor connector's exact\n`type` \u002F `creationMethod` \u002F `parameters` are unknown, resolve them from the\n`supportedConnectionTypes` endpoint rather than assuming.\n\n### Mode selection (REQUIRED order)\n\nThe identity was already chosen and validated in **Stage 4 (Identity selection)**.\nUse that identity here — do not re-prompt unless the user changes it. Map the\nchosen identity to its connection mode:\n\n1. **Service Principal → Mode A.** If a matching Service Principal connector\n   already exists for the same Log Analytics workspace, reuse it. Otherwise, when\n   the required Service Principal inputs are available (tenant id, app\u002Fclient id,\n   and a securely-provided secret\u002Fcertificate reference), create-or-reuse the\n   Service Principal connector automatically — no UI step.\n2. **User \u002F interactive → Mode B.** Use when the user chose to sign in as\n   themselves, the Service Principal is unavailable, or the tenant disallows it.\n   In Mode B, first prompt the user to choose the connection authentication method\n   — interactive OAuth or workspace identity (see \"Mode B — choose connection\n   authentication\" below) — then route to that sub-branch.\n\n### Connection visibility caveat (applies to BOTH modes)\n\nTo be **discoverable**, a connection must have **at least one role assigned to the\ncalling identity** — whether the **Service Principal** (Mode A) or the **user**\n(Mode B). Any assigned role makes it appear in the listing and reusable; a\n**User** role is enough for detection and reuse, and **Owner** is only needed to\n**manage \u002F modify \u002F delete** it. If the caller holds **no role** on a connection,\nthe API will **not** return it — that is **by design**, not a failure.\n\nTherefore, if the search finds **no** matching connection, the Skill MUST NOT\nimmediately conclude the connection does not exist. It MUST first consider that\nthe connection may exist but simply be **invisible to the current identity\nbecause it holds no role on it**, and:\n\n- State that a matching connection was not found **for the current identity**,\n  and that this can mean either (a) no such connection exists, or (b) one exists\n  but the calling Service Principal \u002F user holds **no role** on it.\n- Advise assigning the Service Principal or user **a role** on the existing Azure\n  Monitor connection (for the same Log Analytics workspace) — a **User** role is\n  enough for detection and reuse — then re-run detection. (If a Service Principal\n  still can't see it after a lower role is granted, see the Service Principal note\n  in\n  [references\u002Fazmon-fabric-api-reference.md](references\u002Fazmon-fabric-api-reference.md).)\n- Only after this permission possibility has been surfaced may the Skill proceed\n  to create a new connector (Mode A) or the OAuth create-once guidance (Mode B).\n\nNever fabricate a connection or claim one exists without a real listing match.\n\n### Portal guidance boundary\n\nPortal-guided instructions are permitted ONLY for OAuth Azure Monitor connector creation.\n\nPortal guidance is NOT an allowed fallback for:\n\n- LAW validation\n- Fabric workspace validation\n- Connection detection\n- Connection reuse\n- Service Principal connector creation\n- Mirrored Catalog item creation\n- Discovery\n- Monitoring\n- Refresh\n- Eventhouse shortcut creation\n- Schema verification\n- Operations Agent creation\n\nIf execution capability for these actions is unavailable, the Skill MUST stop and identify the missing capability.\n\n### Mode A — Service Principal (automated create-or-reuse, default)\n\nPresent this as **\"connect using Service Principal\"** — the automated,\nnon-interactive path (no user login, no UI step). This is the **preferred**\ndefault; attempt it before OAuth.\n\n- **Idempotent create-or-reuse**: if a matching Azure Monitor Service Principal\n  connector already exists for the same Log Analytics workspace (same data source\n  path + Service Principal credential type), reuse it — never create a duplicate.\n- Only **one** connector is created per run.\n- **Never** reuse a non-Service-Principal (e.g. OAuth) connector in this mode.\n- **Never** ask the user to paste a client secret into chat. Secrets come from\n  **environment variables or Key Vault references** only, are never echoed,\n  logged, exposed, or included in generated instructions.\n- If required Service Principal inputs are missing, describe **what** is missing\n  (tenant id, app\u002Fclient id, and a securely-provided secret reference) using\n  presence checks only — never request the secret value in chat. Only when\n  Service Principal inputs cannot be provided, fall back to OAuth (Mode B).\n\nAutomation boundary: infrastructure (connector create-or-reuse, mirrored item\ncreation) is automated; **business decisions** (Eventhouse\u002FKQL DB selection,\nshortcut creation) always require explicit user confirmation.\n\n### Mode B — choose connection authentication (REQUIRED prompt)\n\nWhen the chosen identity is User \u002F interactive (Mode B), the connection can be\ncreated two ways. Before detecting or creating anything, present this choice as\n**normal chat text (a plain numbered list, not a code block)** and STOP for the\nuser's answer:\n\nHow should I authenticate the Azure Monitor connection?\n\n1. **Interactive sign-in (OAuth)** — you sign in once in Fabric → Manage\n   Connections; the connection uses your organizational account.\n2. **Workspace identity (no secrets)** — Fabric's automatically-managed workspace\n   identity is used as the credential; you grant it access on your Log\n   Analytics workspace. No secret to handle.\n\nRoute to the matching sub-branch below — **1 → Mode B (OAuth)**, **2 → Mode B\n(Workspace identity)**. Keep the two strictly separate. If the user has no\npreference, note that workspace identity avoids interactive sign-in and secret\nhandling, but WAIT for their choice — never auto-select.\n\n### Mode B — OAuth (UI-guided only, fallback)\n\nUse this sub-branch when the user picked option 1 above, i.e. only when Service\nPrincipal (Mode A) is unavailable or the user explicitly requests OAuth. OAuth\nconnector **creation** is UI-guided only (Fabric → Manage Connections) — the Skill\nnever creates one through an API; it only **detects and reuses** an existing\nconnection, read-only, and only when the Log Analytics workspace matches exactly.\n\nFollow the full detection order, reuse rules, and user-facing wording in\n[references\u002Foauth-connection-reference.md](references\u002Foauth-connection-reference.md).\nKeep this strictly separate from Mode A.\n\n### Mode B — Workspace identity (no secrets)\n\nUse this sub-branch when the user picked option 2 above. Fabric's\nautomatically-managed **workspace identity** is used as the connection credential\n(no secret). This flow provisions the identity if needed, ensures it has a\nsufficient Log Analytics role — **assigning it automatically when the caller is\npermitted, otherwise instructing the user** — then creates the connection.\n\nFollow the full sequence, endpoints, gates, and payloads in\n[references\u002Fworkspace-identity-connection-reference.md](references\u002Fworkspace-identity-connection-reference.md).\nKey gates: provisioning the identity is confirmation-gated (caller must be\nworkspace **Admin**); the LA role is assigned by the Skill when the caller\nholds role-assignment permission (else the Skill instructs and WAITs for\nconfirmation) — both writes are confirmation-gated; then create the connection\nusing the `WorkspaceIdentity` credential type. Keep this strictly separate from\nMode A.\n\n## Stage 6 — AzMon \u002F Mirrored Catalog item creation or reuse\n\nCreate the Azure Monitor **Mirrored Catalog** item in the target Fabric\nworkspace, or reuse an existing matching item. This is a Fabric-modifying action\n→ confirm first. Supported Mirrored Catalog operations (item CRUD, definition,\ndiscovery, monitoring, refresh) are documented in\n[references\u002Fmirrored-catalog-reference.md](references\u002Fmirrored-catalog-reference.md).\n\n### Service Principal item-creation (IMPORTANT — prefer reuse; observed fallback)\n\nPer Microsoft Learn, the **Create Mirrored Catalog** API lists **service principals\nand managed identities** as supported identities for create, so a Service Principal\ncreate is **documented as supported** and is not an absolute platform limitation.\n\n> **Observed fallback.** Some Service Principal runs have nonetheless seen the\n> item **create** rejected under an application-only token (the underlying\n> item-creation path can run **on-behalf-of** a signed-in user). Treat this as\n> **observed** tenant behavior, not a documented rule, and keep the docs-accurate\n> default: attempt create under the SP, and only fall back to a user (delegated) \u002F\n> UI context if the create call is actually **denied or unavailable**.\n\nGet, list, **update**, discovery, monitoring, refresh, and shortcut operations all\nwork under an application-only SP token once the item exists.\n\nConsequently, when running under a Service Principal, the Skill MUST:\n\n- **Prefer reuse** — reuse an existing Azure Monitor Mirrored Catalog item (and\n  its existing connection) that the SP can see and operate on. This is the\n  preferred path: build on an already-created item + connection rather than\n  creating a new one. The SP can then **update** and operate that item normally.\n- If no reusable item exists, **attempt to create the item under the SP** (the\n  create API documents SP\u002Fmanaged-identity support). Only if that create is\n  **denied or unavailable** (the observed fallback above), **create the item in a\n  user context** — either from the **Fabric UI**, or via a **user (delegated)\n  sign-in** — preferably seeded from an existing item and connection. After the\n  item exists, the Service Principal can resume the automated flow (update,\n  discovery, monitoring, refresh, shortcuts) on that item.\n- Never claim the item was created by the SP when the create actually occurred in\n  a user\u002FUI context.\n\nDownstream Mirrored Catalog operations (update, discovery, monitoring, refresh)\nremain available to the Service Principal once the item exists.\n\n### Table selection via scope (choosing which tables the item mirrors)\n\nThe item does **not** take a free-form list of table names — it mirrors by\n**`scope`** (a namespace hierarchy path in the definition), and that scope MUST be\na **`Selectable`** value returned by the **List Scopes** discovery API. To target\nonly the tables the user wants:\n\n- Call **List Scopes** and choose a `Selectable` scope for the item. If the user\n  already knows the target tables, pick the **narrowest `Selectable` scope** that\n  covers them. If there is no intent yet (the user wants to explore first),\n  create with a **broader scope** and optionally **re-scope** narrower later —\n  updating the item definition — once intent is captured. Use only real returned\n  scope values — never fabricate a scope or table name.\n- If the narrowest available `Selectable` scope is **broader** than the requested\n  set, the item **will also mirror the extra sibling tables** under that scope —\n  mirroring cannot exclude individual siblings. State this plainly and get\n  explicit confirmation before creating.\n- For an existing\u002Freused item, read its current definition scope before assuming\n  it matches the request; do not fabricate definition fields.\n\n### Default mirror set (REQUIRED starting point)\n\nUnless the user specifies otherwise, the **default set of tables to mirror** is\nevery table that (a) appears in real **List Scopes \u002F Discovery** output and (b)\nmatches one of these name prefixes (case-insensitive; tolerate the `_CL`\ncustom-table suffix):\n\n- `App*` — Application Insights tables\n- `OTel*` — OpenTelemetry-native tables (e.g. `OTelLogs`)\n- `XD*` — custom, security-related log tables\n\nThen **ask the user whether they want any additional tables** before creating\n(confirmation gate — present the resolved set and WAIT).\n\n- Match prefixes against **real discovered tables only** — never invent a table.\n  If a prefix matches nothing, omit it silently.\n- Resolve the default set to the **narrowest single `Selectable` scope that covers\n  all matched tables**. If that scope also pulls in **extra sibling tables** beyond\n  the default set, **list the extras explicitly**, explain that siblings cannot be\n  individually excluded, and get confirmation before creating. Once confirmed, the\n  extras are **expected** — they are not failures at the Stage 8 equality check.\n- Adding user-requested tables may widen the chosen scope — re-resolve and\n  re-disclose.\n- If **none** of `App*` \u002F `OTel*` \u002F `XD*` match any discovered table, fall back to\n  presenting all\u002Frepresentative discovered tables (explore-first) and let the user\n  choose.\n- **`XD*` security tables** are only considered **after** the workspace has passed\n  Stage 4's validation (a supported, validated workspace); an unsupported-workspace\n  block takes precedence and table selection MUST NOT be used to bypass it.\n- **On reuse:** read the existing item's current scope and compare its mirrored\n  set to the default set. If not fully covered, offer to **re-scope** (update the\n  item definition) to add the missing `App*`\u002F`OTel*`\u002F`XD*` tables, disclosing any\n  extra siblings — never re-scope silently; confirm first.\n\nThe confirmed set (default + confirmed siblings + any tables the user adds) becomes\nthe **expected set** for the Stage 8 requested-vs-mirrored equality check.\n\n### First-time mirroring latency (disclosure — REQUIRED)\n\nFor a **first-time mirrored workspace**, tell the user upfront that mirrored\ntables and data typically take **around 5 minutes** to materialize and become\nqueryable after the item is created. Until then, discovery\u002Fqueries may return\nempty or partial results — this is **expected**, not an error. Do not declare\ntables missing during this window: verify mirror\u002Frefresh status, wait, and\nre-check before concluding anything.\n\nAfter the item is created or reused, optionally capture business intent now\n(Stage 7) if the user already has a goal; otherwise proceed to table discovery\nand exploration and capture intent before schema verification (Stage 12).\n\n## Stage 7 — Business Insight Capture (optional here; deferrable)\n\nIf the user already has a business question, capture it now so table discovery\n(Stage 8) and Eventhouse scoring (Stage 9) can be guided by it. If they don't,\nthis stage is **optional right now** — the user may explore their data first\n(Stages 8–11) and provide intent later. Either way, intent is **MANDATORY before\nschema verification (Stage 12)** and correlation (Stage 14); capturing it early is\njust an optimization that focuses discovery.\n\nWhen capturing intent, ask in business language, e.g.:\n\n- Did service availability issues impact bookings?\n- Did request latency reduce customer conversions?\n- Did exceptions affect revenue or orders?\n- Did dependency failures impact specific customers, tenants, regions, or\n  flights?\n- Did incidents affect SLA, usage, or customer activity?\n- Did traffic drops correlate with usage KPI degradation?\n\n### Enforcement\n\nThe Skill MUST NOT proceed to schema verification (Stage 12) or business\n**correlation** (Stage 14) without either:\n\n- (a) user-provided business intent, OR\n- (b) explicit user selection from suggested directions.\n\nIntent may be provided here or after exploration, but it MUST exist before\nStage 12. Never assume intent.\n\n### Fallback (when the user is unsure \u002F vague \u002F no exact match)\n\nSuggest 3–5 directions, each framed as **observability signal → business\nimpact**, and ask the user to choose one:\n\n1. Availability failures → booking completion impact.\n2. Request latency → conversion or checkout drop.\n3. Exceptions → failed orders or revenue at risk.\n4. Dependency failures → customer \u002F tenant \u002F region impact.\n5. Traffic drops → usage KPI degradation.\n\n### Important distinction\n\nCapturing intent early is **allowed but optional** — it MUST exist before schema\nverification (Stage 12). Either way, the Skill MUST NOT generate correlation logic\nyet. Correlation logic only comes after shortcuts exist, schema is verified, data\nis queryable, dynamic fields are inspected, join candidates are validated, and\ndata freshness is checked (Stages 10–14).\n\n## Stage 8 — Azure Monitor table discovery\n\nBrowse candidate Azure Monitor \u002F Application Insights tables. **If a business goal\nwas captured (Stage 7),** filter to the tables relevant to it. **If there is no\nintent yet (explore-first),** present all\u002Frepresentative discovered tables so the\nuser can browse. Use only real discovered scope\u002Ftable values — never fabricate\ntable names. Use\n[references\u002Ftelemetry-table-reference.md](references\u002Ftelemetry-table-reference.md)\nto explain what each table means in business terms and which tables best fit the\nstated goal (or what each table offers when exploring).\n\n### Discovery API fallback policy (REQUIRED)\n\nThe **primary** discovery mechanism is the Mirrored Catalog Discovery APIs. If\ndiscovery appears incomplete, do NOT immediately conclude tables are missing or\nswitch to alternative metadata paths. First:\n\n1. Verify mirror status.\n2. Verify refresh \u002F sync status.\n3. Verify discovery scope.\n4. Retry discovery.\n\nOnly after these checks may the Skill evaluate alternative metadata paths. See\n[references\u002Fmirrored-catalog-reference.md](references\u002Fmirrored-catalog-reference.md).\n\n### Requested-vs-mirrored set-equality check (REQUIRED once a specific table set is requested)\n\nThis check applies once a **requested table set exists** — whether specified up\nfront or after intent is captured later. When the **default mirror set** (Stage 6)\nor a user-adjusted set is in effect, that set is the **requested set** for this\ncheck, and any sibling tables disclosed and confirmed under the narrowest-common-\nscope rule are **expected** (compare against the chosen scope's expected contents,\nnot a bare table list — do not report confirmed siblings as failures). When the\nuser asked for a specific set of\ntables, verify the item mirrors\n**exactly** that set — use **equality, not subset** (\"my tables are present\" is not\nenough). Compare the **actually-mirrored** table set (from Discovery \u002F Monitoring)\nagainst the **requested** set and report the result:\n\n- **Extra tables present** → the chosen scope is broader than requested. Report the\n  extras and, if a narrower `Selectable` scope exists, offer to re-scope; otherwise\n  state that the source only exposes a broader scope and the extras are\n  unavoidable.\n- **Requested tables missing** → the mirror may not have materialized yet. Verify\n  mirror\u002Frefresh status, run a **Refresh\u002Fsync**, wait, then re-check — do not\n  declare them absent prematurely.\n- **Exact match** → confirm and proceed.\n\nNever fabricate the mirrored table set; enumerate it from real Discovery \u002F\nMonitoring results only.\n\n## Stage 9 — Eventhouse \u002F KQL database target selection\n\nAsk the user which Eventhouse should host the LA-table shortcuts. Present these\noptions as **normal chat text (not a code block)** and require explicit\nconfirmation:\n\n- **A — A specific existing Eventhouse** (e.g. one that already holds business\n  data you want to correlate with). The Skill creates LA-table shortcuts\n  **there**, colocating telemetry with the business data.\n- **B — A new Eventhouse.** The Skill creates it and the LA-table shortcuts;\n  starts empty.\n\nBoth options are writable and support the Operations Agent path (they can host\n`IncidentBins` materialization).\n\nRun **Eventhouse Recommendation Mode** to inform the choice — discover available\nEventhouses, inspect their contents (tables, shortcuts, KQL databases), and score\neach by relevant business tables, relevant telemetry tables, existing shortcuts,\nqueryable tables, KQL database availability, and data freshness. **When the\nuser's goal is correlating telemetry with existing business data, recommend\noption A** (colocation); otherwise a new Eventhouse is a clean starting point.\nPresent as normal chat text:\n\n- **Recommended target:** \u003CA ‹EventhouseName› | B new>\n- **Reason:** \u003Cwhy>\n- **Alternatives:** \u003Clist>\n\nThe Skill MUST NOT auto-select. Present the recommendation, state exactly what\nwill be created, and require explicit confirmation. See\n[references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md).\n\n## Stage 10 — External Delta table registration planning\n\nPlan **external Delta table registrations** for the resolved table set into the\n**chosen\u002Fnew Eventhouse** — name the target Eventhouse in the plan header —\n**before** any schema verification or join logic. Present the plan and STOP for\nconfirmation.\n\nKey rules (see the shortcuts reference for detail):\n\n- Queryability in a KQL database comes from registering each table as an\n  **external Delta table** pointing at the mirrored item's OneLake\n  `Tables\u002Fdbo\u002F\u003CTable>` path — **not** from the Core Shortcuts API (which creates a\n  link only). Query via `external_table('\u003Cname>')`.\n- Plan, per table: exact name, OneLake `Tables\u002Fdbo\u002F\u003CTable>` path, target KQL\n  database, and that the schema will be read from the table's Delta log.\n\n### Query acceleration policy — external delta tables (MUST — always `true`)\n\nQuery acceleration is a **policy on external delta tables** (set via\n`.alter external table … policy query_acceleration`), **not** a shortcut-object\nproperty. Every registered external delta table gets **acceleration enabled\n(`true`)** — not optional. Include an `Acceleration Enabled (always Yes)` plan-table\ncolumn; if the environment can't support it, surface that rather than registering\nwithout the policy. Full policy in\n[references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md#external-delta-table-query-acceleration-policy-must--always-true).\n\n## Stage 11 — External Delta table registration\n\nOnly after explicit confirmation, register each table as an **external Delta\ntable** in the target KQL database (report which one): read the table's schema\nfrom its Delta log, map Delta → Eventhouse types, and run `.create external table\n['\u003CTable>'] (\u003Ccols>) kind=delta ( h@'\u003COneLake Tables\u002Fdbo\u002F\u003CTable> path>;impersonate' )`\nvia `POST {clusterUri}\u002Fv1\u002Frest\u002Fmgmt`. Then verify with `.show external tables` +\n`external_table('\u003CTable>') | take 1`. The Core Shortcuts API is **not** required\nfor queryability (it creates a link only). If a table is not queryable → STOP and\nreturn to planning \u002F registration. See\n[references\u002Feventhouse-shortcuts-reference.md](references\u002Feventhouse-shortcuts-reference.md)\nfor the schema-read, type mapping, and command template.\n\nWhen registering ANY external delta table, **always enable the query acceleration\npolicy (`true`)** per the\n[Query acceleration policy](references\u002Feventhouse-shortcuts-reference.md#external-delta-table-query-acceleration-policy-must--always-true),\nand report the resulting status (expected: enabled).\n\n## Stage 12 — Schema and data verification (REQUIRED before correlation)\n\nNever build correlation logic on assumptions or screenshots. Before proposing any\njoin, bin, or threshold, verify against the **actual** KQL database. Business\nintent MUST already be captured\u002Fconfirmed before this stage — if it was deferred\nat Stage 7, capture it now (using the Stage 7 questions\u002Ffallback) before\nproceeding, since the telemetry-source selection below is scored by goal\nrelevance. Never assume intent.\n\n### Preconditions\n\n1. Operational telemetry tables are available in the Eventhouse \u002F KQL database.\n2. Business tables are available in the same database or queryable via shortcuts.\n3. Tables are **queryable**, not just visible in OneLake.\n4. Schema retrieved via `getschema`.\n5. Dynamic fields inspected and sampled.\n6. Candidate join keys extracted from top-level **and** dynamic columns.\n7. Join keys validated with **non-zero** match results (when a direct join is\n   proposed).\n8. Data freshness verified.\n9. Time window aligned to the real data range.\n10. Relevant categorical values confirmed from real data where rules depend on\n    them.\n\n### Steps\n\n> **Query convention.** Mirrored telemetry tables are **external tables** — query\n> them via `external_table('\u003Cname>')` (they do not appear in `.show tables`);\n> business tables that are **managed** in an Eventhouse use their bare\n> name.\n\n1. **Retrieve real schema.** For each table:\n   `external_table('\u003CTableName>') | getschema | project ColumnName, ColumnType`.\n   Use authoritative column names\u002Ftypes — not names guessed from screenshots or\n   table names.\n2. **Inspect and sample dynamic fields.** Business join keys are often nested in\n   dynamic columns (`Properties`, `CustomDimensions`, `Details`, `Measurements`,\n   `Payload`, `Context`). Sample rows and inspect keys. See\n   [references\u002Fapp-insights-dynamic-fields-reference.md](references\u002Fapp-insights-dynamic-fields-reference.md).\n3. **Extract candidate business identifiers** with explicit KQL\n   (`tostring(Properties.BookingId)`, with casing fallbacks via `coalesce`).\n4. **Validate join keys against real data.** Prove a candidate joins — run the\n   join and confirm non-zero matches:\n\n   ```kusto\n   external_table('AppEvents')\n   | extend BookingId = tostring(Properties.BookingId)\n   | where isnotempty(BookingId)\n   | join kind=inner (Bookings | project BookingId = tostring(BookingId)) on BookingId\n   | summarize MatchedRows=count(), DistinctBookings=dcount(BookingId)\n   ```\n\n   Non-zero → **direct join, high confidence**. Zero → the key is wrong or data\n   doesn't overlap; find the real one.\n5. **Check freshness and align the window.**\n   `external_table('\u003CTableName>') | summarize Rows=count(), MinTime=min(TimeGenerated), MaxTime=max(TimeGenerated)`.\n   Do not assume `ago(1h)`; use a window covering the actual data range and\n   explain it in user terms.\n6. **Confirm categorical values** used by rules\n   (`external_table('\u003CTable>') | summarize count() by \u003Cfield>`) so impact rules\n   use real categories.\n\n### Telemetry source selection framework (REQUIRED)\n\nTelemetry source selection MUST be **data-driven**. Before selecting a correlation\nmodel, the Skill MUST inspect ALL candidate telemetry sources discovered (e.g.\nAppEvents, AppExceptions, AppRequests, AppDependencies, AppTraces, AppPageViews,\nAppBrowserTimings, AvailabilityResults, and any other telemetry source present) —\nnot just one.\n\nScore each candidate telemetry source by:\n\n1. Business identifiers discovered.\n2. Dynamic-field richness.\n3. Direct-join confidence.\n4. Validated match count.\n5. Business-process context.\n6. Relevance to the selected business goal.\n\nSelect the highest-scoring telemetry source. The Skill MUST NOT automatically\nprioritize AppExceptions, and MUST NOT automatically prioritize AppEvents — the\nwinner is whichever source scores highest against real data.\n\n### Exit criteria (MANDATORY)\n\nBefore Stage 14, ALL must hold: schema retrieved via `getschema`; join keys\nvalidated with non-zero matches (when a direct join is used); freshness verified\nand window aligned; relevant categorical values confirmed. If any fails → STOP,\ndo not proceed.\n\n### Handoff (MANDATORY)\n\nPresent a concise summary (verified join keys, match results, business impact if\nany, data time window). Then ask: \"Do you want to continue to business analysis\n(impact modeling, a dashboard, and optionally an Operations Agent) based on this\nverified model?\" HARD STOP and wait. On confirmation, continue with Stages 13–17\nas defined in\n[references\u002Fbusiness-analysis-workflow.md](references\u002Fbusiness-analysis-workflow.md).\n\n## Stages 13–17 — Business-oriented analysis (defined in the reference)\n\nThe business-oriented analysis half (business data discovery\u002Fscoring, correlation\nplanning, an optional Real-Time KQL dashboard, and an optional gated Operations\nAgent) is defined authoritatively in\n[references\u002Fbusiness-analysis-workflow.md](references\u002Fbusiness-analysis-workflow.md)\n(with Appendices A–B) and loaded only when the user opts in at the Stage 12\nhandoff. On opt-in, **do not work from memory** — open that file and follow\nStages 13–17 exactly; the controller still tracks and enforces these stages, their\norder, hard stops, and confirmation gates (including dashboard-before-agent and\nthe Stage 16 \"do we even want an agent?\" gate).\n\n## Troubleshooting (user-facing)\n\n- **\"No playbook generated\" \u002F cannot compute a field** → the instructions\n  described fields conceptually. Add the explicit KQL materialization query, add\n  per-field KQL definitions, ensure alert rules reference actual output columns,\n  add dynamic-field extraction, and clarify join keys\u002Fidentifiers. Do not just\n  reword prose.\n- **Start succeeds but no Teams alert arrives** → likely no data matched the\n  rule. Switch to POC\u002Fdebug thresholds; explain no data may have matched. Do not\n  imply platform failure without evidence.\n\n## Must \u002F Prefer \u002F Avoid\n\n### Must\n- Enforce stages, hard stops, and confirmation gates.\n- Keep OAuth (UI-guided) and Service Principal (automated create-or-reuse)\n  strictly separate.\n- Validate permissions before creation.\n- Verify schema, dynamic fields, join matches, and freshness before correlation.\n- Provide explicit KQL in Operations Agent instructions.\n\n### Prefer\n- Service Principal (automated) over OAuth (UI-guided) for connection\n  resolution; fall back to OAuth only when Service Principal is unavailable.\n- Direct joins over time-window correlation.\n- Real discovered values over anything guessed.\n- Business-language confirmation over technical questions.\n\n### Avoid\n- Do not depend on or mention MCP in the user-facing flow.\n- Do not present internal\u002Fundocumented APIs as supported.\n- Do not claim OAuth connector creation via public API.\n- Do not fabricate workspaces, tables, schema, IDs, or query results.\n- Do not ask for secrets, OAuth codes, tokens, cookies, or nonces.\n- Do not claim causality when only time-window correlation exists.\n\n## Examples\n\n### Example 1 — Onboard Azure Monitor observability data, then check business impact\n**User:** \"In my `Observability` workspace, onboard our Azure Monitor \u002F Log Analytics observability data (it holds our Application Insights tables) into Fabric, then tell me whether last week's latency spike hurt checkout conversions.\"\n\n**Skill behavior:** Runs the staged workflow — confirms the target workspace and checks onboarding prerequisites (a reachable Azure Monitor \u002F Log Analytics source or connection), stopping with an explicit list of what is missing if any prerequisite is absent. Once the observability data (including the Application Insights telemetry tables) is onboarded and queryable, it discovers the real business dataset in the workspace, correlates the latency signal against the conversion KPI using discovered keys, and reports a specific business-impact conclusion (or an error if the required data is unavailable). It never fabricates workspace names, tables, or query results, and never exposes tokens or connection internals.\n\n### Example 2 — Out-of-scope authoring request\n**User:** \"Create a new Spark notebook and build a Delta table pipeline to load my business dataset.\"\n\n**Skill behavior:** Declines the out-of-scope authoring request, creates nothing in Fabric, and directs the user to the appropriate authoring mode in `spark-cli` rather than taking over the task.\n",{"name":5,"description":7},"main","4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd","skills\u002Fazmon-mirroredcatalogs-operations-cli",395,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 20:10:24",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add microsoft\u002Fskills-for-fabric --skill azmon-mirroredcatalogs-operations-cli",{"tool":59,"command":60},"bunx","bunx skills add microsoft\u002Fskills-for-fabric --skill azmon-mirroredcatalogs-operations-cli",{"tool":62,"command":63},"pnpm","pnpm dlx skills add microsoft\u002Fskills-for-fabric --skill azmon-mirroredcatalogs-operations-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002FSKILL.md",true,[67,73,77,81,85,89,93,97,101,105,109,113,117],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"apm.yml","REFERENCE","参考文档",431,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Fapm.yml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"code-reviewer.md",3385,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fsuperpowers\u002Fskills\u002Frequesting-code-review\u002Fcode-reviewer.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapp-insights-dynamic-fields-reference.md",5939,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fapp-insights-dynamic-fields-reference.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fazmon-fabric-api-reference.md",15862,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fazmon-fabric-api-reference.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fbusiness-analysis-workflow.md",18343,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fbusiness-analysis-workflow.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdashboard-reference.md",6934,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fdashboard-reference.md",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Feventhouse-shortcuts-reference.md",8999,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Feventhouse-shortcuts-reference.md",{"path":98,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fmirrored-catalog-reference.md",5642,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fmirrored-catalog-reference.md",{"path":102,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Foauth-connection-reference.md",2233,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Foauth-connection-reference.md",{"path":106,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Foperations-agent-reference.md",11208,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Foperations-agent-reference.md",{"path":110,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Ftelemetry-table-reference.md",9984,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Ftelemetry-table-reference.md",{"path":114,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fworkspace-discovery-policy-reference.md",3214,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fworkspace-discovery-policy-reference.md",{"path":118,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fworkspace-identity-connection-reference.md",4678,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fazmon-mirroredcatalogs-operations-cli\u002Freferences\u002Fworkspace-identity-connection-reference.md",[122,130,135,160,185,190],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":129},"01M78JNNY5VN2MZ7TSV040K3FJ","fabric-policies-cli","Author, review and manage Microsoft Fabric governance policies and PolicySet items. Invoke before clarifying underspecified lockdown requests or missing intent, identities or scope. Discover current contracts and roles, map scenarios to rules, and execute one approved API lifecycle. Not catalog audits or KQL policies. Triggers: Fabric policy, PolicySet, governance rule, latest Fabric policies, policy contract review.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Ffabric-policies-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":131,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":129},"01M78JNBFP3GAR4MSKEMHY2HDE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Ffabric-policies-cli\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M6PHZNVB6K7DCCJH4YZHKC4F","ontology-cli","Manages Microsoft Fabric Ontology items: authors legacy V1 entity\u002Frelationship definitions and answers questions for new-experience (V2) Ontologies through ask_ontology. Use for Ontology item operations or grounded questions; V2 authoring\u002Fupgrades and V1 queries are unsupported. Power BI data questions use fabriciq, report authoring powerbi-report-cli, and model\u002FDAX changes semantic-model-authoring.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fontology-cli\u002FSKILL.md",[],[35,142,143,144,9,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159],"ontology","ontology cli","ask","operations","bi","microsoft fabric","changes","queries","power bi","relationship","fabriciq","v1","Legacy","use","upgrades","for","model","power",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":39},"01M6PHZ91CSTP67DM6JN8TYEFV","databasehub-cli","Analyzes Database Hub inventory, health, and security posture through Entra-authenticated Fabric APIs. Use for estate counts; SQL\u002FPostgreSQL CPU, storage, and memory; Cosmos DB availability\u002FRU; authentication\u002Fauditing\u002FCMK warnings; and Fabric SQL inventory. Fabric SQL tuning routes to sqldb-cli; Warehouse\u002FLakehouse\u002FMirrored Database SQL to sqldw-cli. Triggers: data estate performance, database estate health, database security posture.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[166],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[35,168,169,170,171,172,173,174,175,157,155,176,177,178,179,180,181,182,183,184],"databasehub cli","database","CPU","database sql","security posture","postgresql","health","database security","triggers","cosmos","authentication","inventory","performance","db","memory","availability","warehouse",{"skillNo":186,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":39},"01M6PHYVDVBD0VQN4FFAMN428Z","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fontology-cli\u002FSKILL.md",[],[35,142,143,157,158,159,152,156,148,9,145,146,147,149,150,151,144,153,154,155],{"skillNo":191,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":39},"01M6PHYDZ17VY69E3GS71KFW09","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills-for-fabric\u002Fblob\u002Fmain\u002Fplugins\u002Ffabric-skills\u002Fskills\u002Fdatabasehub-cli\u002FSKILL.md",[194],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[35,168,184,183,171,181,180,179,170,172,173,174,175,169,155,176,177,182,157,178]]