Microsoft Fabric Updates Blog

Empowering Workload Developers with Language Choice and Simplicity

Celebrating Enhanced Flexibility in the WDK Sample

We’re thrilled to announce a major step forward for the Workload Development Kit (WDK): developers can now transform our workload sample into their favorite programming languages.

Whether you prefer Python, Java, Node.js, or Go, we’ve made it easier to start building innovative workloads with the tools and languages that feel most natural to you. This expansion is all about empowering creativity and removing barriers, so you can focus on delivering value and bringing your ideas to life faster than ever.

Generate Python service with swagger file.

Generating a backend service in Python using the WDK sample.

A New Guide for Any Language, Any Stack

To make workload development more accessible, we’ve published a new guide that demonstrates how to implement the same service logic showcased in our Workload Sample using any language you choose.

To learn how to Set up a Microsoft Fabric workload back end by using the OpenAPI Specification (Swagger) refer to the documentation.

We will walk through how to:

  • Generate server stubs in your preferred language using the Swagger file provided in the WDK Sample.
  • Implement the required endpoints and controllers.
  • Test your service locally or in the cloud, without needing to install.NET or write a single line of C#.

If you want to learn more about how to leverage tools like Flask, FastAPI, Express, Spring Boot to achieve this level of flexibility, you’re in the right place!

Positioning for WDK’s Growth and Scalability

As the Workload Development Kit expands, additional samples, templates, and tools will be released for a variety of workloads. Some resources will utilize C#, but they can be adapted to other programming languages as needed.

By providing materials that support multiple programming languages, the aim is to enable broader collaboration and accommodate diverse development needs. These resources are intended to be applicable to projects ranging from cloud-based deployments to local prototyping, with the goal of improving accessibility and supporting development efforts.

Start Building Your Way

We’re committed to making workload development easier, more flexible, and more inclusive.

If you’ve been waiting for a way to implement workload service logic in Python, Node.js, or another language—checkout our guide and join the growing community of developers building innovative Fabric workloads—without the .NET learning curve.

To learn how to Set up a Microsoft Fabric workload back end by using the OpenAPI Specification (Swagger) refer to the documentation.

We look forward to hearing your feedback!

Next Steps

To learn more, refer to the Microsoft Fabric Workload Development Kit documentation.

Related blog posts

Empowering Workload Developers with Language Choice and Simplicity

April 9, 2026 by Sakshi Jain

Background Currently, many items rely on the item’s owner identity for accessing connections and certain features (like delegated mode in SQL endpoint) specific to the item. If the owner leaves the organization or their credentials expire, items can become partially or fully non-functional. We’ve heard from many of you that the current remediation path (like … Continue reading “Associated identities for items (Preview)”

April 8, 2026 by Yulia Turchin

 Have you ever accidentally deleted something important? With Item recovery in Microsoft Fabric (Preview), you no longer need to worry. You can easily restore deleted items—whether it was a mistake or something unexpected—within a retention window you control.