eventstream-authoring-cli

Author and deploy Microsoft Fabric Eventstream topologies via the REST API.

952|267|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/microsoft/skills-for-fabric --skill eventstream-authoring-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eventstream-authoring-cli
Source: https://github.com/microsoft/skills-for-fabric/tree/main/plugins/fabric-authoring/skills/eventstream-authoring-cli
Command: npx skills add https://github.com/microsoft/skills-for-fabric --skill eventstream-authoring-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build, wire, and publish real-time Eventstream topologies for Microsoft Fabric using the Fabric Items REST API, enabling end-to-end event-driven data pipelines.

Core Features & Use Cases

  • Create Eventstreams and define topology with sources, operators, streams, and destinations
  • Deploy, update, and delete Eventstreams in Fabric workspaces
  • Validate topology definitions and manage lifecycle via REST API

Quick Start

Create a new Eventstream topology for your Fabric workspace and deploy it using the REST API.

Frequently Asked Questions about eventstream-authoring-cli

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

FAQPage Schema
How do I create and deploy a Fabric Eventstream topology via REST API?

You create an Eventstream topology by defining sources, operators, streams, and destinations, then deploy it to a Fabric workspace using the Fabric Items REST API. This enables end-to-end event-driven data pipelines programmatically.

What is the best way to automate real-time Eventstream deployment in Microsoft Fabric?

Automating real-time Eventstream deployment involves using the Fabric Items REST API to wire sources, operators, and destinations, then managing the topology lifecycle including updates and deletions within Fabric workspaces.

Can I update or delete existing Eventstream topologies in a Fabric workspace?

Yes, you can update or delete existing Eventstream topologies in Fabric workspaces by sending corresponding lifecycle management requests through the Fabric Items REST API.

How does DefaultStream and DerivedStream routing work in Fabric Eventstreams?

DefaultStream and DerivedStream routing in Fabric Eventstreams directs real-time event data from configured sources through operators to specific destinations, enabling complex topology wiring and stream derivation within the pipeline.

How many sources and destinations can I wire into a Fabric Eventstream topology?

You can wire up to 25 sources, 8 operators, and 4 destinations into a single Fabric Eventstream topology, routing data through DefaultStream and DerivedStream configurations via the REST API.

Do I need the Fabric Items REST API to validate Eventstream topology definitions?

Yes, validating Eventstream topology definitions is handled through the Fabric Items REST API, ensuring that sources, operators, and destinations are correctly wired before deployment to a workspace.