eventschemaset-cli

Author and inspect Microsoft Fabric Event Schema Sets via the Fabric Items REST API with az rest.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill eventschemaset-cli-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eventschemaset-cli
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/eventschemaset-cli
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill eventschemaset-cli-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing Microsoft Fabric Event Schema Sets (centralized catalogs of event types and message schemas) requires crafting correct REST payloads, base64-encoded definitions, and LRO polling by hand, which is error-prone. This Skill provides guided, mode-based workflows for creating, updating, deleting, listing, and decoding Event Schema Sets through the Fabric Items REST API using az rest. ## Core Features & Use Cases - Authoring mode: Create Event Schema Sets (empty or with an inline definition), rename or re-describe items, override the full eventTypes/schemas definition, and delete items, with LRO polling and confirmation safeguards for destructive actions. - Consumption mode: List and search Event Schema Sets, inspect item properties (OneLake path, sensitivity label), and base64-decode definitions to enumerate event types, schemas, and schema versions. - Use Case: A data engineer needs to add a BusinessEventType event OrderPlaced with a JSON schema to an existing orders-catalog Event Schema Set; the Skill resolves the workspace and item IDs, decodes the current definition, appends the event type, re-encodes the full document, and submits the updateDefinition override. ## Quick Start Ask the AI to list all Event Schema Sets in your Fabric workspace or to create a new Event Schema Set with a given name and event types.

Frequently Asked Questions about eventschemaset-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Event Schema Set in Microsoft Fabric?▼

Create an Event Schema Set by sending a POST request to /v1/workspaces/{workspaceId}/eventSchemaSets via az rest with a displayName and optional base64-encoded definition. The call returns 201 Created or 202 Accepted, in which case you poll the Location header until Succeeded.

How to decode a Fabric Event Schema Set definition?▼

Decode the definition by calling POST .../eventSchemaSets/{id}/getDefinition with an empty JSON body, then select the part whose path is not .platform and base64-decode its payload. The decoded JSON contains the eventTypes and schemas collections.

What is the difference between EventSchemaSet, Eventstream, and Eventhouse in Fabric?▼

EventSchemaSet is a centralized catalog of event types and message schemas, while Eventstream is a real-time ingestion and routing pipeline and Eventhouse is a KQL database item. Use the eventschemaset-cli skill only for the catalog item; Eventstream and Eventhouse have their own dedicated skills.

Does the Fabric Event Schema Set API support service principals?▼

Microsoft Learn documents all Event Schema Set operations as delegated user identity only, with service principals and managed identities not supported. Because the item is in Preview, SP/MI access can succeed depending on the tenant; on 401/403, fall back to az login as a user.

Why does updateDefinition fail with a 400 InputError on format?▼

The service rejects bare Json as a format value; supported formats are JsonSchema, Avro, Protobuf, and XSD. Use versioned values such as CloudEvents/1.0 for eventTypes format and JsonSchema/draft-07 for schemaFormat, schemas format, and each version's format.

Does updating an Event Schema Set definition merge or replace it?▼

UpdateDefinition replaces the entire definition; it is an override, not a merge. You must decode the current definition, apply your changes, and submit the complete document, or any omitted event types and schemas will be dropped.