freshness

laujan · laujan · commit fc8327325d5a · 2025-01-28T11:45:03.000-08:00
diff --git a/articles/ai-services/translator/connector/document-translation-flow.md b/articles/ai-services/translator/connector/document-translation-flow.md
@@ -16,11 +16,11 @@ ms.author: lajanuar
 <!-- markdownlint-disable MD036 -->
 <!-- markdownlint-disable MD001 -->
 
-# Create a Azure AI Translator Document Translation flow (preview)
+# Create an Azure AI Translator Document Translation flow (preview)
 
 > [!IMPORTANT]
 >
-> The Microsoft Azure Translator connector is currently available in public preview. Features, approaches and processes may change, prior to General Availability (GA), based on user feedback.
+> 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.
 
 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.
 
@@ -74,7 +74,7 @@ Here's what you need to get started: [**Translator resource**](#translator-resou
    1. Deselect all check boxes.
    1. Make sure **Microsoft network routing** is selected.
    1. Under the **Resource instances** section, select **Microsoft.CognitiveServices/accounts** as the resource type and select your Translator resource as the instance name.
-   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).
+   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).
 
       :::image type="content" source="../media/managed-identities/allow-trusted-services-checkbox-portal-view.png" alt-text="Screenshot: allow trusted services checkbox, portal view.":::
 
@@ -113,7 +113,7 @@ Next, assign a **`Storage Blob Data Contributor`** role to the managed identity
 
     :::image type="content" source="../media/managed-identities/azure-role-assignments-page-portal.png" alt-text="Screenshot: Azure role assignments page in the Azure portal.":::
 
-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**:
+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**:
 
     | Field | Value|
     |------|--------|
@@ -183,7 +183,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
       :::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the  how-to-add connection window.":::
 
       > [!NOTE]
-      > After you've set up your connection, you won't be required to reenter your credentials for subsequent flows.
+      > After you set up your connection, you won't be required to reenter your credentials for subsequent flows.
 
 1. The **Start document translation** action window now appears. Complete the fields as follows:
 
@@ -201,7 +201,7 @@ Here are the steps to translate a file in Azure Blob Storage using the Translato
          |Select the checkbox next to the source container|Select the checkbox next to the target container.|
          | From the main window area, select a file or document for translation.| Select the ellipses located at the right, then choose **Properties**.|
          | 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.|
-         | 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.|
+         | 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.|
    * Choose a **Target Language** from the dropdown menu and select **Save**.
 
       :::image type="content" source="../media/connectors/start-document-translation-window.png" alt-text="Screenshot of the Start document translation dialog window.":::
@@ -289,7 +289,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
 
 1. Select **New step** and enter **Azure Blob Storage** in the search box.
 
-1. Select the **Create blob (V2)** action.
+1. Select the **`Create blob (V2)`** action.
 
 1. If you're using the Azure storage step for the first time, you need to enter your storage resource authentication:
 
@@ -326,7 +326,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
       :::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the how-to-add connection window.":::
 
       > [!NOTE]
-      > After you've setup your connection, you won't be required to reenter your credentials for subsequent Translator flows.
+      > After setting up your connection, you won't be required to reenter your credentials for subsequent Translator flows.
 
 1. The **Start document translation** action window now appears. Complete the fields as follows:
 
@@ -342,7 +342,7 @@ Here are the steps to upload a file from your SharePoint site to Azure Blob Stor
    * Select the checkbox next to the target container.
    * Select the ellipses located at the right, then choose **Properties**.
    * The target URL is located at the top of the Properties list. Select the **Copy to Clipboard** icon.
-   * Navigate back to your Power automate flow and paste the target URL in the **Location of the translated documents** field.
+   * Navigate back to your Power Automate flow and paste the target URL in the **Location of the translated documents** field.
 
 1. Choose a **Target Language** from the dropdown menu and select **Save**.
 
@@ -401,7 +401,7 @@ In this step, you retrieve the translated document from Azure Blob Storage and u
 
    :::image type="content" source="../media/connectors/do-until-progress.png" alt-text="Screenshot showing the Do until control action.":::
 
-1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **Get blob content using path (V2)** action.
+1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **`Get blob content using path (V2)`** action.
 1. In the **Storage account name or blob endpoint** field, select **Enter custom value** and enter your storage account name.
 1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression**, and enter the following logic in the formula field:
 
@@ -411,12 +411,12 @@ In this step, you retrieve the translated document from Azure Blob Storage and u
 
    ```
 
-1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **Get Blob Metadata using path (V2)** action.
+1. Select **Add an action**, enter **Azure Blob Storage** in the search box, and select the **`Get Blob Metadata using path (V2)`** action.
 1. In the **Storage account name or blob endpoint** field, select **Enter custom value** and enter your storage account name.
 
    :::image type="content" source="../media/connectors/enter-custom-value.png" alt-text="Screenshot showing 'enter custom value' from the create-blob-(V2) window.":::
 
-1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression** and enter the following logic in the formula field:
+1. Select the **Blob path** field to show the **Dynamic content** window, select **Expression**, and then enter the following logic in the formula field:
 
    ```powerappsfl
 
@@ -451,9 +451,9 @@ Let's check your document translation flow and results.
 
    :::image type="content" source="../media/connectors/test-flow.png" alt-text="Screenshot showing the test icon/button.":::
 
-1. Select **Test Flow** → **Manually** → **Test** from the right-side window.
-1. In the **Run flow** window, select the **Continue** then the **Run flow** buttons.
-1. Finally, select  the **Done** button.
+1. Select **`Test Flow`** → **Manually** → **Test** from the right-side window.
+1. In the **`Run flow`** window, select the **Continue** then the **`Run flow`** buttons.
+1. Finally, select  the **`Done`** button.
 1. You should receive a "Your flow ran successfully" message and green check marks align with each successful step.
 
    :::image type="content" source="../media/connectors/successful-sharepoint-flow.png" alt-text="Screenshot showing a successful flow using SharePoint and Azure Blob Storage.":::
diff --git a/articles/ai-services/translator/connector/text-translator-flow.md b/articles/ai-services/translator/connector/text-translator-flow.md
@@ -7,7 +7,7 @@ manager: nitinme
 ms.service: azure-ai-translator
 ms.custom: build-2023
 ms.topic: how-to
-ms.date: 07/10/2024
+ms.date: 01/28/2025
 ms.author: lajanuar
 ---
 
@@ -21,7 +21,7 @@ ms.author: lajanuar
 
 > [!IMPORTANT]
 >
-> * The Translator connector is currently available in public preview. Features, approaches and processes may change, prior to General Availability (GA), based on user feedback.
+> * The Translator connector is currently available in public preview. Features, approaches, and processes can change, before General Availability (GA) release, based on user feedback.
 
 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.
 
@@ -79,7 +79,7 @@ Let's select an action. Choose to translate or transliterate text.
       :::image type="content" source="../media/connectors/add-connection.png" alt-text="Screenshot showing the add-connection window.":::
 
       > [!NOTE]
-      > After you've setup your connection, you won't be required to reenter your credentials for subsequent Translator flows.
+      > After setting up your connection, you won't be required to reenter your credentials for subsequent Translator flows.
 
 1. The **Translate text** action window appears next.
 1. Select a **Source Language** from the dropdown menu or keep the default **Auto-detect** option.
diff --git a/articles/ai-services/translator/document-translation/language-studio.md b/articles/ai-services/translator/document-translation/language-studio.md
@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-translator
 ms.topic: quickstart
-ms.date: 06/07/2024
+ms.date: 01/28/2025
 ms.author: lajanuar
 ms.custom: references_regions, build-2023
 recommendations: false
@@ -16,7 +16,7 @@ recommendations: false
 
 > [!IMPORTANT]
 >
-> * Document Translation in Language Studio is currently in Public Preview. Features, approaches and processes may change, prior to General Availability (GA), based on user feedback.
+> * Document Translation in Language Studio is currently in Public Preview. Features, approaches, and processes can change, before General Availability (GA) release, based on user feedback.
 >
 > * Currently, virtual network connectivity isn't supported for the Document Translation feature in the Language Studio.
 
@@ -59,7 +59,7 @@ Document Translation in Language Studio requires the following resources:
 
   * **Resource Region**. For this project, choose a geographic region such as **East US**. For Document Translation, [system-assigned managed identity](how-to-guides/create-use-managed-identities.md) isn't supported for the **Global** region.
 
-  * **Pricing tier**. Select Standard S1 or D3 to try the service. Document Translation isn't supported in the free tier.
+  * **Pricing tier**. Select Standard S1 or D3. Document Translation isn't supported in the free tier.
 
 * An [**Azure Blob Storage account**](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM). An active Azure Blob Storage account is required to use Document Translation in the Language Studio.
 
@@ -147,7 +147,7 @@ While still in the **files and destination** section, select **Download translat
 1. The **Job history** page contains the **Translation job id** and job status.
 
     > [!NOTE]
-    > The list of translation jobs on the job history page includes all the jobs that were submitted through the chosen translator resource. If your colleague used the same translator resource to submit a job, you will see the status of that job on the job history page.
+    > The list of translation jobs on the job history page includes all the jobs that were submitted through the chosen translator resource. If your colleague used the same translator resource to submit a job, the status of that job appears on the job history page.
 
    :::image type="content" source="media/language-studio/job-history.png" alt-text="Screenshot of the job history page.":::
 
diff --git a/articles/ai-services/translator/firewalls.md b/articles/ai-services/translator/firewalls.md
@@ -1,25 +1,25 @@
 ---
-title: Translate behind firewalls - Translator
+title: Translate behind firewalls - Azure AI Translator
 titleSuffix: Azure AI services
 description: Azure AI Translator can translate behind firewalls using either domain-name or IP filtering.
 #services: cognitive-services
 author: laujan
 manager: nitinme
 ms.service: azure-ai-translator
 ms.topic: conceptual
-ms.date: 07/09/2024
+ms.date: 01/28/2025
 ms.author: lajanuar
 ---
 
-# Use Translator behind firewalls
+# Use Azure AI Translator behind firewalls
 
-Translator can translate behind firewalls using either [Domain-name](/azure/firewall/dns-settings#dns-proxy-configuration) or [IP filtering](#configure-firewall). Domain-name filtering is the preferred method.
+Azure AI Translator can translate behind firewalls using either [Domain-name](/azure/firewall/dns-settings#dns-proxy-configuration) or [IP filtering](#configure-firewall). Domain-name filtering is the preferred method.
 
 If you still require IP filtering, you can get the [IP addresses details using service tag](/azure/virtual-network/service-tags-overview#discover-service-tags-by-using-downloadable-json-files). Translator is under the **CognitiveServicesManagement** service tag.
 
 ## Configure firewall
 
- Navigate to your Translator resource in the Azure portal.
+ Navigate to your Azure AI Translator resource in the Azure portal.
 
 1. Select **Networking** from the **Resource Management** section.
 1. Under the **Firewalls and virtual networks** tab, choose **Selected Networks and Private Endpoints**.
@@ -33,7 +33,7 @@ If you still require IP filtering, you can get the [IP addresses details using s
 
 1. To grant access to an internet IP range, enter the IP address or address range (in [`CIDR` notation](https://tools.ietf.org/html/rfc4632)) under **Firewall** > **Address Range**. Only valid public IP (`non-reserved`) addresses are accepted.
 
-Running Microsoft Translator from behind a specific IP filtered firewall is **not recommended**. The setup is likely to break in the future without notice.
+Running Azure AI Translator from behind a specific IP filtered firewall is **not recommended**. The setup is likely to break in the future without notice.
 
 The IP addresses for Translator geographical endpoints as of September 21, 2021 are:
 
@@ -45,6 +45,6 @@ The IP addresses for Translator geographical endpoints as of September 21, 2021
 
 ## Next steps
 
-[**Translator virtual network support**](reference/v3-0-reference.md#virtual-network-support)
+[**Azure AI Translator virtual network support**](reference/v3-0-reference.md#virtual-network-support)
 
 [**Configure virtual networks**](../cognitive-services-virtual-networks.md#grant-access-from-an-internet-ip-range)
