Skip to content

Commit c4ef1ed

Browse files
authored
Merge pull request #2540 from laujan/361124-translator-january-freshness
361124 translator january freshness
2 parents 9879435 + 4b19d6d commit c4ef1ed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

59 files changed

+505
-545
lines changed

articles/ai-services/translator/connector/document-translation-flow.md

Lines changed: 24 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
---
2-
title: "Use Translator V3 connector to build a Document Translation flow"
2+
title: "Use Microsoft Azure V3 connector to build a Document Translation flow"
33
titleSuffix: Azure AI services
4-
description: Use Microsoft Translator V3 connector and Power Automate to create a Document Translation flow.
4+
description: Use Microsoft Azure Translator V3 connector and Power Automate to create a Document Translation flow.
55
author: laujan
66
manager: nitinme
77
ms.service: azure-ai-translator
8-
ms.custom: build-2023, build-2023-dataai
98
ms.topic: tutorial
10-
ms.date: 07/09/2024
9+
ms.date: 01/27/2025
1110
ms.author: lajanuar
1211
---
1312

@@ -17,13 +16,13 @@ ms.author: lajanuar
1716
<!-- markdownlint-disable MD036 -->
1817
<!-- markdownlint-disable MD001 -->
1918

20-
# Create a Document Translation flow (preview)
19+
# Create an Azure AI Translator Document Translation flow (preview)
2120

2221
> [!IMPORTANT]
2322
>
24-
> The Translator connector is currently available in public preview. Features, approaches and processes may change, prior to General Availability (GA), based on user feedback.
23+
> The Microsoft Azure Translator connector is currently available in public preview. Features, approaches, and processes may change, before General Availability (GA) release, based on user feedback.
2524
26-
This tutorial guides you through configuring a Microsoft Translator V3 connector cloud flow that supports document translation. The Translator V3 connector creates a connection between your Translator Service instance and Microsoft Power Automate enabling you to use one or more prebuilt operations as steps in your apps and workflows.
25+
This tutorial guides you through configuring a Microsoft Azure Translator V3 connector cloud flow that supports document translation. The Translator V3 connector creates a connection between your Translator Service instance and Microsoft Power Automate enabling you to use one or more prebuilt operations as steps in your apps and workflows.
2726

2827
Document Translation is a cloud-based REST API feature of the Azure AI Translator service. The Document Translation API enables multiple and complex document translations while preserving original document structure and data format.
2928

@@ -75,7 +74,7 @@ Here's what you need to get started: [**Translator resource**](#translator-resou
7574
1. Deselect all check boxes.
7675
1. Make sure **Microsoft network routing** is selected.
7776
1. Under the **Resource instances** section, select **Microsoft.CognitiveServices/accounts** as the resource type and select your Translator resource as the instance name.
78-
1. Make certain that the **Allow Azure services on the trusted services list to access this storage account** box is checked. For more information about managing exceptions, *see* [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security).
77+
1. Make certain that the **`Allow Azure services on the trusted services list to access this storage account`** box is checked. For more information about managing exceptions, *see* [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security).
7978

8079
:::image type="content" source="../media/managed-identities/allow-trusted-services-checkbox-portal-view.png" alt-text="Screenshot: allow trusted services checkbox, portal view.":::
8180

@@ -114,7 +113,7 @@ Next, assign a **`Storage Blob Data Contributor`** role to the managed identity
114113

115114
:::image type="content" source="../media/managed-identities/azure-role-assignments-page-portal.png" alt-text="Screenshot: Azure role assignments page in the Azure portal.":::
116115

117-
1. Finally, assign a **Storage Blob Data Contributor** role to your Translator service resource. The **Storage Blob Data Contributor** role gives Translator (represented by the system-assigned managed identity) read, write, and delete access to the blob container and data. In the **Add role assignment** pop-up window, complete the fields as follows and select **Save**:
116+
1. Finally, assign a **Storage Blob Data Contributor** role to your Translator service resource. The **Storage Blob Data Contributor** role gives Translator (represented by the system-assigned managed identity) read, write, and delete access to the blob container and data. In the **`Add role assignment`** pop-up window, complete the fields as follows and select **Save**:
118117

119118
| Field | Value|
120119
|------|--------|
@@ -168,7 +167,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
168167
> * Translate your document(s) choosing source and target languages.
169168
> * Get the status of the translation operation.
170169
171-
1. In the **Choose an operation** pop-up window, enter Translator V3 in the **Search connectors and actions** search bar and select the **Microsoft Translator V3** icon.
170+
1. In the **Choose an operation** pop-up window, enter Translator V3 in the **Search connectors and actions** search bar and select the **Microsoft Azure Translator V3** icon.
172171

173172
:::image type="content" source="../media/connectors/choose-operation.png" alt-text="Screenshot showing the selection of Translator V3 as the next flow step.":::
174173

@@ -184,7 +183,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
184183
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the how-to-add connection window.":::
185184

186185
> [!NOTE]
187-
> After you've set up your connection, you won't be required to reenter your credentials for subsequent flows.
186+
> After you set up your connection, you won't be required to reenter your credentials for subsequent flows.
188187
189188
1. The **Start document translation** action window now appears. Complete the fields as follows:
190189

@@ -202,7 +201,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
202201
|Select the checkbox next to the source container|Select the checkbox next to the target container.|
203202
| From the main window area, select a file or document for translation.| Select the ellipses located at the right, then choose **Properties**.|
204203
| The source URL is located at the top of the Properties list. Select the **Copy to Clipboard** icon.|The target URL is located at the top of the Properties list. Select the **Copy to Clipboard** icon.|
205-
| Navigate to your Power automate flow and paste the source URL in the **Location of the source documents** field.|Navigate to your Power automate flow and paste the target URL in the **Location of the translated documents** field.|
204+
| Navigate to your Power Automate flow and paste the source URL in the **Location of the source documents** field.|Navigate to your Power Automate flow and paste the target URL in the **Location of the translated documents** field.|
206205
* Choose a **Target Language** from the dropdown menu and select **Save**.
207206

208207
:::image type="content" source="../media/connectors/start-document-translation-window.png" alt-text="Screenshot of the Start document translation dialog window.":::
@@ -213,7 +212,7 @@ Now that you submitted your documents for translation, let's check the status of
213212

214213
1. Select **New step**.
215214

216-
1. Enter Translator V3 in the search box and choose **Microsoft Translator V3**.
215+
1. Enter Translator V3 in the search box and choose **Microsoft Azure Translator V3**.
217216

218217
1. Select **Get documents status** (not the singular Get *document* status action).
219218

@@ -290,7 +289,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
290289

291290
1. Select **New step** and enter **Azure Blob Storage** in the search box.
292291

293-
1. Select the **Create blob (V2)** action.
292+
1. Select the **`Create blob (V2)`** action.
294293

295294
1. If you're using the Azure storage step for the first time, you need to enter your storage resource authentication:
296295

@@ -313,7 +312,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
313312

314313
1. Select **New step**.
315314

316-
1. Enter Translator V3 in the search box and choose **Microsoft Translator V3**.
315+
1. Enter Translator V3 in the search box and choose **Microsoft Azure Translator V3**.
317316

318317
1. Select the **Start document translation** action.
319318

@@ -327,7 +326,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
327326
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the how-to-add connection window.":::
328327

329328
> [!NOTE]
330-
> After you've setup your connection, you won't be required to reenter your credentials for subsequent Translator flows.
329+
> After setting up your connection, you won't be required to reenter your credentials for subsequent Translator flows.
331330
332331
1. The **Start document translation** action window now appears. Complete the fields as follows:
333332

@@ -343,7 +342,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
343342
* Select the checkbox next to the target container.
344343
* Select the ellipses located at the right, then choose **Properties**.
345344
* The target URL is located at the top of the Properties list. Select the **Copy to Clipboard** icon.
346-
* Navigate back to your Power automate flow and paste the target URL in the **Location of the translated documents** field.
345+
* Navigate back to your Power Automate flow and paste the target URL in the **Location of the translated documents** field.
347346

348347
1. Choose a **Target Language** from the dropdown menu and select **Save**.
349348

@@ -359,7 +358,7 @@ Before retrieving the documents status, let's schedule a 30-second delay to ensu
359358

360359
:::image type="content" source="../media/connectors/delay-step.png" alt-text="Screenshot showing the delay step.":::
361360

362-
1. Select **New step**. Enter Translator V3 in the search box and choose **Microsoft Translator V3**.
361+
1. Select **New step**. Enter Translator V3 in the search box and choose **Microsoft Azure Translator V3**.
363362

364363
1. Select **Get documents status** (not the singular Get *document* status).
365364

@@ -402,7 +401,7 @@ In this step, you retrieve the translated document from Azure Blob Storage and u
402401

403402
:::image type="content" source="../media/connectors/do-until-progress.png" alt-text="Screenshot showing the Do until control action.":::
404403

405-
1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **Get blob content using path (V2)** action.
404+
1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **`Get blob content using path (V2)`** action.
406405
1. In the **Storage account name or blob endpoint** field, select **Enter custom value** and enter your storage account name.
407406
1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression**, and enter the following logic in the formula field:
408407

@@ -412,12 +411,12 @@ In this step, you retrieve the translated document from Azure Blob Storage and u
412411
413412
```
414413

415-
1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **Get Blob Metadata using path (V2)** action.
414+
1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **`Get Blob Metadata using path (V2)`** action.
416415
1. In the **Storage account name or blob endpoint** field, select **Enter custom value** and enter your storage account name.
417416

418417
:::image type="content" source="../media/connectors/enter-custom-value.png" alt-text="Screenshot showing 'enter custom value' from the create-blob-(V2) window.":::
419418

420-
1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression** and enter the following logic in the formula field:
419+
1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression**, and then enter the following logic in the formula field:
421420

422421
```powerappsfl
423422
@@ -452,16 +451,16 @@ Let's check your document translation flow and results.
452451

453452
:::image type="content" source="../media/connectors/test-flow.png" alt-text="Screenshot showing the test icon/button.":::
454453

455-
1. Select **Test Flow****Manually****Test** from the right-side window.
456-
1. In the **Run flow** window, select the **Continue** then the **Run flow** buttons.
457-
1. Finally, select the **Done** button.
454+
1. Select **`Test Flow`****Manually****Test** from the right-side window.
455+
1. In the **`Run flow`** window, select the **Continue** then the **`Run flow`** buttons.
456+
1. Finally, select the **`Done`** button.
458457
1. You should receive a "Your flow ran successfully" message and green check marks align with each successful step.
459458

460459
:::image type="content" source="../media/connectors/successful-sharepoint-flow.png" alt-text="Screenshot showing a successful flow using SharePoint and Azure Blob Storage.":::
461460

462461
---
463462

464-
That's it! You learned to automate document translation processes using the Microsoft Translator V3 connector and Power Automate.
463+
That's it! You learned to automate document translation processes using the Microsoft Azure Translator V3 connector and Power Automate.
465464

466465
## Next steps
467466

articles/ai-services/translator/connector/text-translator-flow.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: nitinme
77
ms.service: azure-ai-translator
88
ms.custom: build-2023
99
ms.topic: how-to
10-
ms.date: 07/10/2024
10+
ms.date: 01/28/2025
1111
ms.author: lajanuar
1212
---
1313

@@ -21,7 +21,7 @@ ms.author: lajanuar
2121

2222
> [!IMPORTANT]
2323
>
24-
> * The Translator connector is currently available in public preview. Features, approaches and processes may change, prior to General Availability (GA), based on user feedback.
24+
> * The Translator connector is currently available in public preview. Features, approaches, and processes can change, before General Availability (GA) release, based on user feedback.
2525
2626
This article guides you through configuring a Microsoft Translator V3 connector cloud flow that supports text translation and transliteration. The Translator V3 connector creates a connection between your Translator Service instance and Microsoft Power Automate enabling you to use one or more prebuilt operations as steps in your apps and workflows.
2727

@@ -79,7 +79,7 @@ Let's select an action. Choose to translate or transliterate text.
7979
:::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add-connection window.":::
8080

8181
> [!NOTE]
82-
> After you've setup your connection, you won't be required to reenter your credentials for subsequent Translator flows.
82+
> After setting up your connection, you won't be required to reenter your credentials for subsequent Translator flows.
8383
8484
1. The **Translate text** action window appears next.
8585
1. Select a **Source Language** from the dropdown menu or keep the default **Auto-detect** option.

articles/ai-services/translator/containers/configuration.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
11
---
2-
title: Configure containers - Translator
2+
title: Configure containers - Azure AI Translator
33
titleSuffix: Azure AI services
4-
description: The Translator container runtime environment is configured using the `docker run` command arguments. There are both required and optional settings.
4+
description: The Azure AI Translator container runtime environment is configured using the `docker run` command arguments. There are both required and optional settings.
55
#services: cognitive-services
66
author: laujan
77
manager: nitinme
88
ms.service: azure-ai-translator
99
ms.topic: how-to
10-
ms.date: 04/08/2024
10+
ms.date: 01/28/2025
1111
ms.author: lajanuar
1212
recommendations: false
1313
---
1414

15-
# Configure Translator Docker containers
15+
# Configure Azure AI Translator Docker containers
1616

1717
Azure AI services provide each container with a common configuration framework. You can easily configure your Translator containers to build Translator application architecture optimized for robust cloud capabilities and edge locality.
1818

19-
The **Translator** container runtime environment is configured using the `docker run` command arguments. This container has both required and optional settings. The required container-specific settings are the billing settings.
19+
The **Azure AI Translator** container runtime environment is configured using the `docker run` command arguments. This container has both required and optional settings. The required container-specific settings are the billing settings.
2020

2121
## Configuration settings
2222

@@ -34,7 +34,7 @@ The container has the following configuration settings:
3434
|Yes|[Mounts](#mount-settings)|Reads and writes data from the host computer to the container and from the container back to the host computer.|
3535

3636
> [!IMPORTANT]
37-
> The [**ApiKey**](#apikey-configuration-setting), [**Billing**](#billing-configuration-setting), and [**EULA**](#eula-setting) settings are used together, and you must provide valid values for all three of them; otherwise your container won't start. For more information about using these configuration settings to instantiate a container.
37+
> The [**ApiKey**](#apikey-configuration-setting), [**Billing**](#billing-configuration-setting), and [**EULA**](#eula-setting) settings are used together, and you must provide valid values for all three of them; otherwise your container can't start. For more information about using these configuration settings to instantiate a container, *see* [Install and run Azure AI Translator container](install-run.md).
3838
3939
## ApiKey configuration setting
4040

0 commit comments

Comments
 (0)