You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/how-to-send-notifications-to-teams.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,23 +24,23 @@ Before you can send notifications to Teams from your pipelines, you must create
24
24
25
25
:::image type="content" source="media/how-to-send-notifications-to-teams/teams-incoming-webhook-connector.png" alt-text="Shows the Incoming Webhook app under the Apps tab in Teams.":::
26
26
27
-
1.Click the "Add to a team" button to add the connector to the Team or Team channel name site where you want to send notifications.
27
+
1.Select the "Add to a team" button to add the connector to the Team or Team channel name site where you want to send notifications.
28
28
29
29
:::image type="content" source="media/how-to-send-notifications-to-teams/teams-add-connector-to-site.png" alt-text="Highlights the "Add to a team" button for the Incoming Webhook app.":::
30
30
31
31
1. Type or select Team or Team channel name where you want to send the notifications.
32
32
33
33
:::image type="content" source="media/how-to-send-notifications-to-teams/type-a-team-or-team-channel-name.png" alt-text="Shows the team selection prompt on the Incoming Webhook app configuration dialog in Teams. Type the "Team or Team channel name"":::
34
34
35
-
1.Click the "Set up a connector" button to set up the Incoming Webhook for the Team or Team channel name you selected in the previous step.
35
+
1.Select the "Set up a connector" button to set up the Incoming Webhook for the Team or Team channel name you selected in the previous step.
36
36
37
37
:::image type="content" source="media/how-to-send-notifications-to-teams/teams-prod-notifications.png" alt-text="Shows the team selection prompt on the Incoming Webhook app configuration dialog in Teams. Highlights the Team and the "Set up a connector" button":::
38
38
39
39
1. Name the Webhook as appropriate and optionally upload an icon to identify your messages.
40
40
41
41
:::image type="content" source="media/how-to-send-notifications-to-teams/teams-add-icon.png" alt-text="Highlights the name property, optional image upload, and "Create" button in the Incoming Webhook options page.":::
42
42
43
-
1. Copy the Webhook URL that is generated on creation and save it for later use in pipeline. After that, click the "Done" button to complete the setup.
43
+
1. Copy the Webhook URL that is generated on creation and save it for later use in pipeline. After that, select the "Done" button to complete the setup.
44
44
45
45
:::image type="content" source="media/how-to-send-notifications-to-teams/teams-copy-webhook-url.png" alt-text="Shows the new webhook URL on the Incoming Webhook options page after creation.":::
46
46
@@ -183,7 +183,7 @@ Before you can send notifications to Teams from your pipelines, you must create
183
183
184
184
1. Search for "Web" in the pipeline "Activities" pane, and drag a **Web** activity to the pipeline canvas.
185
185
186
-
1. Create a dependency condition for the **Web** activity so that it only runs if the **Set Variable** activity succeeds. To create this dependency, click the green handle on the right side of the **Set Variable** activity, drag it, and connect it to the **Web** activity.
186
+
1. Create a dependency condition for the **Web** activity so that it only runs if the **Set Variable** activity succeeds. To create this dependency, select the green handle on the right side of the **Set Variable** activity, drag it, and connect it to the **Web** activity.
187
187
188
188
1. Select the new **Web** activity on the canvas if it isn't already selected, and its "General" tab, to edit its details.
189
189
@@ -341,7 +341,7 @@ Before you can send notifications to Teams from your pipelines, you must create
341
341
342
342
1. Search for "Web" in the pipeline "Activities" pane, and drag a **Web** activity to the pipeline canvas.
343
343
344
-
1. Create a dependency condition for the **Web** activity so that it only runs if the **Set Variable** activity succeeds. To create this dependency, click the green handle on the right side of the **Set Variable** activity, drag it, and connect it to the **Web** activity.
344
+
1. Create a dependency condition for the **Web** activity so that it only runs if the **Set Variable** activity succeeds. To create this dependency, select the green handle on the right side of the **Set Variable** activity, drag it, and connect it to the **Web** activity.
345
345
346
346
1. Select the new **Web** activity on the canvas if it isn't already selected, and its "General" tab, to edit its details.
347
347
@@ -401,7 +401,7 @@ In this sample usage scenario, we'll create a master pipeline with three **Execu
- Create a dependency condition for the second **Execute Pipeline** activity so that it only runs if the first **Execute Pipeline** activity succeeds. To create this dependency, click the green handle on the right side of the first **Execute Pipeline** activity, drag it, and connect it to the second **Execute Pipeline** activity.
404
+
- Create a dependency condition for the second **Execute Pipeline** activity so that it only runs if the first **Execute Pipeline** activity succeeds. To create this dependency, select the green handle on the right side of the first **Execute Pipeline** activity, drag it, and connect it to the second **Execute Pipeline** activity.
405
405
406
406
:::image type="content" source="media/how-to-send-notifications-to-teams/execute-pipeline-activity-2-general.png" alt-text="Shows the second "Execute pipeline" activity "OnSuccess Notification" general pane for "NotifiyTeamsChannelPipeline" pipeline.":::
407
407
@@ -419,12 +419,12 @@ In this sample usage scenario, we'll create a master pipeline with three **Execu
419
419
| name | ``@activity('LoadDataPipeline').output['pipelineName']`` |
- Create a dependency condition for the third **Execute Pipeline** activity so that it only runs if the first **Execute Pipeline** activity fails. To create this dependency, click the red handle on the right side of the first **Execute Pipeline** activity, drag it, and connect it to the third **Execute Pipeline** activity.
427
+
- Create a dependency condition for the third **Execute Pipeline** activity so that it only runs if the first **Execute Pipeline** activity fails. To create this dependency, select the red handle on the right side of the first **Execute Pipeline** activity, drag it, and connect it to the third **Execute Pipeline** activity.
428
428
429
429
- Validate, debug, and then publish your **MasterPipeline** pipeline.
430
430
@@ -438,7 +438,7 @@ In this sample usage scenario, we'll create a master pipeline with three **Execu
438
438
439
439
:::image type="content" source="media/how-to-send-notifications-to-teams/teams-notifications-view-pipeline-run-onfailure.png" alt-text="Shows on failure pipeline notifications in a Teams channel.":::
440
440
441
-
1. Click the "View pipeline run" button to view pipeline run.
441
+
1. Select the "View pipeline run" button to view pipeline run.
442
442
443
443
## Add dynamic messages with system variables and expressions
444
444
@@ -449,7 +449,7 @@ make your messages dynamic. For example:
449
449
450
450
- ``@activity("DataFlow").error.Message``
451
451
452
-
The above expressions will return the relevant error messages from a failure, which can be sent out as notification on a Teams channel. For more information, see the
452
+
The above expressions will return the relevant error messages from a failure, which can be sent out as notification on a Teams channel. For more information about this topic, see the
453
453
[Copy activity output properties](copy-activity-monitoring.md) article for more details.
454
454
455
455
We also encourage you to review the Microsoft Teams supported [notification payload schema](https://adaptivecards.io/explorer/AdaptiveCard.html) and
0 commit comments