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

CRITICAL NOTES

1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
2. To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
3. Skill disambiguation: use eventschemaset-cli for the EventSchemaSet catalog item (event types and message schemas). Eventstream is a different item -- a real-time ingestion and routing pipeline; use eventstream-cli for it. Eventhouse / KQL Database is another different item; use eventhouse-cli for it.

Fabric Event Schema Set -- CLI Skill

This one skill owns Fabric Event Schema Sets: authoring the catalog (create, rename, override definition, delete) plus read-only inspection and decoding of its eventTypes and schemas.

Preview: The Fabric EventSchemaSet item and its REST operations are currently in Preview -- behavior, response shapes, and availability may change. Every operation is documented as delegated (user) identity only (service principals and managed identities listed as not supported), but because the item is in Preview, SP/MI access can succeed and is tenant-dependent. Prefer az login as a user; on 401/403 with an SP/MI, fall back to a delegated user identity.