Skip to content
MaestroHub
Menu
Free trialdownload and run it todayStart the pilot

Integrations

OPC UA to Microsoft Fabric, without a script.

Read the OPC UA nodes with MaestroHub on site, give them names, units and quality, and write them into a Fabric lakehouse through OneLake with Entra ID authentication. Outages to Azure are buffered on disk.

The flow

One value, from the machine to Microsoft Fabric. Illustrative.

OPC UAindustrial protocolns=2;s=Boiler1.Steam
MaestroHub

Boiler 1 steam flow · 8.2 t/h · Good

  • named, unit, quality
  • origin stamped
  • buffered on disk
Microsoft Fabriclakehouse (OneLake)Files/plant/boiler1/

Why do it with MaestroHub

More than a pipe from OPC UA to Microsoft Fabric.

01

Enterprise identity all the way

Writes use a service principal or managed identity in Entra ID, the way your IT team already secures Fabric.

02

Clean lakehouse files from day one

Named, typed values with quality, instead of raw node dumps.

03

Runs on site, not in the cloud

MaestroHub sits next to the machines and only sends what you choose to Fabric.

What lands in Microsoft Fabric

An example. You choose the fields in the pipeline.

tsassetsignalvalueunitquality
2026-10-03 06:00:01utilities/boiler1steam_flow8.2t/hgood

Set it up in three steps

  1. 1

    Connect OPC UA

    Add the OPC UA server, browse its address space and pick the nodes, or add hundreds at once with bulk creation.

  2. 2

    Give the values meaning

    Map each value to a topic in the namespace with its name, unit and schema. Quality and origin are stamped on every value.

  3. 3

    Deliver to Microsoft Fabric

    Add a OneLake output with Entra ID credentials and write to the lakehouse's Files or Tables area.

Before you start

What each side needs, from the connector documentation.

OPC UA

  • The server address, built as opc.tcp://host:port/path. The standard OPC UA port is 4840.
  • For any Security Policy other than None, a client certificate: paste your own (RSA keys only) or let MaestroHub generate a self-signed one.
  • If you use the auto-generated certificate, the OPC UA server administrator must trust it on the server.
  • A username and password when the server does not allow Anonymous access.

Example settings

Server Hostname
opcua.example.com
Port
4840
Security Policy
Basic256Sha256
Security Mode
SignAndEncrypt
Certificate Mode
Auto-generate (self-signed)
Authentication Type
UsernamePassword
OPC UA connector documentation

Microsoft Fabric

  • The Fabric workspace and lakehouse, by ID (GUID) or by name. Give the lakehouse name without the .Lakehouse suffix.
  • A Microsoft Entra ID identity: a service principal (tenant ID, client ID, client secret), a managed identity when MaestroHub runs on Azure, or the default credential chain.
  • Contributor, or a OneLake data role, on the target workspace for that identity.

Example settings

Authentication Method
service_principal
Workspace
<your-workspace>
Lakehouse
<your-lakehouse>
Tenant ID
<your-tenant-id>
Client ID
<your-client-id>
Default Scope
Files
Microsoft Fabric connector documentation

Things to know

Pitfalls and limits the documentation calls out, so they don't surprise you on site.

OPC UA

  • Security Policy and Security Mode must agree. Policy None requires Mode None. Any other policy requires Sign or SignAndEncrypt.
  • Node identifiers need a namespace index and a type prefix (i=, s=, g=, b=). Namespace 0 is typically standard nodes, 2 and up custom nodes. Browse a small scope first to find the exact IDs.
  • On Monitor functions, set the sampling interval equal to or faster than the publishing interval, or changes can be missed. Subscriptions are recreated automatically after a lost connection or a session timeout.

Limits

  • Manual client certificates support RSA keys only. Auto-generated certificates are RSA 2048-bit and valid for 365 days.
  • Monitor functions cannot be created through Quick Add. Use the full Function Builder.

Microsoft Fabric

  • A Parquet file written under Tables/ does not become a table; it lands in the unidentified area. Write it under Files/ and convert it with Load to Tables, a notebook, or the Fabric Load Table REST API.
  • Set Input Format to base64 for binary files such as Parquet. Left on text, the base64 characters themselves are uploaded and no Parquet reader can open the file.
  • Paths that do not start with Files/ or Tables/ get the Default Scope prepended (Files by default).

Limits

  • The connector writes files only. It does not run SQL, manage Fabric items or create tables.
  • Files are limited to 124 MB (25 MB by default), measured on the decoded bytes.

What teams use it for

Power BI on plant data

Operational KPIs in reports alongside finance and supply chain.

Utility and energy tracking

Steam, power and water per asset for cost allocation.

Data science in Fabric

Notebooks on clean, quality-flagged time series.

Ways to connect OPC UA to Microsoft Fabric

In general terms. Check any specific product for its own details.

Compare a custom script, a flow tool, a cloud vendor's edge service and MaestroHub

Swipe sideways to see every column

A custom scriptA flow toolA cloud vendor's edge serviceMaestroHub
Talks OPC UAA library you chooseCommunity plug-insDepends on the vendorBuilt in, one of 90+ connectors
Names, units and schemaYou write itYou build itPartly, in the vendor's modelOne governed namespace
Quality on every valueYou write itYou build itDepends on the vendorBuilt in, carried through calculations
Where each value came fromYou write itYou build itDepends on the vendorStamped on every value
Survives a network outageYou build itYou build itUsually, to that vendor's cloudOn disk, per destination, in order
Several destinations at onceOne script eachYes, flow by flowMostly that vendor's cloudAny mix, each with its own buffer
Permissions and auditYou build itYou build itCloud account permissionsRoles, single sign-on, audit trail
AI agents can use the dataYou build itYou build itDepends on the vendorThrough the MCP server

Questions

How do I send OPC UA data to Microsoft Fabric?

Read the OPC UA nodes with MaestroHub on site, give them names, units and quality, and write them into a Fabric lakehouse through OneLake with Entra ID authentication. Outages to Azure are buffered on disk.

Do I need to write code to connect OPC UA to Microsoft Fabric?

No. You configure the OPC UA connection and the Microsoft Fabric output in MaestroHub and join them with a pipeline. Transformations can be added where you need them.

Where does MaestroHub run for this?

On your own infrastructure next to the machines: an edge box, a virtual machine or Kubernetes. Nothing has to leave your network.

Why not just write a script for OPC UA to Microsoft Fabric?

A script works on day one. The cost comes later: decoding and naming values, handling bad quality, buffering through outages, keeping credentials safe, and doing it again for the next machine and the next destination. MaestroHub does those once, for every connector.

What else can OPC UA data go to?

More than 90 connectors are included in every edition, among them historians, databases, cloud warehouses, message brokers and business systems, so the same values can feed several destinations at once.

Try OPC UA to Microsoft Fabric yourself.

The free trial includes every connector. No factory to hand? The Digital Factory Simulator serves OPC UA, Modbus, MQTT and more on your laptop.

Cookie preferences

Choose which categories of cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.