Microsoft Integration

Connect Your Factory to Microsoft's Cloud. Full Context. Full Control.

UMH integrates with your full Microsoft architecture, Fabric, Copilot, Power BI, Azure Arc. Engineers' context is built into the data at the edge and streamed up through the Unified Namespace. Cloud decisions flow back down to the shop floor, validated and controlled.

Discuss your Microsoft architecture

Explore the platform

All major OT protocols, contextualized before they reach the cloud

Built for OT and IT: Management Console, infrastructure-as-code, and agent APIs

Manufacturing data layer for Fabric, Power BI, and the Unified Namespace

Send data to the cloud, receive data back to the factory

Copilot and AI agents access data, never your OT directly

Open source core, no vendor lock-in

Trusted by global enterprises

The Challenge

Microsoft runs your business. Your shop floor doesn't connect to it.

Your shop floor doesn't speak cloud, and connectivity alone doesn't fix it

Factory data lives in PLCs, SCADA systems, and historians that speak OPC UA, Modbus, and S7. Fabric and Copilot expect structured, streaming data. Plain connectivity solutions move data across that gap, but they don't equip it with the context it needs to be useful. That knowledge must be in the data before it reaches the cloud.

Pushing raw data into the cloud is expensive

Sending every tag and signal into Fabric gives you storage bills, not insights. The cloud needs the right data, not all data. Without filtering, contextualization, and structure at the edge, you pay to store millions of data points nobody can interpret. Costs scale with volume. Value doesn't.

Copilot and AI agents need a manufacturing platform they can work with

Copilot Studio and Microsoft Foundry are built for every industry. They need more than data from your factory. They need a platform they can configure, query, and operate. UMH gives AI agents and coding tools CLI, APIs, and infrastructure-as-code they work with natively. Not just a data pipe, but a platform AI can act on.

"With UMH, we gained real-time insight into our production for the first time. The platform’s flexibility allowed us to connect all our machines and drastically reduce manual data work. This has been a game-changer for our efficiency."

Head of Manufacturing IT

Read the full story >

Our solution

The manufacturing data layer for Microsoft's cloud.

UMH sits between your factory and Microsoft's cloud. It connects to every OT protocol, contextualizes data with your engineers' expertise at the edge, and streams it into Fabric through the Unified Namespace. Copilot and Foundry agents access contextualized data through validated interfaces. They never touch your OT.

UMH processes and stores your factory data on-premise. Dashboards, historians, and local applications consume it immediately. The cloud is one destination, not the only one. Your manufacturing data is available on-site first, then streamed into Fabric, enriched and structured.

A manufacturing data layer, not a cloud gateway

Filter noise, enrich with engineering knowledge, combine signals from multiple sources, and enforce semantic models before data reaches the cloud. Machine handbooks, TIA exports, and your team's operational expertise, mapped into the data at the edge. Fabric and Copilot get data with meaning, in a structure they can work with.

Industrial data management with your engineers' context

UMH validates every command before it reaches production. Every action is logged, every access point controlled. AI agents from Copilot Studio or Microsoft Foundry run against UMH, not your machines. The same boundary works for any AI platform, not just Microsoft's.

Guardrails for Copilot, Foundry, and every AI agent

UMH runs natively on AKS Edge on-premise and Azure in the cloud. Arc manages both. No parallel infrastructure, no separate tooling. One operating model from shop floor to Fabric.

One Microsoft operating model

Instant

Add Fabric as a destination to your Unified Namespace. Configuration, not a project.

80% less

Engineering effort to connect the next site via templates and standardized data models.

5x lower cost

AI-assisted data modeling replaces manual system integrator work.

From deployment to AI agents in four steps

Step

Deploy on your Microsoft infrastructure

UMH runs on AKS Edge on-premise and Azure in the cloud, managed through Arc. One deployment, one operating model.

step

•

TEXT

Deploy on your Microsoft infrastructure

Who:

Jeremy (CTO)

Format:

Video call with screen sharing

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

Step

Connect your shop floor

All major OT protocols. Pre-built templates for common vendors. Your engineers add context and enforce data models at the edge.

step

•

TEXT

Connect your shop floor

Who:

Jeremy (CTO)

Format:

Video call with screen sharing

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

Step

Stream into Microsoft's cloud

Contextualized manufacturing data flows into Fabric, Event Hub, and Power BI. Available across your entire Microsoft architecture.

step

•

TEXT

Stream into Microsoft's cloud

Who:

Jeremy (CTO)

Format:

Video call with screen sharing

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

Step

Build AI agents and applications on top

Copilot Studio, Foundry, and your own tools consume data with full manufacturing context.

step

•

TEXT

Build AI agents and applications on top

Who:

Jeremy (CTO)

Format:

Video call with screen sharing

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

The format:

30 minutes to code.
15 minutes to discuss what you'd change to make it production-ready.

At scale: Template one site, replicate across your organization. New sites stream into the same Fabric instance in days.

Frequently asked questions.

What does UMH add to my Microsoft stack?

The manufacturing data layer. UMH connects your shop floor, contextualizes the data at the edge, and streams it into Fabric. Copilot and Foundry agents get data they can work with — not raw machine signals.

What data lands in Microsoft Fabric?

Contextualized, structured manufacturing data. Not raw OPC UA tags, but data with meaning: machine state, production counts, energy consumption, quality metrics — all mapped to your engineers' definitions.

Can Copilot agents write back to my machines?

Only through UMH's validated interface. Every command is checked against your rules before it reaches production. Every action is logged. Agents access data and send commands through UMH, never directly to your OT.

Does UMH work with clouds other than Microsoft?

Yes. The same architecture works with AWS, Google Cloud, and other platforms. UMH is the manufacturing data layer — the cloud is one destination, not the only one.

How does pricing work?

Per-site licensing, not per-connector or per-data-point. Typical investment is $25-50K per year per site. No surprise overages as you connect more machines.

START WITH UMH

Connect your factory to Microsoft's cloud. With data that's ready and AI that's safe.

Talk to our experts about your Microsoft architecture. Or explore the platform yourself, fully open source.

Talk to our team

Explore the platform