Welcome to the Fabric workload development documentation. This comprehensive guide covers everything you need to know to create a custom Fabric workload for your organization. We’re here to assist you every step of the way, so please don’t hesitate to reach out with any questions. Happy developing!
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
Microsoft Fabric is a comprehensive analytics solution designed for enterprise-level applications. This platform encompasses a wide range of services, including data engineering, real-time analytics, and business intelligence, all consolidated within a single, unified framework.
The key advantage of Microsoft Fabric is its integrated approach, that eliminates the need for distinct services from multiple vendors. Users can leverage this platform to streamline their analytics processes, with all services accessible from a single source of truth.
Microsoft Fabric provides integration and simplicity, as well as a transparent and flexible cost management experience. This cost management experience allows users to control expenses effectively by ensuring they only pay for the resources they require.
The Fabric platform is not just a tool, but a strategic asset that simplifies and enhances the analytics capabilities of any enterprise. For more information about Fabric click here.
In Microsoft Fabric, workloads signify different components that are integrated into the Fabric framework. Workloads enhance the usability of your service within the familiar Fabric workspace, eliminating the need to leave the Fabric environment for different services. Data Factory, Data Warehouse, Power BI and Fabric Activator are some of the built-in Fabric workloads.
With the Workload Development Kit, you can create your own workload for your data applications. Publishing a Fabric Workload to the Fabric Workload Hub increases your application’s discoverability and user engagement. The Microsoft Fabric Workloads Development Kit provides the necessary tools and interfaces to embed your data application into Microsoft Fabric.
For more information on what workloads can offer Microsoft partners, and for useful examples, head to our official Workload Dev Kit documentation.
You can also learn more about the Fabric workload architecture here.
This is a robust mechanism designed to enhance the existing Fabric experience by integrating custom capabilities. The entire Fabric platform has been engineered with interoperability in mind, allowing for others to seamlessly incorporate their own workload capabilities.
The Fabric workspace includes various components, known as Fabric items, which handle the storage, analysis, and presentation of your data. You can leverage the item editor to create a native, consistent user experience by embedding your application within the context of a Fabric workspace item.
Fabric workloads integrate with Microsoft Entra Id for authentication and authorization. All interactions between workloads and other Fabric or Azure components necessitate proper authentication support for incoming and outgoing requests, ensuring correct generation and validation of tokens.
This represents user permissions pertaining to the workspace and specific items. It is utilized to inherit user permissions and applied as part of provisioning resources (see Roles in workspaces in Power BI - Power BI | Microsoft Learn).
The monitoring hub provides a comprehensive view of all background jobs to Fabric users, enhancing transparency and control.
Our architecture is designed to integrate flawlessly with OneLake, enabling operations such as saving, reading, and fetching data. This interaction is facilitated facilitated through OneLake APIs, ensuring secure and authenticated communication. Learn more about OneLake here.
Head to our documentation for a step-by-step guide to getting your environment set up and your first workload up and running: Getting Started.
After you have completed the initial guides on spinning up your sample workload, follow along on our Frontend and Backend implementation guides to learn more about how to start developing a custom workload for your application.
After developing your Fabric Workload according to the certification requirements, you can publish it to the Workload Hub which will allow every Fabric user a chance to easily start a trial experience and then buy your workload. An in-depth description of how to publish a workload can be found here.
Here are all the resources included and referenced. These documents provide additional information and can serve as a reference:
- WDK Documentation
- Quickstart Guide
- Workload Architecture
- Authentication Overview
- OneLake
- One Lake APIs
- Frontend Configuration Guide
- Backend Implementation Guide
- DevGateway Container Setup Guide
- Backend API Requests Authentication Overview
- Monitoring Hub Configuration Guide
- Backend REST APIs
- Publish a workload to the Workload Hub
