Blog Post

Fabric Updates Blog
3 MIN READ

Cross-domain intelligence with Azure Monitor data in Microsoft Fabric (Preview)

IlanaWaitser's avatar
IlanaWaitser
Icon for Microsoft Employee rankMicrosoft Employee
1 month ago

The challenge: Disconnected monitoring and business data

In many organizations, observability, operational, and business data live in separate data silos. While Microsoft Fabric provides a unified data foundation in OneLake for business and operational data, observability data is often disconnected. As a result, organizations can detect issues quickly but struggle to understand their full business impact and determine the right response.

Consider a self-check-in kiosk failure at an airport. The technical signal alone doesn't reveal how many customers are impacted, which flights are at risk, or how operational costs may be affected. The signal is only the trigger. The right decision depends on the broader business context.

As systems grow more complex, incidents no longer affect just systems—they affect customers, revenue, and operations in real time. By the time business impact is fully understood, opportunities to proactively mitigate that impact may already be lost.

The solution: Cross-domain intelligence

By bringing Azure Monitor telemetry together with operational and business data—such as ERP and CRM—organizations can reason and act across domains.

To enable cross-domain intelligence, Azure Monitor Logs mirroring into Microsoft Fabric (Preview) now available.

In just a few steps, telemetry from a Log Analytics workspace becomes available in OneLake alongside business data—without duplication, at no additional cost, and with near real-time availability. All Azure Monitor Logs tiers are supported—Analytics, Basic, and Auxiliary logs.

Figure: Start mirroring Azure Monitor Logs into Microsoft Fabric.

This creates the foundation for:

  • Cross-domain real-time insights and actions:
    • Signals are evaluated with full business context, not as isolated alerts—so you can see who and what is affected, and how much it's costing.
    • Signals turn into operational and business action—triggering the right response to mitigate the business impact of incidents before it grows.
  • Advanced Fabric analytics—using tools like Spark and Power BI for long-term analysis, machine learning, and a wide range of analytical scenarios.

Scenario in action: Airport check-in disruption

At Zava Airport, self-check-in kiosks stream telemetry into Azure Monitor. Following a deployment issue, customers are unable to complete self check-in.

The Operations Agent detects the problem, enriches it with business context from ERP and CRM systems, and helps Vic, the operations manager, quickly understand that high-value loyalty customers are affected and that operational costs are rising. Based on this context, Vic approves the Operations Agent’s recommendations to open a dedicated counter to reduce customer impact and to escalate the issue to IT for faster resolution, given the high business impact.

Instead of reacting after the fact, she makes decisions in the moment, based on full business context.

Learn how organizations can move from operational signals to business action:

So how is this powered in Fabric?

Behind the scenes: How it’s built in Fabric

This experience is powered by a simple, unified setup in Fabric:

  • Azure Monitor Data in OneLake - Telemetry logs from Log Analytics workspace are brought in via Mirrored Azure Monitor item—without duplication.
  • Cross-domain data ready in Eventhouse - Telemetry and business data (such as ERP and CRM) are made available in one place—ready for real-time cross-domain analysis and action.
  • Real-time analytics and action - Real-Time Dashboard and the Operations Agent run on this combined data—triggering automated actions across systems.

Together, this creates a continuous flow from data to insight to action—all on a unified data foundation.

Learn how this solution is built in Microsoft Fabric:

Key takeaways

What this scenario demonstrates is a fundamental shift in how organizations operate:

  • Multiple data domains, unified in OneLake — Breaking the silos: Business data (such as ERP, CRM) and Observability data in one place without copying data.
  • Real-time reasoning across domains — Signals are evaluated together in seconds—not passed sequentially between teams.
  • Drive action, not just reports — The system detects, decides, and triggers actions based on all available context.
  • Coordinated actions from a single event — One incident can drive multiple outcomes across the teams within the same workflow.

Looking ahead

Fabric IQ and Ontology will further enrich this experience by helping organizations model business entities and relationships across domains, enabling even deeper understanding of business context.

Next steps

Explore how Azure Monitor data and business data come together in Microsoft Fabric to enable cross-domain intelligence, analytics, and action.

We'd love to hear how this experience works for you. Drop us a comment or reach out to our team your input directly shapes what comes next.

Updated 1 month ago
Version 1.0
No CommentsBe the first to comment