W3C Web of Things (WoT) support in Azure IoT Operations

Integration challenges often pose a barrier to the ability to scale industrial solutions. When new or updated assets show up having a new protocol, a slightly different telemetry shape, or an undocumented interface, teams end up rewriting glue code and retesting end-to-end pipelines. Azure IoT Operations reduces that friction by providing a unified data plane at the edge: modular services running on Azure Arc-enabled Kubernetes, with an edge-native MQTT broker as the backbone for reliable, event-driven architectures.

Key concepts 

Azure IoT Operations is Microsoft’s edge platform for running IoT services on Kubernetes via Azure Arc. MQTT is the pub/sub messaging protocol Azure IoT Operations uses for event-driven data movement. OPC UA is a common industrial connectivity standard that can expose rich information models, but many assets don’t implement it directly. W3C Web of Things (WoT) standardizes machine-readable descriptions of an asset’s interface via a “Thing Model.”

We’re announcing a key step toward open, model-driven interoperability in Azure IoT Operations: W3C Web of Things (WoT) is now a first-class modeling input for developer workflows, backed by the Azure IoT Operations SDKs and the code generation (codegen) v2 toolchain.

Why WoT in Azure IoT Operations?

Azure IoT Operations already emphasizes open standards such as MQTT and OPC UA to foster interoperability across OT and IT systems while staying Kubernetes-native and scalable. In practice, though, many assets cannot natively present an OPC UA information model and integration documentation still often arrives as a static PDF.

To scale deployments, teams need a machine-readable asset description they can use for automated onboarding and repeatable pipelines. WoT enables that path for non-OPC UA assets: instead of relying on a PDF, vendors (or integrators) can provide a WoT Thing Model that describes the asset’s telemetry, commands, and properties so onboarding and integration can be automated.

What’s included

The Azure IoT Operations SDKs are a set of tools and libraries (across multiple languages) for building and extending solutions. Within that toolbox, the Protocol Compiler is the centerpiece: it takes an interface model as input and generates client and server code so you can focus on business logic instead of message plumbing. With WoT support, you can use a WoT Thing Model as that input to generate code stubs for telemetry and for mRPC (message-based remote procedure calls used for service-to-service interactions in Azure IoT Operations).

If you’re coming from the DTDL (Digital Twins Definition Language) world, the workflow will feel familiar: the Protocol Compiler takes a model as input and outputs generated client/server libraries in your target language.

When an asset interface and data model are expressed as a WoT Thing Model, you can treat that model as the contract. Generated code then enforces the expected payload shapes for telemetry and mRPC interactions, reducing bespoke glue code and lowering the risk of mismatched or undocumented data.

Eclipse ediTDor as a practical editor for WoT Thing Models

A model-first workflow only works if authoring is approachable. Eclipse ediTDor is an open-source, web-based editor that helps you create and validate W3C WoT Thing Models, including export to JSON-LD (a standard JSON format for linked data). It is hosted by the Eclipse Foundation, and you can try it here: Eclipse ediTDor.

WoT as the asset description that unlocks automation

Putting it all together, a typical workflow looks like this:

1. Start with a WoT Thing Model for the asset (from the vendor, a partner, or authored in-house).
2. Open the model in Eclipse ediTDor to review, validate, and refine it.
3. Use the Protocol Compiler (codegen v2) to generate client/server code stubs for telemetry and mRPC interactions.
4. Deploy your application into an Azure IoT Operations environment running on Azure Arc-enabled Kubernetes and integrate with data services via the built-in MQTT broker.

Getting Started

If you want to explore this further, here are the key starting points:

• Azure IoT Operations SDKs overview and quick start: [Azure IoT Operations Developer Guide]
• Codegen V2 in the SDK repo: Azure IoT Operations SDK
• Eclipse ediTDor for WoT authoring: Edi{td}or
• Azure IoT Operations product overview: [What Is Azure IoT Operations]

Conclusion

With WoT support in Azure IoT Operations, we continue our commitment of building an open, standardized ecosystem where machine-readable asset descriptions are a first-class input to onboarding and development. Combined with the Protocol Compiler and practical authoring options like Eclipse ediTDor, it becomes feasible to go from an asset description to running code with significantly less integration friction.