Skip to content

Commit a4da25d

Browse files
committed
note and edits
1 parent 1182b20 commit a4da25d

File tree

9 files changed

+39
-52
lines changed

9 files changed

+39
-52
lines changed

articles/cognitive-services/language-service/conversational-language-understanding/how-to/call-api.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,6 @@ You can query the deployment programmatically through the [prediction API](https
2020

2121
## Test deployed model
2222

23-
> [!Note]
24-
> You can use your custom model in an [power automate flow](../../tutorials/power-automate.md)
25-
2623
You can use Language Studio to submit an utterance, get predictions and visualize the results.
2724

2825
[!INCLUDE [Test model](../includes/language-studio/test-model.md)]

articles/cognitive-services/language-service/custom-named-entity-recognition/how-to/call-api.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,6 @@ You can query the deployment programmatically using the [Prediction API](https:/
2121

2222
## Test deployed model
2323

24-
> [!Note]
25-
> You can use your custom model in an [power automate flow](../../tutorials/power-automate.md)
26-
2724
You can use Language Studio to submit the custom entity recognition task and visualize the results.
2825

2926
[!INCLUDE [Test model](../includes/language-studio/test-model.md)]

articles/cognitive-services/language-service/custom-text-classification/how-to/call-api.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,6 @@ You can query the deployment programmatically [Prediction API](https://aka.ms/ct
2121

2222
## Test deployed model
2323

24-
> [!Note]
25-
> You can use your custom model in an [power automate flow](../../tutorials/power-automate.md)
26-
2724
You can use Language Studio to submit the custom text classification task and visualize the results.
2825

2926
[!INCLUDE [Test model](../includes/language-studio/test-model.md)]
Lines changed: 36 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,62 +1,70 @@
11
---
2-
title: Traige incoming emails with power automate
2+
title: Triage incoming emails with Power Automate
33
titleSuffix: Azure Cognitive Services
4-
description: Traige incoming emails with power automate
4+
description: Learn how to use custom text classification to categorize and triage incoming emails with Power Automate
55
services: cognitive-services
66
author: aahill
77
manager: nitinme
88
ms.service: cognitive-services
99
ms.subservice: language-service
1010
ms.topic: tutorial
11-
ms.date: 06/03/2022
11+
ms.date: 01/27/2023
1212
ms.author: aahi
13-
ms.custom:
1413
---
1514

16-
# Tutorial: Traige incoming emails with power automate
15+
# Tutorial: Triage incoming emails with power automate
1716

18-
In this tutorial we will triage incoming email using custom single text classification project type. When a new email is received, the content of the body gets classified and depending on the classificaiton result, a message is sent to the specialized team on Microsoft Teams.
17+
In this tutorial you will categorize and triage incoming email using custom text classification. Using this [Power Automate](https://learn.microsoft.com/power-automate/getting-started) flow, when a new email is received, its contents will have a classification applied, and depending on the result, a message will be sent to a designated channel on [Microsoft Teams](https://www.microsoft.com/microsoft-teams).
1918

2019

2120
## Prerequisites
22-
* Azure subscription, <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics" title="Create a Language resource" target="_blank">create a Language resource </a> in the Azure portal to get your key and endpoint. After it deploys, click **Go to resource**.
23-
* You will need the key and endpoint from the resource you created in your power automate flow.
24-
* Successfully created and deployed a [single text classification custom model](../quickstart.md).
2521

22+
* Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services)
23+
* <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics" title="Create a Language resource" target="_blank">A Language resource </a>
24+
* (optional) A trained model if you're using a custom capability such as [custom NER](../custom-named-entity-recognition/overview.md), [custom text classification](../custom-text-classification/overview.md), or [conversational language understanding](../conversational-language-understanding/overview.md).
25+
* You will need the key and endpoint from your Language resource to authenticate your Power Automate flow.
26+
* A successfully created and deployed [single text classification custom model](../quickstart.md)
2627

27-
## Create a power automate flow
2828

29-
1- [Signin to power automate](https://make.powerautomate.com/)
29+
## Create a Power Automate flow
3030

31-
2- From the left side menu, choose *My flows* and create a *Automated cloud flow*
32-
:::image type="content" source="../media/create-flow.png" alt-text="A screenshot of the flow creation." lightbox="../media/create-flow.png":::
31+
1. [Sign in to power automate](https://make.powerautomate.com/)
3332

34-
3- Name your flow as *EmailTriage*, from triggers search for *email* and choose *When a new email arrives* option then click *create*
35-
:::image type="content" source="../media/email-flow.png" alt-text="A screenshot of the language flow." lightbox="../media/email-flow.png":::
33+
2. From the left side menu, select **My flows** and create a **Automated cloud flow**
3634

37-
4- Start by adding the right connection to your email. This connection will be used to access the email content.
35+
:::image type="content" source="../media/create-flow.png" alt-text="A screenshot of the flow creation screen." lightbox="../media/create-flow.png":::
3836

39-
5- To add a Language connector, search for *Azure Language*
40-
:::image type="content" source="../media/language-connector.png" alt-text="A screenshot of azure language connectors." lightbox="../media/language-connector.png":::
37+
3. Name your flow `EmailTriage`. Below **Choose your flow's triggers**, search for *email* and select **When a new email arrives**. Then click **create**
4138

42-
6- Search for *CustomSingleLabelClassification*
43-
:::image type="content" source="../media/single-classification.png" alt-text="A screenshot of Classification connector." lightbox="../media/single-classification.png":::
39+
:::image type="content" source="../media/email-flow.png" alt-text="A screenshot of the email flow triggers." lightbox="../media/email-flow.png":::
4440

45-
7- Start by adding the right connection to your connector. This connection will be used to access the classification project.
41+
4. Add the right connection to your email account. This connection will be used to access the email content.
4642

47-
8- In documents id field, add **1**.
43+
5. To add a Language service connector, search for *Azure Language*.
44+
45+
:::image type="content" source="../media/language-connector.png" alt-text="A screenshot of available Azure Language service connectors." lightbox="../media/language-connector.png":::
4846

49-
9- In documents text field add *body* from dynamic content.
47+
6. Search for *CustomSingleLabelClassification*.
5048

51-
10- Fill in the project name and deployment name of your deployed model
49+
:::image type="content" source="../media/single-classification.png" alt-text="A screenshot of Classification connector." lightbox="../media/single-classification.png":::
5250

53-
:::image type="content" source="../media/classification.png" alt-text="A screenshot project details." lightbox="../media/classification.png":::
51+
7. Start by adding the right connection to your connector. This connection will be used to access the classification project.
5452

55-
11- Add condition to send a Microsoft Teams message to the righ team. Choose *results* from dynamic content and add the condition. For this tutorial, we are looking for *Computer_science* related emails. In the *Yes* condition, choose your desired option to notify the team. In the *No* condition, you can add further condition to check other cases and do alternative actions.
53+
8. In the documents ID field, add **1**.
5654

57-
:::image type="content" source="../media/email-triage.png" alt-text="A screenshot of email flow." lightbox="../media/email-triage.png":::
55+
9. In the documents text field, add **body** from **dynamic content**.
56+
57+
10. Fill in the project name and deployment name of your deployed custom text classification model.
58+
59+
:::image type="content" source="../media/classification.png" alt-text="A screenshot project details." lightbox="../media/classification.png":::
60+
61+
11. Add a condition to send a Microsoft Teams message to the right team by:
62+
1. Select **results** from **dynamic content**, and add the condition. For this tutorial, we are looking for `Computer_science` related emails. In the **Yes** condition, choose your desired option to notify a team channel. In the **No** condition, you can add additional conditions to perform alternative actions.
63+
64+
:::image type="content" source="../media/email-triage.png" alt-text="A screenshot of email flow." lightbox="../media/email-triage.png":::
5865

5966

6067
## Next steps
6168

62-
[Language studio overview](../../language-studio.md)
69+
* [Use the Language service with Power Automate](../../tutorials/power-automate.md)
70+
* [Available Language service connectors](/connectors/cognitiveservicestextanalytics)

articles/cognitive-services/language-service/entity-linking/how-to/call-api.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,6 @@ The entity linking feature can be used to identify and disambiguate the identity
2222

2323
[!INCLUDE [development-options](../includes/development-options.md)]
2424

25-
> [!Note]
26-
> You can use this feature in an [power automate flow](../../tutorials/power-automate.md)
27-
2825
## Determine how to process the data (optional)
2926

3027
### Specify the entity linking model

articles/cognitive-services/language-service/language-detection/how-to/call-api.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,6 @@ The Language Detection feature can detect a wide range of languages, variants, d
2525

2626
[!INCLUDE [development options](../includes/development-options.md)]
2727

28-
> [!Note]
29-
> You can use this feature in an [power automate flow](../../tutorials/power-automate.md)
30-
3128
## Determine how to process the data (optional)
3229

3330
### Specify the language detection model

articles/cognitive-services/language-service/summarization/how-to/conversation-summarization.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,6 @@ When you submit data to conversation summarization, we recommend sending one cha
5050

5151
You can use conversation issue and resolution summarization to get summaries as you need. To see an example using text chats, see the [quickstart article](../quickstart.md).
5252

53-
> [!Note]
54-
> You can use this feature in an [power automate flow](../../tutorials/power-automate.md)
55-
5653
### Get summaries from speech transcriptions
5754

5855
Conversation issue and resolution summarization also enables you to get summaries from speech transcripts by using the [Speech service's speech-to-text feature](../../../Speech-Service/call-center-overview.md). The following example shows a short conversation that you might include in your API requests.

articles/cognitive-services/language-service/text-analytics-for-health/how-to/call-api.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,9 +86,6 @@ To receive your result using the **FHIR** structure, you must send the FHIR vers
8686

8787
## Getting results from the feature
8888

89-
> [!Note]
90-
> You can use this feature in an [power automate flow](../../tutorials/power-automate.md)
91-
9289
Depending on your API request, and the data you submit to the Text Analytics for health, you will get:
9390

9491
[!INCLUDE [Text Analytics for health features](../includes/features.md)]

articles/cognitive-services/language-service/tutorials/power-automate.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You can use [Power Automate](/power-automate/getting-started) flows to automate
2626
## Prerequisites
2727
* Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services)
2828
* <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics" title="Create a Language resource" target="_blank">A Language resource </a>
29-
* (optional) A trained model if you're using a custom capability such as [custom NER](../custom-named-entity-recognition/overview.md), [custom text classification](../custom-text-classification/), or [conversational language understanding](../conversational-language-understanding/overview.md).
29+
* (optional) A trained model if you're using a custom capability such as [custom NER](../custom-named-entity-recognition/overview.md), [custom text classification](../custom-text-classification/overview.md), or [conversational language understanding](../conversational-language-understanding/overview.md).
3030
* You will need the key and endpoint from your Language resource to authenticate your Power Automate flow.
3131

3232
## Create a Power Automate flow
@@ -55,11 +55,11 @@ You can use [Power Automate](/power-automate/getting-started) flows to automate
5555

5656
7. Add endpoint and key for your Language resource, which will be used for authentication. You can find your key and endpoint by navigating to your resource in the [Azure portal](https://portal.azure.com), and selecting **Keys and endpoint** from the left navigation menu.
5757

58-
:::image type="content" source="../media/azure-portal-resource-credentials.png" alt-text="A screenshot of language key and endpoint." lightbox="../media/azure-portal-resource-credentials.png":::
58+
:::image type="content" source="../media/azure-portal-resource-credentials.png" alt-text="A screenshot of A language resource key and endpoint in the Azure portal." lightbox="../media/azure-portal-resource-credentials.png":::
5959

6060
8. Once you have your key and endpoint, add it to the connector in Power Automate.
6161

62-
:::image type="content" source="../media/language-auth.png" alt-text="A screenshot of language key and endpoint." lightbox="../media/language-auth.png":::
62+
:::image type="content" source="../media/language-auth.png" alt-text="A screenshot of adding the language key and endpoint to the Power Automate flow." lightbox="../media/language-auth.png":::
6363

6464
9. Add the data in the connector
6565
:::image type="content" source="../media/ner-connector.png" alt-text="A screenshot of the NER connector." lightbox="../media/ner-connector.png":::

0 commit comments

Comments
 (0)