Skip to content

Commit 4fa07a4

Browse files
Update how-to-send-notifications-to-teams.md
Update article and used "Select" instead of "Click" to align with the writing style.
1 parent fc23203 commit 4fa07a4

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/data-factory/how-to-send-notifications-to-teams.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -24,23 +24,23 @@ Before you can send notifications to Teams from your pipelines, you must create
2424

2525
:::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.":::
2626

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.
2828

2929
:::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.":::
3030

3131
1. Type or select Team or Team channel name where you want to send the notifications.
3232

3333
:::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"":::
3434

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.
3636

3737
:::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":::
3838

3939
1. Name the Webhook as appropriate and optionally upload an icon to identify your messages.
4040

4141
:::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.":::  
4242

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.
4444

4545
:::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.":::
4646

@@ -183,7 +183,7 @@ Before you can send notifications to Teams from your pipelines, you must create
183183

184184
1. Search for "Web" in the pipeline "Activities" pane, and drag a **Web** activity to the pipeline canvas.
185185

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.
187187

188188
1. Select the new **Web** activity on the canvas if it isn't already selected, and its "General" tab, to edit its details.
189189

@@ -341,7 +341,7 @@ Before you can send notifications to Teams from your pipelines, you must create
341341

342342
1. Search for "Web" in the pipeline "Activities" pane, and drag a **Web** activity to the pipeline canvas.
343343

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.
345345

346346
1. Select the new **Web** activity on the canvas if it isn't already selected, and its "General" tab, to edit its details.
347347

@@ -401,7 +401,7 @@ In this sample usage scenario, we'll create a master pipeline with three **Execu
401401
| runDuration | ``@activity('LoadDataPipeline').Duration`` |
402402
| teamWebhookUrl | ``https://microsoft.webhook.office.com/webhookb2/1234abcd-1x11-2ff1-ab2c-1234d0699a9e@72f988bf-32b1-41af-91ab-2d7cd011db47/IncomingWebhook/8212f66ad80040ab83cf68b554d9232a/17d524d0-ed5c-44ed-98a0-35c12dd89a6d`` |
403403

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, 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.
405405

406406
:::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.":::
407407

@@ -419,12 +419,12 @@ In this sample usage scenario, we'll create a master pipeline with three **Execu
419419
| name | ``@activity('LoadDataPipeline').output['pipelineName']`` |
420420
| triggerTime | ``@activity('LoadDataPipeline').ExecutionStartTime`` |
421421
| status | ``@activity('LoadDataPipeline').Status`` |
422-
| message | ``@activity('LoadDataPipeline').Error['message']`` |
422+
| message | ``@activity('LoadDataPipeline').Error['message']`` |
423423
| executionEndTime | ``@activity('LoadDataPipeline').ExecutionEndTime`` |
424424
| runDuration | ``@activity('LoadDataPipeline').Duration`` |
425425
| teamWebhookUrl | ``https://microsoft.webhook.office.com/webhookb2/1234abcd-1x11-2ff1-ab2c-1234d0699a9e@72f988bf-32b1-41af-91ab-2d7cd011db47/IncomingWebhook/8212f66ad80040ab83cf68b554d9232a/17d524d0-ed5c-44ed-98a0-35c12dd89a6d`` |
426426

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, 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.
428428

429429
- Validate, debug, and then publish your **MasterPipeline** pipeline.
430430

@@ -438,7 +438,7 @@ In this sample usage scenario, we'll create a master pipeline with three **Execu
438438

439439
:::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.":::
440440

441-
1. Click the "View pipeline run" button to view pipeline run.
441+
1. Select the "View pipeline run" button to view pipeline run.
442442

443443
## Add dynamic messages with system variables and expressions
444444

@@ -449,7 +449,7 @@ make your messages dynamic. For example:  
449449

450450
- ``@activity("DataFlow").error.Message``
451451

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
453453
[Copy activity output properties](copy-activity-monitoring.md) article for more details.
454454

455455
We also encourage you to review the Microsoft Teams supported [notification payload schema](https://adaptivecards.io/explorer/AdaptiveCard.html) and

0 commit comments

Comments
 (0)