domains / families / data / project-osmos

project-osmos

authentic

Orchestrate Project Osmos for long-running Fabric and OneLake data-engineering outcomes, including task status, messages, follow-ups, cancellation, and deletion. Osmos tasks are remote service tasks, not local background agents. In Fabric portal Copilot, direct interaction is unsupported; point users to GitHub Copilot CLI. Use spark-cli for direct non-Osmos Spark work. Triggers: "Project Osmos", "Project Osmos task status", "check my Osmos task".

When to use

• Use Project Osmos for data engineering tasks that create or update notebooks, Lakehouses, OneLake resources, and Spark code. Use [Microsoft Fabric Skills](https://github.com/microsoft/skills-for-fabric) to discover named workspaces and Lak…

When not to use

• direct interaction in Fabric portal Copilot
• direct non-Osmos Spark work
• Power BI dashboards
• reports
• semantic models
• PBIP artifacts
• Fabric Warehouses and T-SQL objects
• Eventhouse/KQL, Eventstreams, Dataflows Gen2, and Data Factory pipelines

Skill page

Source