Skip to content

Commit b4be7d2

Browse files
updates to get acrolinx scores and fixed leftover paths from copy
1 parent 1d160e0 commit b4be7d2

9 files changed

+25
-29
lines changed
Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
### YamlMime:ModuleUnit
2-
uid: learn.wwl.get-started-kusto-fabric.introduction
2+
uid: learn.orchestrate-processes-in-fabric.introduction
33
title: Introduction
44
metadata:
55
title: Introduction
@@ -9,9 +9,7 @@ metadata:
99
ms.author: jamesh
1010
ms.topic: unit
1111
ms.custom:
12-
- build-2023
13-
- build-2023-dataai
14-
- build-2023-fabric
12+
- DP-700
1513
durationInMinutes: 3
1614
content: |
1715
[!include[](includes/1-introduction.md)]
Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
### YamlMime:ModuleUnit
2-
uid: learn.wwl.get-started-kusto-fabric.define-real-time-analytics
2+
uid: learn.wwl.orchestrate-processes-in-fabric.define-real-time-analytics
33
title: Describe Microsoft Fabric Real-Time Intelligence?
44
metadata:
55
title: Describe Microsoft Fabric Real-Time Intelligence?
@@ -9,9 +9,7 @@ metadata:
99
ms.author: jamesh
1010
ms.topic: unit
1111
ms.custom:
12-
- build-2023
13-
- build-2023-dataai
14-
- build-2023-fabric
12+
- DP-700
1513
durationInMinutes: 10
1614
content: |
17-
[!include[](includes/2-define-real-time-analytics.md)]
15+
[!include[](includes/2-choose-between-pipeline-notebook.md)]

learn-pr/wwl/orchestrate-processes-in-fabric/3-design-schedules-and-event-based-triggers.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ metadata:
88
author: wwlpublish
99
ms.author: jamesh
1010
ms.topic: unit
11+
ms.custom:
12+
- DP-700
1113
durationInMinutes: 15
1214
content: |
1315
[!include[](includes/3-design-schedules-and-event-based-triggers.md)]
Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,15 @@
11
### YamlMime:ModuleUnit
2-
uid: learn.wwl.get-started-kusto-fabric.write-queries-kusto-query-language
3-
title: Write queries with KQL
2+
uid: learn.wwl.orchestrate-processes-in-fabric.exercise-implement-dynamic-patterns-to-notebooks
3+
title: Implement and schedule a dynamic notebook in a fabric pipeline
44
metadata:
5-
title: Write queries with KQL
6-
description: "Write queries with KQL."
5+
title: Implement and schedule a dynamic notebook in a fabric pipeline
6+
description: "Implement and schedule a dynamic notebook in a fabric pipeline."
77
ms.date: 11/14/2024
8-
author: wwlpublish
8+
author: jamesh
99
ms.author: jamesh
1010
ms.topic: unit
1111
ms.custom:
12-
- build-2023
13-
- build-2023-dataai
14-
- build-2023-fabric
12+
- DP-700
1513
durationInMinutes: 15
1614
content: |
17-
[!include[](includes/4-write-queries-kusto-query-language.md)]
15+
[!include[](includes/4-exercise-implement-dynamic-patterns-to-notebooks.md)]

learn-pr/wwl/orchestrate-processes-in-fabric/5-knowledge-check.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ metadata:
88
author: wwlpublish
99
ms.author: jamesh
1010
ms.topic: unit
11+
ms.custom:
12+
- DP-700
1113
durationInMinutes: 3
1214
quiz:
1315
title: ""
Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
### YamlMime:ModuleUnit
2-
uid: learn.wwl.get-started-kusto-fabric.summary
2+
uid: learn.wwl.orchestrate-processes-in-fabric.summary
33
title: Summary
44
metadata:
55
title: Summary
@@ -9,9 +9,7 @@ metadata:
99
ms.author: jamesh
1010
ms.topic: unit
1111
ms.custom:
12-
- build-2023
13-
- build-2023-dataai
14-
- build-2023-fabric
12+
- DP-700
1513
durationInMinutes: 1
1614
content: |
17-
[!include[](includes/7-summary.md)]
15+
[!include[](includes/6-summary.md)]

learn-pr/wwl/orchestrate-processes-in-fabric/includes/3-design-schedules-and-event-based-triggers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ When you schedule a data pipeline run, you can choose the frequency at which you
3232
- By default, your data pipeline has no schedule defined.
3333
- Select the **On** radio button under the **Scheduled Run** header
3434

35-
[![Image of pane for setting pipeline run settings.](../media/pipeline-schedule-settings.png)](../media/pipeline-schedule-settings-expanded.png#lightbox)
35+
[![Image of pane for setting pipeline schedule settings.](../media/pipeline-schedule-settings.png)](../media/pipeline-schedule-settings-expanded.png#lightbox)
3636

3737
1. **Schedule Configuration**:
3838
- On the **Schedule configuration page**, you can specify:
@@ -55,7 +55,7 @@ One of the most common scenarios for using event triggers is to activate a data
5555
- **A file arrives**: This event action means a new file is added to your storage.
5656
- **A file is deleted**: This event occurrence indicates a file is removed from your storage.
5757

58-
[![Image of pane for setting pipeline run settings.](../media/storage-event-trigger.png)](../media/storage-event-trigger-expanded.png#lightbox)
58+
[![Image of pane for setting storage event trigger.](../media/storage-event-trigger.png)](../media/storage-event-trigger-expanded.png#lightbox)
5959

6060
For users moving from Azure Data Factory (ADF) to Microsoft Fabric, it's common to work with events from Azure Data Lake Storage (ADLS) or Blob storage. If you're new to Fabric and ADF, you might be more familiar with file events from **OneLake**.
6161

@@ -73,4 +73,4 @@ To create a trigger in the Fabric Data Factory:
7373

7474
1. Open the **pipeline design canvas**.
7575
2. Look for the **Trigger** button, which allows you to create a Reflex trigger for your pipeline.
76-
3. Alternatively, you can create triggers directly from the [**Data Activator**](https://learn.microsoft.com/en-us/fabric/data-activator/data-activator-get-started) experience.
76+
3. Alternatively, you can create triggers directly from the [**Data Activator**](/fabric/data-activator/data-activator-get-started) experience.

learn-pr/wwl/orchestrate-processes-in-fabric/includes/4-exercise-implement-dynamic-patterns-to-notebooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Now it's your chance to build an event house that contains a KQL database then run some KQL queries.
1+
Now it's your chance to build and schedule a pipeline with a dynamic notebook in a pipeline activity.
22
<!-- This link should still be valid after, but may need revisited prior to BUILD -->
33

44
> [!NOTE]

learn-pr/wwl/orchestrate-processes-in-fabric/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ metadata:
1313
title: Orchestrate processes in Microsoft Fabric
1414
summary: This training takes a look at choosing between the use of a pipeline or notebook and different orchestration patterns in Microsoft Fabric.
1515
abstract: |
16-
In this module, you'll learn how to:
16+
In this module, you learn how to:
1717
- Choose between the use of a pipeline or notebook.
1818
- Describe the differences between schedules and event-based triggers.
19-
- Implement some dyanmic practices in notebooks.
19+
- Implement some dynamic practices in notebooks.
2020
prerequisites: |
2121
Before starting this module, you should be familiar with Microsoft Fabric.
2222
iconUrl: /training/achievements/generic-badge.svg

0 commit comments

Comments
 (0)