Session
Fabric IQ, KQL, and Activator: Who Actually Enforces the Rule?
Most Fabric teams can write a business rule, but they still have to decide where it runs. Adding that rule to a Fabric IQ ontology gives agents context; it does not automatically evaluate incoming events or trigger an action.
In this session, I’ll use a retail returns case: a recalled product is scanned for restocking. I’ll define the policy against Product and Return entities in Fabric IQ, then send test events through Eventstream into Eventhouse. On screen, we’ll use KQL to identify the affected returns, enrich the stream from a recall reference table, and configure Activator to send a quarantine alert. Next, I’ll change the ontology rule while leaving Activator untouched, so you can see the difference between defining a rule and enforcing it.
You’ll leave knowing when to use ontology, KQL, Eventstream, or Activator, and when a streaming trigger makes more sense than a scheduled KQL check.
**Session Level:** Intermediate to Advanced (Level 300)
**Target Audience:** Microsoft Fabric architects, data engineers, RTI practitioners, solution architects, and technical decision-makers.
**Preferred Duration:** 45–60 minutes, adaptable to a 30-minute conference slot.
**Format:** Technical presentation with a practical, end-to-end demonstration and Q&A.
**Technologies Covered:** Microsoft Fabric IQ, Ontology, Real-Time Intelligence, Eventstream, Eventhouse, KQL, and Activator.
**Prerequisites:** Basic familiarity with Microsoft Fabric. Prior experience with Fabric IQ or ontology is not required.
**Demo:** Uses synthetic retail data to demonstrate how business rules are defined, evaluated, and operationalized across Fabric components.
Mou Rakshit
Avanade, Intelligent Data Platform Data Engineering Thought leadership
Northville, Michigan, United States
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top