Forum Discussion
Fabric extensibility toolkit
Hello all, Iam trying to create a custom workload in fabric, i have setup the hello world workload. I need help in customizing it as per my requirements, if you have any resources on how to modify frontend, backend, security please share it with me. Also please tell me about your experiences with workload creation.
Hi toshi_n,
Thank you for reaching out to the community. It’s great to hear that you have set up the Hello World workload using the Fabric Extensibility Toolkit. If you’d like to customize it further, you can start by editing the frontend components in the “src/frontend” folder to adjust the UI, add new elements, or set up routes and panels. Make sure to update the manifest configuration file so your changes are recognized by Fabric.
For backend changes, use the “src/backend” directory, which is usually built with Node.js. Here, you can expand API endpoints, add new features, or connect to external services. Don’t forget to keep the manifest updated with the right service definitions for proper integration.
Regarding security, Fabric workloads use Microsoft Entra ID (Azure Active Directory) for authentication. You can set role-based permissions and secure API calls through the manifest, ensuring only authorized users have access.
It’s also helpful to review Fabric workload samples, as they show common patterns for customization and best practices. Many developers find that getting the manifest and Entra ID permissions set up correctly is key to a smooth customization process.
Build Your Workload - Microsoft Fabric | Microsoft Learn
Microsoft Fabric Extensibility Toolkit - Microsoft Fabric | Microsoft Learn
Extensibility Toolkit overview - Microsoft Fabric | Microsoft Learn
Implementation guide - Microsoft Fabric | Microsoft Learn
Implement the Microsoft Fabric backend - Microsoft Fabric | Microsoft Learn
Thank you.
7 Replies
Hi toshi_n,
Thank you for reaching out to the community. It’s great to hear that you have set up the Hello World workload using the Fabric Extensibility Toolkit. If you’d like to customize it further, you can start by editing the frontend components in the “src/frontend” folder to adjust the UI, add new elements, or set up routes and panels. Make sure to update the manifest configuration file so your changes are recognized by Fabric.
For backend changes, use the “src/backend” directory, which is usually built with Node.js. Here, you can expand API endpoints, add new features, or connect to external services. Don’t forget to keep the manifest updated with the right service definitions for proper integration.
Regarding security, Fabric workloads use Microsoft Entra ID (Azure Active Directory) for authentication. You can set role-based permissions and secure API calls through the manifest, ensuring only authorized users have access.
It’s also helpful to review Fabric workload samples, as they show common patterns for customization and best practices. Many developers find that getting the manifest and Entra ID permissions set up correctly is key to a smooth customization process.
Build Your Workload - Microsoft Fabric | Microsoft Learn
Microsoft Fabric Extensibility Toolkit - Microsoft Fabric | Microsoft Learn
Extensibility Toolkit overview - Microsoft Fabric | Microsoft Learn
Implementation guide - Microsoft Fabric | Microsoft Learn
Implement the Microsoft Fabric backend - Microsoft Fabric | Microsoft Learn
Thank you.Hi toshi_n,
Just wanted to follow up and confirm that everything has been going well on this. Please let me know if there’s anything from our end.
Please feel free to reach out Microsoft fabric community forum.Thank you.
Hi toshi_n,
.Just a quick check-in! Has your issue been resolved with the information we shared? We’d be delighted to help further if needed.
Thank you.
The fabric extensibility toolkit does not have src/frontend and src/backend. Its previous version which is workload development kit had those files.
Hi toshi_n,
Thank you for bringing that up. The new Fabric Extensibility Toolkit no longer follows the old src/frontend and src/backend structure used in the previous Workload Development Kit. Instead, it uses a different layout, where most customization is done through the manifest, capability files, and the components registered via extension entry points. UI elements, commands, panels, and actions are now defined in these configuration files, rather than in separate frontend or backend folders.
Thank you.
Thanks for the quick response. Just a follow up question, is there any documentation or tutorial that explains this part of the workload development. Also does changing config files means we don't need a frontend developer as resource? Any other resources that answers the how to part would be helpful.
Hi toshi_n,
The official documentation here I mentioned below explains the new customization model in the Extensibility Toolkit. With the updated toolkit, there are no separate frontend or backend folders; all UI, behavior, and security settings are managed through the manifest, capability files, and extension entry points. The docs cover how to extend panels, commands, item types, and set up authentication with Entra ID. As for your question about frontend developers, you’ll still need one for most real-world scenarios since the toolkit loads your web app, and the manifest only tells Fabric how to display it. Backend developers are only necessary if you need custom APIs, but frontend work is still required for more than basic configuration.
Please see the below-listed documents for detailed information.
Extensibility Toolkit overview - Microsoft Fabric | Microsoft Learn
Manual Step by step guid to configure the development environment - Microsoft Fabric | Microsoft Learn
Getting Started with the Extensibility Toolkit - Microsoft Fabric | Microsoft Learn
Authentication overview for Microsoft Fabric Extensibility Toolkit - Microsoft Fabric | Microsoft Learn
Get started with Fabric Extensibility Toolkit - Microsoft Fabric | Microsoft Learn
Build Your Workload - Microsoft Fabric | Microsoft Learn
Thank you.
