AI Easy Translator

AI Easy Translator simplifies the process of translating text across multiple languages, enabling seamless communication for global IT support teams and applications. This Azure Managed Application provides a robust, scalable, and secure solution for translating text in real-time, supporting over 100 languages and dialects.

By leveraging Azure AI Translator, AI Easy Translator delivers instant, enterprise-grade translations without the need to manage underlying infrastructure, allowing teams to focus on core business functions while ensuring efficient and accurate communication.

This guide shows you how to deploy and start using AI Easy Translator, a one‑click Azure Managed Application that installs inside your subscription. No extra infrastructure, no vendor access.

Technical Details of AI Easy Translator Solution

Before you deploy

Ensure you have sufficient permissions to provision resources for Azure AI Translator. Required Azure role: Contributor (or higher) in the target subscription.

If you have previously deployed an Azure AI service, you may skip the following steps.

Register the Cognitive Services Resource Provider

Azure Resource Providers supply Azure resources. Before creating an Azure AI Translator resource, ensure the Microsoft.CognitiveServices provider is registered.

Steps to Register via Azure Portal:

Sign in to the Azure Portal.
Navigate to Resource groups in the left-hand menu.
Select your resource group.
Go to Settings > Resource providers.
Locate Microsoft.CognitiveServices in the list.
If the status is NotRegistered, click Register.

Note: Registration requires the Microsoft.Authorization/register/action permission, included in Owner or User Access Administrator roles. The Contributor role does not include this permission.

Alternative CLI Command:

az provider register --namespace Microsoft.CognitiveServices

Accept the Responsible AI Notice

When deploying an Azure AI service for the first time, you must accept the Responsible AI (RAI) notice, which outlines Microsoft's guidelines for responsible AI usage.

Steps:

In the Azure Portal, click Create a resource.
Search for Cognitive Services and click Create.
Fill in the required fields and click Review + create.
Review the Responsible AI notice and click Accept.

Note: After accepting the RAI notice, you may delete the test AI service. The acceptance is tied to your account, not the specific resource.

Deploy in few clicks

AI Easy Translator can be deployed in just a few steps via the Azure Marketplace.

Open the offer in Azure Marketplace and click Create.

AI Easy Translator

On the Basics tab, fill in the required details:
- Subscription – Choose the subscription where the resource should be deployed.
- Resource group – Select an existing resource group or create a new one.
- Region – Choose the Azure region (data center location) where the service will be deployed. This determines:
  - Physical location of the resources.
  - Where your data is processed.
  - Latency for end users (choose the region closest to your primary users for best performance).
  - Compliance with regional data residency requirements.
- Service Instance Name – Enter a unique name using lowercase letters, numbers, or hyphens (5–40 characters).
- Pricing Tier – Choose between:
  - F0 → Free tier (limited use, ideal for testing)
  - S1 → Standard tier (recommended for production)
- Tags (optional) – Add metadata such as cost center or owner for better resource tracking.

Basics configurations tab

Review + Create → Create. Azure builds the resource in a managed resource group; it typically completes in under a minute.

After deployment

Find your newly deployed resources of your managed application located in the managed resource group, Select Go to resource and retrieve your key and endpoint.

You need the key and endpoint from the resource to connect your application to the Translator service. You paste your key and endpoint into the code later in the quickstart. You can find these values on the Azure portal Keys and Endpoint page:

Use Case: Sending Translation Requests

You are now ready to use AI Easy Translator to translate text across 100+ supported languages, including German, Czech, Arabic, Dutch, English, French, Italian, Japanese, Korean, Polish, Portuguese, Spanish, Swedish, and more.

Authorization and Security

To ensure secure access, include the appropriate headers in your API requests:

curl https://<yourEndpoint>/translate?api-version=3.0\
     -H "Ocp-Apim-Subscription-Key: <yourKey>" \
     -H "Content-Type: application/json" \
     -d '[{"Text":"Hello world"}]' \
     -G --data-urlencode "from=en" --data-urlencode "to=de"

Expected response:

[
  {
    "translations": [
      {
        "text": "Hallo Welt",
        "to": "de"
      }
    ]
  }
]

Network & Firewall Configuration

AI Easy Translator requires outbound HTTPS (port 443) to connect to Azure AI Translator endpoints. Below are secure configuration options for different network environments to ensure seamless connectivity. For detailed guidance, see Microsoft Learn: Translate behind firewalls.

Before You Configure

Ensure you have sufficient permissions to configure network settings (e.g., Azure Firewall, NSGs, or on-premises firewalls). Required Azure role: Network Contributor or higher for Azure network resources.

Configuration Options

Azure Virtual Networks (VNets), NSGs, or Azure Firewall
- Allow the CognitiveServicesManagement service tag in your network security group or Azure Firewall.
- Why: This service tag includes the Azure AI Translator endpoint, with IP ranges automatically updated by Azure for reliable connectivity.
On-Premises or Third-Party Firewalls
- Download the weekly ServiceTags_Public_*.json file from Microsoft and filter for CognitiveServicesManagement IP ranges.
- Why: Microsoft updates this file weekly, providing at least a one-week lead time for IP range changes.
Static IP for Regulated Environments
- Create a Private Endpoint for the Azure AI Translator resource to obtain a static private IP and DNS record (e.g., <name>.privatelink.cognitiveservices.azure.com).
- Why: Keeps traffic within your VNet, VPN, or ExpressRoute, meeting static IP or private connectivity requirements.

Best practice
Microsoft recommends domain-name filtering (e.g., *.cognitiveservices.azure.com) over IP filtering for simplicity, where possible.
Avoid hardcoding specific IP addresses, as they may change without notice, potentially breaking connectivity.
If using Private Endpoints, you must use the Virtual Network endpoint instead of the public endpoint. Access tokens are not supported with Private Endpoints.
For additional details: https://learn.microsoft.com/en-us/azure/ai-services/translator/how-to/use-firewalls

Enjoy instant, enterprise grade translation in minutes. If you hit a snag, ping support@sykorait.com