After Activator detects that a condition or pattern has been met, the next step is to trigger an action.
Actions are what turn analytics into operational responses — they ensure that insight leads directly to something happening.
Actions can be either internal or external:
Internal actions occur within Fabric — for example, updating a dataset, refreshing a Power BI report, or writing a new event back into an Eventstream.
2026-07-26
In many real-time systems, a single event on its own doesn’t tell the full story. Pattern detection allows you to identify sequences or combinations of events that together indicate something meaningful.
For example, a single failed login attempt is rarely an issue, but multiple failed logins within five minutes could suggest a security concern. Similarly, a single temperature reading above normal might not matter, but a rising trend over time could signal equipment failure.
2026-07-24
In Activator, rules are the core element that make automation possible. A rule defines the condition you want the system to look for in your data — the point at which something should happen.
Rules can be simple or complex.
A simple example might be: temperature > 90°C or error rate exceeds 5%. These are fixed thresholds — clear, measurable values that indicate when a limit has been crossed.
2026-07-22
Before you start creating rules in Activator, it’s important to understand how the system models data conceptually — using Objects and Signals.
An Object in Activator represents a real-world entity that you want to monitor — for example, a sensor, a customer account, a store, or a device.
Each Object has one or more Signals, which are the measurable data points associated with it. For example, a device object might have signals like temperature, battery level, and status.
2026-07-20
Fabric Activator is the part of Microsoft Fabric that connects real-time insights with automated actions — it’s what makes analytics operational.
At its core, Activator is a no-code service that continuously monitors incoming data from Eventstreams or from KQL queries running on KQL Databases.
It looks for specific conditions that you define — things like a metric crossing a threshold, an anomaly appearing in a time series, or a custom pattern detected across multiple events.
2026-07-18
The Digital Twin Builder in Microsoft Fabric Real-Time Intelligence is a design surface for representing real-world systems as manageable, structured entities inside Fabric.
A digital twin is essentially a logical model of something in the real world—such as a device, customer, room, vehicle, or any other object that produces events or has measurable state. The new builder allows you to define these entities directly within the Fabric experience without requiring a separate digital twin service.
2026-07-16
Fabric Maps allow you to visualize spatial data as it changes in real time. When integrated with Real-Time Intelligence, you can stream live data directly from Eventstreams or query current states from KQL databases.
Each map layer can represent different metrics — such as sensor status, delivery vehicle locations, or regional anomalies — updated continuously as new events arrive.
You can also apply time slicers and filters to replay historical activity, helping to analyze event sequences over time.
2026-07-14
Dashboards are an effective way to visualize data, but not every use case involves a person watching a screen.
In many organizations, the most valuable insights come when real-time intelligence is embedded directly into operational systems.
Microsoft Fabric makes this possible by allowing you to expose query results as APIs — typically REST endpoints built on top of KQL Databases. This means that the same data you’re using in dashboards can also be made available to web or mobile applications, business workflows, or partner integrations.
2026-07-12
In the past, if you wanted a real-time Power BI dashboard, you had to use streaming datasets — data pushed directly into Power BI from an external source.
While that approach worked, it came with significant limitations: the data couldn’t easily be joined with historical information, retention was limited, and managing the push model was complex.
That model is now deprecated — streaming datasets shouldn’t be used for new solutions.
2026-07-10
Thresholds are great for simple conditions — but they fall short when what’s normal changes throughout the day, week, or season. That’s where anomaly detection comes in.
Instead of relying on fixed limits, anomaly detection uses statistical and machine learning techniques to model what’s normal for a given signal, then flag data points that deviate from that pattern.
For example, network traffic might be high during business hours but low overnight — a single static threshold would either miss issues or trigger constant false alarms. Anomaly detection adjusts dynamically, recognizing these natural variations in the data.
2026-07-08
