Add Fabric Workload for one-click organizational deployment

[Copilot]

Implements Microsoft Fabric Workload packaging to enable one-click deployment of ImpactIQ governance solution into any Fabric tenant via Workload Hub.

Implementation

Workload Structure

• Manifest Layer: WorkloadManifest.xml, Product.json, and GovernanceAnalyzer item type definition with XSD validation
• Frontend: React 18 + TypeScript app with GovernanceAnalyzerItemEditor component using Fluent UI
• Integration: Python (WorkloadIntegration) and TypeScript (GovernanceClient) API clients for notebook execution and Lakehouse data access
• Build System: Webpack 5 with dev/prod configs, PowerShell automation for setup/build/deploy

Key Components

GovernanceAnalyzerItemEditor (React)

const client = createGovernanceClient(workspaceId, lakehouseName);
const result = await client.triggerAnalysis(['Sales', 'Finance']);
const summary = await client.getResults();

WorkloadIntegration (Python)

integration = create_workload_integration(workspace_id, lakehouse_name)
result = integration.trigger_governance_analysis(
    workspace_names=["Sales"],
    max_parallel_workers=5
)

Deployment Modes

• Development: Local dev server with hot reload and dev gateway for Fabric registration
• Organizational: Build manifest NuGet package, deploy to tenant workload registry
• Partner Publishing: Submit to Workload Hub for global distribution

Documentation

Six comprehensive guides:

• README: Setup and quick start guide
• DEPLOYMENT: All deployment scenarios (dev/org/partner)
• TESTING: Testing and validation procedures
• ARCHITECTURE: System architecture with diagrams
• SUMMARY: Implementation overview
• GETTING_STARTED_FOR_CREATORS ⭐ NEW: Step-by-step guide for distributing the workload to other organizations, covering three distribution options (organizational deployment, partner publishing, and open source), with timelines, prerequisites, and customization checklists

Files

• 38 files created (495KB): Manifests, frontend app, integration clients, build configs, PowerShell scripts, assets, documentation
• 2 files updated: Main README with workload callout, .gitignore for node_modules/build artifacts

Integration Points

Connects to existing GovernanceNotebook.py via integration clients. Backend API implementation remains mock-first for development; production requires implementing Fabric notebook execution APIs and Lakehouse SQL queries.

Distribution Guide

The new GETTING_STARTED_FOR_CREATORS.md provides workload creators with:

• Three distribution paths: Organizational (1-2 weeks), Partner Publishing (2-3 months), or Open Source (immediate)
• Detailed step-by-step instructions for each path
• Comparison table to help choose the right approach
• Customization checklist for branding and configuration
• Recommended phased approach: validate internally first, then scale

Original prompt

I am looking to build a new Fabric Workload using the extensibility toolkit - allowing any org to take take this solution and provide a one-click deploy into their environment

Some guidance on taking another stab at building a workload:
Here is our latest toolkit: https://github.com/microsoft/fabric-extensibility-toolkit

Here are some sample workloads that we've developed that might inspire and assist in your building: https://github.com/microsoft/Microsoft-Fabric-tools-workload/

Please build this in its entirety.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[BeSmarterWithData]

@copilot

What are my next steps as the creator of this? I.e. how do i set it up so other orgs can utilize?

[Copilot]

@copilot

What are my next steps as the creator of this? I.e. how do i set it up so other orgs can utilize?

I've created a comprehensive guide specifically for you: Workload/GETTING_STARTED_FOR_CREATORS.md

Three distribution options:

1. 🏢 Organizational Deployment (Recommended start - 1-2 weeks)

Deploy to your own Fabric tenant first:

1. Run npm install and setup scripts
2. Build production version (npm run build:prod)
3. Host frontend on Azure App Service
4. Deploy manifest package to your tenant
5. Enable in Fabric Admin Portal

Best for: Testing and validating before wider distribution

2. 🌍 Partner Publishing (2-3 months)

Make it available globally in Fabric Workload Hub:

1. Join Microsoft Partner Network
2. Set up commercial marketplace account
3. Complete Fabric workload certification
4. Submit to Microsoft for review
5. Go live in Workload Hub

Best for: Reaching all Fabric customers worldwide

3. 🎁 Open Source (Immediate)

Let organizations self-deploy from GitHub:

1. Documentation is ready
2. Tag a release (v1.0.0)
3. Organizations follow your deployment guide
4. They build and deploy to their own tenants

Best for: Maximum flexibility with minimal overhead

Immediate next steps:

1. Complete dev testing in your tenant
2. Customize branding (icons in Workload/Manifest/assets/images/)
3. Update Product.json with your support links
4. Create production Entra app
5. Choose your distribution path

The new guide includes detailed commands, timelines, prerequisites, and a customization checklist.

Commit: d05b099