// the find
Azure/Industrial-IoT
OPC Publisher
Microsoft's official OPC UA telemetry publisher for Azure IoT Edge — it discovers industrial assets speaking OPC UA and republishes their data as PubSub telemetry (JSON, JSON+Gzip, or UADP) to IoT Hub, MQTT, or HTTP. This is for engineers building industrial/OT data pipelines on Azure, not a general-purpose OPC UA library.
Version 3.0 rewrote the encoder to publish through the actual UA-.NETStandard PubSub runtime instead of a hand-rolled encoder, which means telemetry framing now comes from the reference stack rather than a Microsoft-specific reimplementation. It ships a formal threat model (STRIDE .tm7 file plus a dataflow doc) and explicitly calls out a security review before enabling the new MCP tool server, which is rare rigor for something that can write to control systems. There's real deployment tooling beyond a Dockerfile: IoT Edge ARM templates, Helm charts, and simulation stacks (opc-plc, umati) so you can exercise the pipeline without real hardware attached.
Two of the three control planes (HTTP, MQTT) are still Preview — IoT Hub device methods is the only GA path, so picking anything else ties you to an unstable API. The 2.9→3.0 migration is a hard break: Samples/FullSamples messaging modes and Avro encoding are removed outright, and a deployment still configured for either fails to start rather than falling back. Support is best-effort via GitHub issues on roughly a monthly patch cadence, which is thin for something running as production OT infrastructure. The new --mcp flag hands an agent read/write access through the same authenticated endpoint as the rest of the control plane — powerful, but it's an opt-in flag rather than something scoped or reviewed per deployment.