Skip to content

Commit c28edea

Browse files
author
ecfan
committed
Draft
1 parent 9aa9b16 commit c28edea

File tree

1 file changed

+18
-20
lines changed

1 file changed

+18
-20
lines changed

articles/logic-apps/ai-resources.md

Lines changed: 18 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -13,37 +13,35 @@ ms.date: 11/11/2024
1313

1414
[!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
1515

16-
This guide provides examples, samples, and other resources that can help learn how to integrate Azure AI services, such as Azure OpenAI and Azure AI Search, with Standard workflows in Azure Logic Apps.
16+
This guide provides examples, samples, and other resources to help you learn how you can integrate Azure AI services, such as Azure OpenAI and Azure AI Search, with Standard workflows in Azure Logic Apps.
1717

18-
## Documentation
18+
## AI-related operations documentation
1919

20-
- [Parse or chunk content for Standard workflows in Azure Logic Apps](/azure/logic-apps/parse-document-chunk-text)
20+
The following sections describe built-in operations and documentation that you can use to build Standard workflows for AI integration scenarios, such as document ingestion and making it possible for customers to "chat with the data".
2121

22-
This guide shows how to convert content into tokens and split up content for easier consumption by Azure AI connectors, such as the **Azure AI Search** and **Azure OpenAI**.
22+
### Parse a document and chunk text operations
2323

24-
In addition, the **Parse a document** and **Chunk text** operations help you prepare content for building document ingestion workflows so that you can make it possible for customers to "chat with the data".
25-
in a handful of steps without a single line of code
24+
The **Parse a document** and **Chunk text** built-in or "in-app" actions help you prepare content for Azure AI services to consume in your workflows. Connectors for Azure AI services such as **Azure OpenAI** and **Azure AI Search** usually expect tokenized input and can handle only a limited number of tokens.
2625

27-
Without any custom logic or configuration, the **Parse a document** operation enables your workflow to read and parse thousands of documents in multiple languages and with file types such as PDF, DOCX, PPT, HTML, and more.
26+
| Action | Description |
27+
|--------|-------------|
28+
| **Parse a document** | This action converts content into tokenized string output so that a workflow can read and parse thousands of documents with file types such as PDF, DOCX, CSV, PPT, HTML, and others in multiple languages. |
29+
| **Chunk text** | This action splits a tokenized string into pieces for subsequent actions in the same workflow to easily consume. |
2830

29-
This no-code approach enables you to automate complex workflowswhether it’s document parsing, data chunking, or powering generative AI models—helping you unlock the full potential of your data with minimal effort.
31+
Both these actions don't require any custom logic or configuration to use. This no-code approach helps you automate complex workflows whether the task is document parsing, data chunking, or powering generative AI models, which helps you unlock your data's full potential with minimal effort.
3032

31-
33+
For a guide that shows how to use these actions in your Standard workflow, see [Parse or chunk content for Standard workflows in Azure Logic Apps](/azure/logic-apps/parse-document-chunk-text).
3234

33-
by using the actions named [**Parse a document**] and [**Chunk text**](/azure/logic-apps/parse-document-chunk-text)
35+
### Azure OpenAI and Azure AI Search operations
3436

35-
the Azure AI Search or Azure OpenAI actions expect tokenized input and can handle only a limited number of tokens.
37+
The **Azure AI Search** and **Azure OpenAI** built-in or "in-app" connectors provide operations that help you integrate the natural language processing capabilities in Azure Open AI with the intelligent search capabilities in Azure AI Search. These connectors simplify backend processes with codeless setup and reduce complexity around integrating AI capabilities into your workflows.
3638

37-
For these scenarios, use the Data Operations actions named Parse a document and Chunk text in your Standard logic app workflow. These actions respectively transform content, such as a PDF document, CSV file, Excel file, and so on, into tokenized string output and then split the string into pieces, based on the number of tokens. You can then reference and use these outputs with subsequent actions in your workflow.
39+
| Connector | Description |
40+
|-----------|-------------|
41+
| **Azure OpenAI** | This connector provides operations with AI capabilities such as generate embeddings and chat completion, which are critical for creating sophisticated AI applications. |
42+
| **Azure AI Search** | This connector provides operations that enhance data retrieval with indexing, advanced vector, and hybrid search operations. |
3843

39-
For more information about the **Parse a document** and **Chunk text** operations, see [Blog articles](#blog-articles).
40-
41-
- [Connect to Azure AI services from Standard workflows in Azure Logic Apps](/azure/logic-apps/connectors/azure-ai)
42-
43-
This guide shows how to access Azure AI services, such as **Azure AI Search** and **Azure OpenAI**, from your Standard workflow and examples for how to use these connector operations.
44-
45-
46-
<a name="blog-articles"></a>
44+
For a guide that shows how to use these connector operations in your Standard workflow, see [Connect to Azure AI services from Standard workflows in Azure Logic Apps](/azure/logic-apps/connectors/azure-ai).
4745

4846
## Azure OpenAI Assistants
4947

0 commit comments

Comments
 (0)