Forum Discussion
Fabric extensibility toolkit
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.
Community SupportHi 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.