Document Translation isn't supported in the free tier. The value that you enter in the Name field will be the custom domain name parameter for your endpoint. The name you choose must be unique within Azure.ĭocument Translation requires a custom domain endpoint. Enter the name you have chosen for your resource. If you're planning on using a system-assigned managed identity for authentication, choose a geographic region like West US. Choose Global unless your business or application requires a specific region. You can create a new resource group or add your resource to a pre-existing resource group that shares the same lifecycle, permissions, and policies. Select one of your available Azure subscriptions. This container is where your translated files are stored (required).Ī single-service Translator resource ( not a multi-service Azure AI services resource):Ĭomplete the Translator project and instance details fields as follows: This container is where you upload your files for translation (required). You also need to create containers in your Azure Blob Storage account for your source and target files: If you don't have one, you can create a free account.Īn Azure Blob Storage account. See Azure AI services pricing-Translator.Īn active Azure account. ![]() However, Document Translation is currently supported in the Translator (single-service) resource only, and is not included in the Azure AI services (multi-service) resource.ĭocument Translation is only supported in the S1 Standard Service Plan (Pay-as-you-go) or in the D3 Volume Discount Plan. Typically, when you create an Azure AI resource in the Azure portal, you have the option to create a multi-service key or a single-service key.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |