Fabric Real Time Intelligence (RTI) in a Workshop covers how-to build a Medallion architecture design-pattern by using Real-Time Intelligence.
This asset can be proctor completely by using the MOAW page. See pre-req(s) to setup Fabric Trial Tenant.
Recommend setting up the tenant prior to the day of the event and completing the lab in the “LabAdmin” workspace as cheat-sheet for participants to leverage. Optionally, attendees may use their own Fabric environment, but it is required to enable Real-Time Dashboards (preview) feature to complete the lab (Section 8 – Building the platform).
If desired, on the day of the event the proctor may create a folder called “Workshop” inside the “LabAdmin” workspace to reproduce the lab live (Section 8 – Building the platform).
Alternatively, after completing the theoretical context, instruct the participants to complete the lab on their own, assist them, and help answer questions by having open discussions.
If necessary, you can demo the Fabric Copilot that helps you write KQL queries here.
MS-INTERNAL ONLY: To access "RTA Field Demos" workpace which is an F64 to demo Copilot from a KQL Queryset, join SG "adxdemoenv" on IDWeb via MSFT VPN.
See Introduction section for more info. Proctors may contact: fabricvbdtechleads[at]microsoft[dot]com or rtacat[at]microsoft[dot]com if you need help preparing for your delivery or have additional questions.
This asset can be proctor completely by using the MOAW page.
If desired, cover the introduction & theoretical context first, or simply skip ahead to Section 8 – Building the platform. The presentation is not required (can only be shared in PDF-format externally). However, the intro & theoretical context should take approximately 30-60 minutes. The purpose is not to read everything verbatim. Attendees will have access to review the MOAW in detail afterwards.
10m Break
Proceed to execute the Hands-On Lab (Section 8 - Building the platform). This should take approximately 1-2 hours. During which time allot for open discussion, questions-and-answers and breaks as necessary.
Conclude the workshop with "Section 9 - Continue your learning" or position a POC next.
Important Links - Readiness
- Real-Time Intelligence Tutorial
- Real-Time Intelligence Tutorial - GitHub
- Building a Real-Time medallion architecture using Eventhouse in Microsoft Fabric
- (MS internal-only) Evaluation form collaborator link to edit & view responses.
- (MS internal-only) Recording of RTI talking points
- Public recordings available in "section 9 - Continue your learning" of the MOAW.
- Download the JSON file of the pre-built dashboard.
- From the Real-Time Intelligence menu, select the Real-Time Dashboard option.
-
Name it "RTA Dashboard" and select Create.
-
From the Manage tab, select "Replace with file" option. Find the downloaded JSON file and select Open.
-
The Dashboard should repaint with the Adventure Works logo displayed, but the other dashboard titles showing error text.
-
The Data Sources side bar will appear. There will be one source listed, select the pencil icon beside the "RTAdemo" title.

-
The Edit Data Sources side bar will appear. Confirm the "Data Source Name" and "Database" have "RTAdemo" selected. Then select Apply.

-
The dashboard will quickly repaint, and the visuals will appear.

Symptom - The "Generate synthetic events" notebook doesnt run or just seems to hang once the Run all button has been selected.
Resolution - Stand up a compute environment and run the notebook using that.
Steps From "8. Building the platform" > "Step 6. Run the notebook";
-
On the Notebook top menu, toggle the "Workspace default" drop box and select the New Environment option.

-
This will present the environment configuration screen, which requires no change. Navigate back to the "Generate synthetic events" notebook.
-
The new environment will now appear in the "Workspace default" drop box, select it. This will attach the notebook to that environment and you will see a callout for Updated environment in the notification tab.

-
Click Run all at the top left to re-run the notebook.
-
Verify that the last code cell is printing out the generated synthetic events in JSON format.

Symptom - The "Generate synthetic events" notebook runs, but doesnt progress past the first cell raising a number of python packaging errors.
Resolution - Restart the process from the next cell.
Steps From "8. Building the platform" > "Step 6. Run the notebook";




